25 Answers

• Replaced the new android.py file fixed the problem.

  However, creating a default new mobile project, and run it in the android emulator still crash. The app crashed, not the emulator.

• For me replacing Android.py on OSX didn't fix the issue. Still don't see the emulator option for Android. (I did make a new project afterwards). Out of ideas.

• Hey guys..

  If you're still having the app-crash-on-launch problem or any other potential issues when Launching your app, you should probably try the latest updates from our git repository. I've fixed a number of issues with the SDCard copier, and packaging/deploying in general.

  For now, the sdcard copier has been turned off by default unless you put this property in your tiapp.xml:

  <property name="ti.android.loadfromsdcard" type="bool">true</property>
  

  I've put up a public drop that has recent builds of the android only mobile sdk here:
  http://drop.io/titanium_android_nightly

  Please keep in mind these are android only builds, meaning that you won't be able to launch your project in the iPhone simulator with these builds. Also, they are built from HEAD meaning there is a chance that there is some breaking changes since our last public release.

  You can extract this zip into your Titanium installation folder. In OSX that's one of:

  /Library/Application Support/Titanium
  # or
  ~/Library/Application Support/Titanium
  

  in Windows:

  # Vista, Win7
  C:\ProgramData\Titanium
  # XP
  C:\Documents and Settings\All Users\Application Data\Titanium
  

  in Linux:

  ~/.titanium
  

  You'll need to change your project's SDK to '1.2.1' after you extract and restart Developer

• See this item for the answer and workaround.

• I replaced the py file as above - but I am still having the same issue. Android is not showing up as an option in the emulator tab.

  It does show up in the KitchenSink project - but the android text boxes show "Loading…" but nothing happens.

  I am on a Mac running SnowLeopard.

  Thanks.

• Could anyone from Appcelerator team make a very clear explanation and stick it to the top of web page about all android.py related issues? We can see dozens of similar messages and twitter posts about Ti mobile issues, and answer is same for all, but it seems it's not enough.

  SDK update (android.py) doesn't fix problem of existing projects, because /build/ folder is created at project creation phase and never recreated (why???). If some part is broken (Ti SDK, iPhone SDK, Android SDK) - project will be broken. So, to fix existing project, you need create new project with same ID, name etc. and copy Resources folder from old one to new project

• Today i tried for the first time to install Titanium and i have the same issues with android.

  I'm running Titanium 1.2.1 with mobilesdk 1.2.1 from mobilesdk-1.2.1-20100426195031-android-win32.zip and the latest android sdk.
  Java jdk-6u20-windows-i586 and the latest Kitchen Sink from github.

  I'm using the modified android.py. Should i use the included one?

  Kitchen Sink is crashing in both 1.6 simulator and on my Xperia X10.

  Any other hints?

• Hmm, I'm having the same issue, and this workaround does not seem to work.

  I'm running windows 7, and I modified the file in: C:ProgramDataTitaniummobilesdkwin321.2.0android

  EDIT: After playing around with it for a while, and upgrading my Android SDK, it now works with new projects. Sorry for the confusion.

• I had the same problem, I replaced the android.py, it didn't work. Some how I tried to figure out within the android.py file that it needs android 1.6 revision 4. I updated and it worked. I guess this was the problem.

  Hope it helps.

  Thanks.

• I replaced the py file as above - but I am still having the same issue. Android is not showing up as an option in the emulator tab.

  It does show up in the KitchenSink project - but the android text boxes show "Loading…" but nothing happens.

  I am on a Mac running SnowLeopard.

  Thanks.

• I replaced the py file as above - but I am still having the same issue. Android is not showing up as an option in the emulator tab.

  It does show up in the KitchenSink project - but the android text boxes show "Loading…" but nothing happens.

  I am on a Mac running SnowLeopard.

  Thanks.

• I'm having the exact same problem as Vasan.

  I'm on a Mac and when I create a new project, Titaniums says I have the Android SDK, I have the Android 1.6 r4, but when i go to the Run Emulator tab, Android is not visible.

  Android is only visible on the Kitchen Sink project, but when I try to run it there, it compiles and everything seems ok, no error messages of any kind, the emulator start, but nothing more appens, no app gets installed or starts…

  Can any of the devs give an input here?

