Hybrid View
-
26 Jan 2013 6:36 AM #1
App hangs on appLoadingIndicator on Android native app - microloader issue
App hangs on appLoadingIndicator on Android native app - microloader issue
REQUIRED INFORMATION
Ext version tested:- Sencha Touch 2.1
- Sencha Cmd 3.0.2.288
- Android 4.0.4
- Android API level 8, 9, & 16
- Generating the default ST 2.1 app freezes on appLoadingIndicator when deployed natively
- Generate app using Code:
sencha generate app TouchTest c:\TouchTest
- cd to TouchTest app and run Code:
sencha app build
- modify packager.json to this:
Code:{ "applicationName":"Touch Test", "applicationId":"com.mycompany.myAppID", "versionString":"1.0", "versionCode":"1", "icon": { "57":"resources/icons/Icon.png", "72":"resources/icons/Icon~ipad.png", "114":"resources/icons/Icon@2x.png", "144":"resources/icons/Icon~ipad@2x.png" }, "inputPath":"build/TouchTest/production", "outputPath":"dist/", "configuration":"Debug", "platform":"Android", "certificatePath":"./my.keystore", "certificatePassword":"mypassword", "provisionProfile":"", "sdkPath":"c:\\Progra~2\\Android\\android-sdk", "androidAPILevel":"9", "permissions":[ "INTERNET", "ACCESS_NETWORK_STATE" ], "orientations": [ "portrait", "landscapeLeft", "landscapeRight", "portraitUpsideDown" ] } - run Code:
sencha app package build packager.json
- Send app to device and install.
- The app should run and hit the main viewport
- App pauses on appLoadingIndicator. I have debugged it to the point described in this post: http://www.sencha.com/forum/showthread.php?254995
See above steps. This was using the default generated app and the versions described above.
HELPFUL INFORMATION
Debugging already done:- I have debugged it to the point described in this post: http://www.sencha.com/forum/showthread.php?254995
- Windows 7 64-bit
Last edited by kevhender; 29 Jan 2013 at 4:29 AM. Reason: Fixed external link
-
28 Jan 2013 5:55 AM #2Sencha - Senior Forum Manager
- Join Date
- Mar 2007
- Location
- St. Louis, MO
- Posts
- 33,641
- Vote Rating
- 434
Thanks for the report! I have opened a bug in our bug tracker.
Success! Looks like we've fixed this one. According to our records the fix was applied for
TOUCH-3952
in
a recent build.


Reply With Quote