-
31 Jul 2012 9:12 PM #1
Sencha sample app generated for Android native fails to start
Sencha sample app generated for Android native fails to start
Hi All,
Trying to compile navigationview example tha tcomes with sencha touch 2...
Using sencha-touch-2.0.1.1, plus patches posted here fixing android API level issues. After some tinkering with classpath, and JAVA_HOME env. variables got the build working. However, 2 issues.
packager.json looks like this:
1) sencha app build native - command hangs unless I have an android device connected via usb. Apk is stil produced though. I did wait for up to 20 minutes, but no activity in the task manager, and 20 mins should be more than enough to build sample app. However, with the device connected it goes through in less than a minute.Code:{ "applicationName":"NView", "applicationId":"com.sample.nview", "versionString":"1.0", "versionCode":"1", "iconName":"resources/icons/icon.png", "inputPath":"C:\\Dev\\Sencha2\\sencha-touch-2.0.1.1\\examples\\navigationview\\build\\package", "outputPath":"C:\\Dev\\Sencha2\\sencha-touch-2.0.1.1\\examples\\navigationview\\build\\native", "configuration":"Release", "platform":"Android", "deviceType":"Universal", "certificatePath":"../../../zst.jks", "certificateAlias":"zst", "certificatePassword":"asd123456", "sdkPath":"c:/dev/androidsdk", "androidAPILevel":"4", "orientations": [ "portrait", "landscapeLeft", "landscapeRight", "portraitUpsideDown" ] }
2) apk is generated and attempted to be executed. I get white screen and the following error on console:
Digging the logcat from the device shows this error:Code:""c:/dev/androidsdk\tools\android" create project --target android-4 --name NView --activity STActivity --path "C:\Dev\Sencha2\sencha-touch-2.0.1.1\deploy\native\navigationview\/" --package com.sample.nview"""c:/dev/androidsdk\platform-tools\adb" install -r "C:\Dev\Sencha2\sencha-touch-2.0.1.1\deploy\native\navigationview\NView.apk"" ""c:/dev/androidsdk\platform-tools\adb" shell am start -n com.sample.nview/.STActivity" [ERROR] 2527 KB/s (647072 bytes in 0.250s)
BTW, initially packager.json had input and output path variables set to build/native but "sencha app build native" overwrote those two in the packager.json. Is that supposed to happen? I can see packager.json.temp during the build, and it gets left over if I have to break the hung build process with ctrl+c.Code:E/chromium( 5243): external/chromium/net/disk_cache/stat_hub.cc:190: [0731/211201:ERROR:stat_hub.cc(190)] StatHub::Init - App com.sample.nview isn't supported. E/chromium( 5243): external/chromium/net/disk_cache/stat_hub.cc:190: [0731/211201:ERROR:stat_hub.cc(190)] StatHub::Init - App com.sample.nview isn't supported.
I've also tried "tabs" example, same results.
I've tried 2 different android devices with Android versions 2.3 and 4.0, no success.
-
7 Aug 2012 11:57 AM #2Sencha - Senior Forum Manager
- Join Date
- Mar 2007
- Location
- St. Louis, MO
- Posts
- 34,085
- Vote Rating
- 453
In app.json, did you change logger to be false (bool)?
Mitchell Simoens @SenchaMitch
Sencha Inc, Senior Forum Manager
________________
http://www.JSONPLint.com - Source to lint your JSONP!
Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
https://github.com/mitchellsimoens
Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/
Need more help with your app? Hire Sencha Services services@sencha.com
Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is almost in print!
When posting code, please use BBCode's CODE tags.
-
7 Aug 2012 11:15 PM #3
"buildOptions" section? yes, it is set to bool, false.
"logger": false
-
16 Dec 2012 11:57 PM #4
I've encountered the same problem, and logger is set to false for me as well. I've Googled extensively, have not found a solution. The one difference for me is I've been packaging the app with PhoneGap
Can anyone help here?
-
27 Jan 2013 7:58 AM #5
I have this same problem too in phoneGap
Thank you for reporting this bug. We will make it our priority to review this report.


Reply With Quote