You found a bug! We've classified it as
We encourage you to continue the discussion and to find an acceptable workaround while we work on a permanent fix.
[2.1] Splash screen is white on startup on Android and iOS
Sencha Touch version tested:
Browser versions tested against:
- Sencha Touch 2.1.0
- Sencha cmd 184.108.40.206
- Stock android
Steps to reproduce the problem:
- Safari, chrome and stock browser are displaying the dots splaschscreen, not when packaged in apk or ipa
The result that was expected:
- sencha generate app
- sencha app build package
- sencha package build android.json (or ios.json)
The result that occurs instead:
- No white screen : white dots on blue screen
- Android 4.1.2
- W7 64bits
Did you check for any errors?
Errors? They are none... It's the basic application, the one when you start developing on sencha.
Application is running fine, but this white splash screen is annoying...
Do you have the splash screen when you build it on iOS or android?
I think it's definitively a bug unless you get those dots by yoursel instead of this white screen
No error on build testing, production, package
here's the end output with sencha -d package build and.json, no error (and the index file in apk launches the dots on chrome when extracted) :
Edit : removing ST stuff in my index.html file (the one in package before building the apk) does the trick. Dots are here again (very short white screen then the white dots)
Verifying alignment of ./Application/app-final/basic/\\Basic.apk (4)...
50 META-INF/MANIFEST.MF (OK - compressed)
961 META-INF/BASIC.SF (OK - compressed)
1981 META-INF/BASIC.RSA (OK - compressed)
3080 assets/resources/css/app.css (OK - compressed)
83612 assets/resources/icons/Icon.png (OK)
87292 assets/resources/icons/Icon@2x.png (OK)
94680 assets/resources/icons/Icon~ipad.png (OK)
99220 assets/resources/icons/Iconemail@example.com (OK)
108596 assets/resources/icons/iTunesArtwork.png (OK)
172104 assets/resources/icons/icon-spot~ipad.png (OK)
175208 assets/resources/startup/1496x2048.png (OK)
230840 assets/resources/startup/1536x2008.png (OK)
284772 assets/resources/startup/320x460.jpg (OK)
291908 assets/resources/startup/640x920.png (OK)
318120 assets/resources/startup/748x1024.png (OK)
341468 assets/resources/startup/768x1004.png (OK)
364587 assets/app.js (OK - compressed)
490165 assets/app.json (OK - compressed)
490356 assets/icon.png (OK)
797525 assets/index.html (OK - compressed)
798671 res/layout/main.xml (OK - compressed)
799024 AndroidManifest.xml (OK - compressed)
799768 resources.arsc (OK)
800896 res/drawable-hdpi/icon.png (OK)
1117044 res/drawable-ldpi/icon.png (OK)
1433192 res/drawable-mdpi/icon.png (OK)
1749324 classes.dex (OK - compressed)
""C:/apps/android-sdk\tools\android" create project --target android-10 --name Basic --activity STActivity --path "./Application/app-final/basic/\/" --package com.testapp.basic"
[DBG] exit code was : 0
[DBG] exit code was : 0
It's the last piece of my app, and this white screen makes the all thing unfinished !
Check if this is your problem
White Screen of Death
Noipe, read my post again, it's the splash screen only, not the app !
Really no one ?
Are all sencha users building such apps ? No splash ? Just a long white screen ?
I can't tell for iOS. But for Android I noticed that behavior with my apps as well. I think it's a caching 'problem'. While developing / testing we do a lot of installs of the same app and it seemed to me that the cache comes somehow 'out of sync (it's probably something else, but that's what I call it). So removing the cache of the app (in the device settings) normally helps to get the launcher screen back. Or you remove the whole app from the device and re-install it.
I tried that, nothing.
Could you reproduce that with the beginner app (sencha create) and then pack with the latest cmd ?
I'm at 99% sure it's a bug, but no one is answering,
It's a pretty big one, I think, beause you don't want your customer having a 30 s white screen, at least not me...
I do not understand the answer of mitch either, it's like he posted to say : "Ok, I posted, done !",
It would have been pretty easy to reproduce this bug in a second....