-
6 Mar 2013 11:53 AM #21
I'm having the same issue.
I'm having the same issue.
Using Sencha Touch 2.1.1 and Cmd 2.0.288, when I build the native application I'm getting the white screen for about 1-2 seconds before the application start.
-
3 Apr 2013 10:47 PM #22
I have the same issue - please see my cross post
http://www.sencha.com/forum/showthread.php?259838-Where-is-TOUCH-3915-fixed&p=954157
-
9 Apr 2013 8:30 PM #23
Sorry, but this is not fixed. Please reopen this bug.
-
10 Apr 2013 8:12 PM #24
Hi,
Yes. White screen is still appeared in android start up for 5 seconds with Sencha touch 2.1.1 /Sencha Cmd 3.1 .
So please reopen the bug and give me a valuable solution on this.
Thanks,
-
12 Apr 2013 4:09 AM #25
Same problem here.
When I install the app on a device, the loading indicator (the 3 dots) shows up the very first time I launch the app. 2nd time, and all consecutive times, I get a white screen until the app launches.
*EDIT* Just to be clear, the loading indicator is missing both on iOS and Android, but the problem is major on Android because of a longer start-up time.Last edited by Gundersen; 12 Apr 2013 at 4:34 AM. Reason: Added
-
12 Apr 2013 4:21 AM #26
-
22 Apr 2013 1:34 AM #27
we are waiting just for this bug to be fixed
we are waiting just for this bug to be fixed
After struggeling for a very long time, to try to get the performance better with phonegap we tried to compile our app with the native Sencha APP android compiler. Unfortunatly this new bug was revealed. But the performance got better. We don't know if we are ever going to release our Sencha Touch based apps' it seems to be a hassle without any end.
We are waiting for this bug to be fixed before we can start selling our app. This is a major bug
-
Today 2:39 AM #28
Shameless bump, this is still present in 2.2 as well. Using a native build, packaged with "sencha app package build <config>". I just get an white splashscreen before the app starts.
This is urgent guys, don't let your community wait that long.
You found a bug! We've classified it as
TOUCH-3915
.
We encourage you to continue the discussion and to find an acceptable workaround while we work on a permanent fix.


Reply With Quote