This documentation relates to previous versions of Titanium Studio.

To see the latest documentation, visit docs.appcelerator.com.

Skip to end of metadata
Go to start of metadata

Errors while building a Titanium project are usually due to configuration issues. The most common problems and possible solutions are posted here.

Run/Debug icons are greyed out

This appears to be related to the project no long being recognized as a Titanium project. You can check this by noticing the absence of a "M" or "D" on the project folder.

  1. Follow the steps here and choose either the settings for Titanium Mobile or Titanium Desktop.
  2. You might need to restart Studio.

Build error in console output

Sometimes your project fails to build, but it's not clear if it's an issue with Studio, or perhaps there is a bug in the SDK. To isolate this problem, you can try building from the command line using the exact same parameters as Studio.

  1. Go to Preferences > Studio > Troubleshooting.
    1. Change the dropdown to "All"
    2. Check on "debug specific components"
    3. Check on "com.aptana.core/debug/shell"
  2. Save and exit the preference menu
  3. Re-run the build. View the Studio log file (Help > Studio > View Log file)
  4. You should see an entry like:
  5. Open a terminal window and paste in the first line (the whole line, starting with the reference to Python), as shown below:

Does the process give the same error?

"iOS SDK version XXX not found"

This will happen if you have upgraded your iOS SDKs, and the old one is not available. To fix:

  1. Select Run > Run Configurations... (you will get to the same spot if you choose Debug Configurations...
  2. Select the configuration for the project you are having an issue with.
  3. Choose an available iOS SDK from the list.
  4. Save and close the dialog.

"Could not locate the Android SDK at the given path"

This usually appears inside the "Titanium" preference page inside Studio. Titanium Studio runs a Python script to determine your current configuration. To diagnose the exact issue, please try the following:

  1. Turn on debug logging: Debugging Studio, and enable specific component "com.aptana.core/debug/shell".
  2. Re-open the preference page.
  3. Open the Studio log file (Help > Titanium Studio > View Log File) and scroll to the end.
  4. You should see a command line invocation of avd.py, ex:
  5. Copy and paste that complete command line into a terminal window and run it. Check the output. If it doesn't find "Android 2.2", the configuration will be marked as invalid.

It may be that you don't have an "avd.py" script at the location it's looking. to solve that, just install the latest Continuous Build, ensuring that you choose the master branch from the drop-down menu of the download site, and restart Studio.

iOS configuration issues

This usually appears inside the "Titanium" preference page inside Studio. Titanium Studio runs some commands to determine your current configuration:

  1. To determine the location of your xcode tooling, it runs xcode-select --print-path.
  2. It then looks at /Platforms/iPhoneSimulator.platform/Developer/SDKs underneath that path for the SDK locations.
  3. Currently, it expecting to see at least one iOS SDK of version greater than or equal to 4.2 and less than 5.1. You can have more installed than that, but you at least need one within that range.

Build error: "No such file or directory"

This can be caused by a few different issues:

  1. You are running an incompatible version of XCode. Upgrade to the latest version.
  2. You have not correctly installed the Java JDK.

Xcode not installed

Titanium Studio reports that Xcode is not installed, even though you believe it is. This appears to be caused by a bad install of Xcode. Uninstalling and re-installing Xcode has fixed the issue in every case so far.

You can double check the install location of Xcode by typing the following in Terminal:

Which should print something like '/Developer'

"The directory ... contains 2 projects"

This can happen when renaming an application. To fix this, delete the contents of build/iphone and re-build.

Labels
  • None