| GitHub Issue | n/a |
|---|
| Type | Bug |
|---|
| Priority | High |
|---|
| Status | Closed |
|---|
| Resolution | Fixed |
|---|
| Resolution Date | 2013-07-01T19:18:48.000+0000 |
|---|
| Affected Version/s | Release 3.0.2, Release 3.1.0 |
|---|
| Fix Version/s | n/a |
|---|
| Components | Android |
|---|
| Labels | qe-3.1.0 |
|---|
| Reporter | Dustin Hyde |
|---|
| Assignee | Chris Barber |
|---|
| Created | 2013-04-06T02:47:43.000+0000 |
|---|
| Updated | 2013-07-01T19:18:48.000+0000 |
|---|
Android Emulator runtime fails to load with attach of thread 'Binder Thread #3' failed.
Logs attached.
Test Steps:
1. Titanium Studio.
2. Create Titanium Project.
2. Run Android Emulator.
Test Result:
Android Emulator runtime fails to load with attach of thread 'Binder Thread #3' failed.
Fails in both Appcelerator Studio and terminal.
A comment here suggests it can be an issue with a name attribute: http://stackoverflow.com/questions/11230388/android-app-crashes-at-startup-attach-of-thread-binder-thread-3-failed But there seem to be other possibilities, all just naturally related to the Android emulator.
Yes.
I deleted ~/.android and it worked.
I generated a new Android Emulator using Appcelerator Studio with a Titanium Project w/Appcelerator Services and the app ran successfully. The emulator corruption does not seem related to Appcelerator Studio.
This is happening on device as well if you try to run a Titanium Project with Appcelerator Services, it could be related to the crittercism module. I attached android device debugger log 'android-console.txt'. OS: OS X Mountain Lion 10.8.3 Appcelerator Studio: 3.1.0.201304082106 Titanium CLI: 3.1.0-cr Titanium SDK: 3.1.0.v20130408154547 Android SDK Tools: r21.1 Android Device: Samsung Galaxy S3 Mini 4.1.1 Android Emulator: Google APIs 2.2 Test Steps: 1. Open Appcelerator Studio. 2. Create Default Titanium Project w/Appcelerator Services. 3. Debug on Android Device. Test Result: App fails to load, see 'android-console.txt'. App frozen with red appcelerator splash screen. Must terminate app manually, locks main UI of device. I can debug on android device using a titanium project with no services.
Seems intermittent.
Looks like a crittercism related failure, see related studio ticket.
[~nle] and [~gtavridis] This might be a crittercism issue. Can we have them take a look?
Hello all, I looked through the two attached logs with runtime output (with "binder Thread #3" in the title) and noticed one thing in common. It seems that the app failed to install in both cases due to insufficient storage. "Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE]" So there could be an issue where the process after the failure is not cognizant of that fact. The other logs seem to be the same as in TIMOB-13934 : [ERROR][TiApplication(31907)] java.lang.NoClassDefFoundError: com.crittercism.ti.CrittercismBootstrap So perhaps they are two separate problems.
Just want to add that the "Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE]" is an error I get very often when trying to install an app to the emulator. And I don't have the Crittercism module at all.
@Daniel, you need to increase the size of your AVD or uninstall some apps.
Marking as duplicate of TIMOB-13934. Insufficient storage errors will we addressed as part of TIMOB-9859.
Closing.
Reopening to edit labels