Appcelerator Blog

The Leading Resource for All Things Mobile

Studio 3.1.4 for OS X Mavericks

2 Flares 2 Flares ×

Today Apple releases the GA version of OS X 10.9 as a free update. If you need to upgrade to Mavericks, we’ve prepared a new update of Studio for you. However, a number of the native SDK software vendors have some kinks remaining in their products, so if you are using HAXM-accelerated Android emulators, Tizen emulators, or BlackBerry emulators, we recommend holding off upgrading to OS X 10.9 until these issues have been sorted out.

Titanium and Appcelerator Studio

The version of Eclipse upon which Studio 3.1.3 is based has issues with file selection dialogs in Mavericks. We’ve corrected this in Studio 3.1.4 by changing the version of Eclipse upon which Studio is based. A guide to visual changes between Studio 3.1.3 and 3.1.4 is available.

To update

Visit the download page for Titanium to download a new version of Titanium Studio, or use the update links below:

Android and Tizen Emulators

Numerous individuals outside the Titanium developer community have reported issues with hardware-accelerated emulators, in particular those for Android and Tizen. It appears that there is a general compatibility issue between HAXM and OS X 10.9. Intel has been alerted to the problem. We have our own tracking issue in ticket TIMOB-15455.

BlackBerry Emulators

The BlackBerry emulators are VMWare images. Currently, the images appear to refuse to start or respond slowly, even when using VMWare Fusion 6. We have alerted BlackBerry to the issue. You can track that issue via ticket TIMOB-15456.

2 Flares Twitter 0 Facebook 0 Google+ 0 LinkedIn 2 Email -- 2 Flares ×