• Hey guys..

  If you're still having the app-crash-on-launch problem or any other potential issues when Launching your app, you should probably try the latest updates from our git repository. I've fixed a number of issues with the SDCard copier, and packaging/deploying in general.

  For now, the sdcard copier has been turned off by default unless you put this property in your tiapp.xml:

  <property name="ti.android.loadfromsdcard" type="bool">true</property>
  

  I've put up a public drop that has recent builds of the android only mobile sdk here:
  http://drop.io/titanium_android_nightly

  Please keep in mind these are android only builds, meaning that you won't be able to launch your project in the iPhone simulator with these builds. Also, they are built from HEAD meaning there is a chance that there is some breaking changes since our last public release.

  You can extract this zip into your Titanium installation folder. In OSX that's one of:

  /Library/Application Support/Titanium
  # or
  ~/Library/Application Support/Titanium
  

  in Windows:

  # Vista, Win7
  C:ProgramDataTitanium
  # XP
  C:Documents and SettingsAll UsersApplication DataTitanium
  

  in Linux:

  ~/.titanium
  

  You'll need to change your project's SDK to '1.2.1' after you extract and restart Developer

• tested with nightly 4/22 worked fine.

• Strange problem: I updated titanium to 1.2.1 (Windows XP), trying to build KitchenSink and run in emulator, but after "Copying project resources.." nothing happens…
  I think problem in this lines:

  [INFO] Copying project resources..
  [TRACE] Traceback (most recent call last):
  [TRACE] File "C:Documents and SettingsAll Users.WINDOWS2Application DataTitaniummobilesdkwin321.2.1androidbuilder.py", line 896, in <module>
  [TRACE] s.build_and_run(False,avd_id)
  [TRACE] File "C:Documents and SettingsAll Users.WINDOWS2Application DataTitaniummobilesdkwin321.2.1androidbuilder.py", line 751, in build_and_run
  [TRACE] self.copy_project_resources()
  [TRACE] File "C:Documents and SettingsAll Users.WINDOWS2Application DataTitaniummobilesdkwin321.2.1androidbuilder.py", line 267, in copy_project_resources
  [TRACE] self.project_deltafy = Deltafy(resources_dir, include_callback=self.include_path)
  [TRACE] File "C:Documents and SettingsAll Users.WINDOWS2Application DataTitaniummobilesdkwin321.2.1androiddeltafy.py", line 84, in __init__
  [TRACE] self.conn = sqlite3.connect(self.db_path, detect_types=sqlite3.PARSE_DECLTYPES)
  [TRACE] sqlite3.OperationalError: unable to open database file
  

  The full debug log is here: http://pastie.org/930144

• Yet another +1

  I'm kinda surprised this has been sitting here for this long, certainly doesn't inspire me to pay money for the service if show-stopping bugs are ignored like this in the main product.

  Would love to try Titanium out, but primarily interested in android dev so will wait till it gets resolved I suppose.

  -Jacob

• I tried the solution provided using the nightly snapshot. Changed my project to 1.2.1, didn't make a difference, still can't emulate or launch or package on Android.

  OSX.

• @Jacob @Gennadly have you guys tried using a nightly as posted in my instructions at the top of this post?

• please tell detail informations, step by step,thanks.

• Yes, I tested the nightly. If this forum wasn't in a silly order, you'd probably have noticed I posted that 2 weeks ago. I'm really surprised that this isn't getting critical bug status.

• Is anyone going to given a permanent solution for this?

  I can't defer my work for indefinite period :(

• Is this problem fixed yet? I just completely restarted my install setup on the mac after my hard drive crashed and have started seeing this problem. First of all, I am unable to create new projects based on 1.4.0 - I get a project creation error. Secondly, when I create the project using 1.2.0, The android emulator doesn't show up when I create new projects. It shows up for the kitchen sink project, but even then the Android emulator's SDK version is stuck at "loading…".

  My whole setup used to work right until the hard drive crash and now I feel I'm back at square one. The setup has got to be better - atleast the Titanium Developer main window should have a debug mode so that we can debug such problems.

• Is this problem fixed yet? I just completely restarted my install setup on the mac after my hard drive crashed and have started seeing this problem. First of all, I am unable to create new projects based on 1.4.0 - I get a project creation error. Secondly, when I create the project using 1.2.0, The android emulator doesn't show up when I create new projects. It shows up for the kitchen sink project, but even then the Android emulator's SDK version is stuck at "loading…".

  My whole setup used to work right until the hard drive crash and now I feel I'm back at square one. The setup has got to be better - atleast the Titanium Developer main window should have a debug mode so that we can debug such problems.

• Ok. I was able to get the missing Android emulator tab to show up. All I needed to do was create a directory by name "android" under the build directory of the project. I still have the other problem with the stuck "loading…" message on the SDK drop-down box.

• I have not been able to run a single android "app" over the last three weeks. Desktop App, sure! All day long. Android: no dice. SDK 1.7.x, 2011-06-17 build, and completely pissed/frustrated.