Skip to content


Installing Titanium on Mac OS 10.10 Yosemite

Again, not a detailed step-by-step guide but mostly tips on the most annoying parts.
A brief overview of the setup process though: download the package from Appcelerator, launch it, and drag and drop the Titanium icon to the Applications folder in the window that pops up (that process never ceases to amaze me: why on Earth require such kind of user input ? Apple, eh….)

Now you can already run it as any other application, however you are likely to encounter an error telling you that you need Java 6, or maybe some more cryptic error message instead, like The JVM shared library “/Library/Java/JavaVirtualMachines/jdk1.8.0_25.jdk/Contents/Home/bin/../jre/lib/server/libjvm.dylib” does not contain the JNI_CreateJavaVM symbol. The solution to this is to install Java for OS X 2014-001 (source).

The second issue I had was a fairly unspecific An internal error occurred during: “Computing SDK Info…”. java.lang.NullPointerException. A reported solution was to install Titanium CLI from the command line (sudo npm install titanium -g), however in my case, just running the update process a couple of times (and restarting Titanium in-between) did the trick.

Posted in programming.

Tagged with , .


2 Responses

Stay in touch with the conversation, subscribe to the RSS feed for comments on this post.

  1. Tamir Bowen says

    Hi, really need your assistance, I’m having the same problem and the above fixes didn’t work for me.
    See my Q thread: https://developer.appcelerator.com/question/179951/an-internal-error-occurred-during-computing-sdk-info-javalangnullpointerexception

    Any help would be much appreciated.
    – TB

    • patheticcockroach says

      Hi,

      Sorry but I don’t have any other solution than what I presented here. Titanium indeed doesn’t seem very happy with the latest Xcode : this very morning I found that the iOS Simulator didn’t seem to work anymore on my building Mac (and again, the error message, which I didn’t write down, was as useless as usual)… I didn’t manage to find a solution, however the compiled build ran normally on a real device and was accepted for review on the App Store.

      About your point 6), where you say you can’t manually select the path to iOS SDK, I believe I had the very same issue but on Windows and with the Android SDK. The solution I found was to let Titanium install the SDK itself (so actually, a duplicate SDK) instead of trying to make it use the already installed SDK: maybe this could be done for iOS too?



Some HTML is OK

or, reply to this post via trackback.

Please solve the CAPTCHA below in order to fight spamWordPress CAPTCHA