21 Comments

  1. When I try to update Appcelerator Studio using the RC stream the “Available Updates” dialog says “Cannot complete the install because of a conflicting dependecy”.

    • Ingo Muschenetz

      Fokke: Which version of Appcelerator Studio are you updating from?

    • Ingo Muschenetz

      @Fokke I ran into the same issue. The issue was that I had the LiveView feature installed separately…it’s now bundled, so that needs to be uninstalled first.

      1. Appcelerator Studio Menu > About Appcelerator Studio
      2. Click “Installation Details”
      3. Click on “LiveView” and “Uninstall…”

      Follow the instructions and then try to re-update.

  2. Martin

    Installed the update after maveriks and can’t sign in, just gives an error, going through the troubleshoot options now

    get the following error on sign in
    “Titanium Studio”/TitaniumStudio.app/Contents/MacOS/TitaniumStudio
    javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
    at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:190)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1747)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1708)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.handleException(SSLSocketImpl.java:1691)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1222)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1199)
    at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:434)
    at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:166)
    at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:1014)
    at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(HttpsURLConnectionImpl.java:230)
    at com.appcelerator.titanium.core.TitaniumUserManager.signIn(TitaniumUserManager.java:136)
    at com.appcelerator.titanium.rcp.handlers.TitaniumSplashHandler$15.run(TitaniumSplashHandler.java:929)
    Caused by: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
    at sun.security.validator.PKIXValidator.(PKIXValidator.java:57)
    at sun.security.validator.Validator.getInstance(Validator.java:161)
    at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.getValidator(X509TrustManagerImpl.java:108)
    at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:204)
    at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:249)
    at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1188)
    at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:135)
    at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:593)
    at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:529)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:943)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1188)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1215)
    … 7 more
    Caused by: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
    at java.security.cert.PKIXParameters.setTrustAnchors(PKIXParameters.java:183)
    at java.security.cert.PKIXParameters.(PKIXParameters.java:103)
    at java.security.cert.PKIXBuilderParameters.(PKIXBuilderParameters.java:87)
    at sun.security.validator.PKIXValidator.(PKIXValidator.java:55)
    … 18 more
    ^CException in thread “Thread-1” org.eclipse.swt.SWTException: Invalid thread access
    at org.eclipse.swt.SWT.error(SWT.java:4397)
    at org.eclipse.swt.SWT.error(SWT.java:4312)
    at org.eclipse.swt.SWT.error(SWT.java:4283)
    at org.eclipse.swt.widgets.Widget.error(Widget.java:783)
    at org.eclipse.swt.widgets.Widget.dispose(Widget.java:670)
    at org.eclipse.swt.widgets.Shell.closeWidget(Shell.java:611)
    at org.eclipse.swt.widgets.Shell.windowWillClose(Shell.java:2327)
    at org.eclipse.swt.widgets.Display.windowProc(Display.java:5530)
    at org.eclipse.equinox.launcher.JNIBridge._takedown_splash(Native Method)
    at org.eclipse.equinox.launcher.JNIBridge.takeDownSplash(JNIBridge.java:167)
    at org.eclipse.equinox.launcher.Main.takeDownSplash(Main.java:2142)
    at org.eclipse.equinox.launcher.Main$SplashHandler.run(Main.java:113)
    Mac-mini:applications Martin$

    • Hi Martin,

      The problem here is that Mavericks removed the base Java install, and if you had other versions of Java installed, it used symlinks to share the SSL cert files. So after you upgraded to Mavericks, the symlinks now point to nonexistent files.

      To fix the issue:
      1. Open the Terminal and run: sudo rm –rf /Library/Java/JavaVirtualMachines/*.jdk
      2. Download Java 7u45 from http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html
      3. Use the installer to install fresh. This will result in good cert files under /Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home/jre/lib/security/. Then launching Studio should work.

      Hope this helps.

      • yuryb

        did everything Michael suggested (in October 28, 2013 @ 8:53 pm post) – still can not run Studio.
        What are my options?
        — downgrade the OSX? how?
        — is there a Studio update which runs on 10.9.1?
        — anything else?
        My Titanium development is on hold due to this issue, customers are furious.
        Help…

        • Ingo Muschenetz

          Upgrade to Studio 3.2.0. It will run on Mavericks.

          • yuryb

            I did, now the Studio runs, but I can not login – login is being rejected…
            I can login to the web site with the same credentials, but not to the Studio. I even created new account, but result is the same… Any suggestions?

          • yuryb

            … I still can use the Studio – can not login. When I run CLI, such as “titanium login” – I can login with no problem, but when I run the studio, I can not login at all, not with my account, nor with a new account (which I created in order to try to login with it). Please help!

  3. Chris Williams

    Martin: Looks like you may have a bad/empty truststore? Looking at http://stackoverflow.com/questions/4764611/java-security-invalidalgorithmparameterexception-the-trustanchors-parameter-mus, the answer seems to be to run:

    cd $OPENJDK_HOME/Contents/Home/jre/lib/security
    ln -s /System/Library/Java/Support/CoreDeploy.bundle/Contents/Home/lib/security/cacerts
    ln -s /System/Library/Java/Support/Deploy.bundle/Contents/Home/lib/security/blacklist
    ln -s /System/Library/Java/Support/Deploy.bundle/Contents/Home/lib/security/trusted.libraries

    Where $OPENJDK_HOME is the root directory of your OpenJDK install, typically OPENJDK_HOME=/Library/Java/JavaVirtualMachines/1.7.0u.jdk

  4. Ingo Muschenetz

    We’ve uncovered an issue with Alloy where apps will not compile. Please follow along here: https://jira.appcelerator.org/browse/ALOY-859

  5. Sebastian

    Updated to this version, because the log won’t appear with Mavericks in 3.1.3

    But neither it does in 3.1.4

    Any hints?

    • Ingo Muschenetz

      @Sebastian, there is this fix that seems relevant, but it was fixed in 3.1.3: https://jira.appcelerator.org/browse/TISTUD-5283. Can you describe your issue in more detail?

      • Andrew

        I am having this same issue. I got update 3.1.4RC for Mavericks and when I run the app in the iOS simulator, I get no app-generated log messages. I get the usual log all the way up to “[INFO] : Focusing the iOS Simulator” then nothing. Is there a fix for this?

        • Michael

          I have the same problem. Console is quiet after “Focusing the iOS Simulator”.
          The problem didn’t go away with the RC as I hoped.

          Logging works when I use the 6.1 emulator. Either someting has happened to the version 7 emulator, or Titanium 3.1.3 broke something.

  6. Vijay

    What is difference between Appcelerator Studio and Titanium Studio?

  7. Sagar

    Hi, I seem to be getting a conflicting dependency error when I try to upgrade. Any recommendation on how to fix this? Thanks.

    Cannot complete the install because of a conflicting dependency.
    Software being installed: Titanium Studio 3.1.4.201310152018-15102013201930 (com.appcelerator.titanium.rcp.product 3.1.4.201310152018-15102013201930)
    Software currently installed: Graphical Editing Framework Draw2d 3.7.1.v20110830-1143-4607w3122194102254 (org.eclipse.draw2d.feature.group 3.7.1.v20110830-1143-4607w3122194102254)
    Only one of the following can be installed at once:
    International Components for Unicode for Java (ICU4J) 50.1.1.v201304230130 (com.ibm.icu 50.1.1.v201304230130)
    International Components for Unicode for Java (ICU4J) 4.4.2.v20110823 (com.ibm.icu 4.4.2.v20110823)
    Cannot satisfy dependency:
    From: Titanium Studio RCP 3.1.4.201310152018-7y7WFA7FEoSDjrz0k5LoMZ7D878H (com.appcelerator.titanium.feature.rcp.feature.group 3.1.4.201310152018-7y7WFA7FEoSDjrz0k5LoMZ7D878H)
    To: org.eclipse.platform.feature.group [4.3.1.v20130911-1000]
    Cannot satisfy dependency:
    From: Titanium Studio 3.1.4.201310152018-15102013201930 (com.appcelerator.titanium.rcp.product 3.1.4.201310152018-15102013201930)
    To: com.appcelerator.titanium.feature.rcp.feature.group [3.1.4.201310152018-7y7WFA7FEoSDjrz0k5LoMZ7D878H]
    Cannot satisfy dependency:
    From: Graphical Editing Framework Draw2d 3.7.1.v20110830-1143 (org.eclipse.draw2d 3.7.1.v20110830-1143)
    To: package com.ibm.icu.text [3.8.1,5.0.0)
    Cannot satisfy dependency:
    From: Graphical Editing Framework Draw2d 3.7.1.v20110830-1143-4607w3122194102254 (org.eclipse.draw2d.feature.group 3.7.1.v20110830-1143-4607w3122194102254)
    To: org.eclipse.draw2d [3.7.1.v20110830-1143]
    Cannot satisfy dependency:
    From: Eclipse e4 Rich Client Platform 1.2.1.v20130910-2014 (org.eclipse.e4.rcp.feature.group 1.2.1.v20130910-2014)
    To: com.ibm.icu [50.1.1.v201304230130]
    Cannot satisfy dependency:
    From: Eclipse Platform 4.3.1.v20130911-1000 (org.eclipse.platform.feature.group 4.3.1.v20130911-1000)
    To: org.eclipse.rcp.feature.group [4.3.1.v20130911-1000]
    Cannot satisfy dependency:
    From: Eclipse RCP 4.3.1.v20130911-1000 (org.eclipse.rcp.feature.group 4.3.1.v20130911-1000)
    To: org.eclipse.e4.rcp.feature.group [1.2.1.v20130910-2014]

    • Hi Sagar, look like you have org.eclipse.draw2d.feature installed on top of the existing version of Studio. Since Studio 3.1.4 updated its Eclipse base to 4.3, you would need to uninstall the draw2d feature, then update Studio, and afterward re-install an Eclipse 4.x compatible version of draw2d feature.

      Hope this helps.

Comments are closed.

Sign up for updates!

Become a mobile leader. Take the first step to scale mobile innovation throughout your enterprise.
Get in touch
computer and tablet showing Appcelerator software
Start free, grow from there.
2 Flares Twitter 0 Facebook 0 Google+ 0 LinkedIn 2 Email -- 2 Flares ×