ios build glitch
50 views
Skip to first unread message
Dave Dyer
Apr 30, 2017, 2:56:02 AM4/30/17
to CodenameOne Discussions
One of the splash screens you automatically generate for release builds
is being generated as a black frame. This has been going on for a while,
I only noticed by accident.
the bad image is Default-landscape.png
and also {Appname}-landscape.png which is presumably a copy.
incidentally, why are there two of each if the icons ans splash images?
Shai Almog
May 1, 2017, 1:15:06 AM5/1/17
to CodenameOne Discussions
No. That's something that only happens in your app probably due to over-elaborate rendering in the first form.
Dave Dyer
May 1, 2017, 2:43:13 AM5/1/17
to CodenameOne Discussions
The first form is a simple splash screen, and it always seems to be the same one. Is it the first one
you make by any chance?
you make by any chance?
Shai Almog
May 2, 2017, 12:33:59 AM5/2/17
to CodenameOne Discussions
It might be that your app takes longer to initialize the first time it is launched and we end up painting a blank screen.
Dave Dyer
May 2, 2017, 3:49:57 PM5/2/17
to CodenameOne Discussions
I agree that's probably the problem, but this occurs before the main app is touched.
What do you propose to fix it? I suppose you could detect a black screen grab, or
add a screen grab timer to the project inits, or maybe you could introduce an optional
protocol that would let the app say it was ready.
What do you propose to fix it? I suppose you could detect a black screen grab, or
add a screen grab timer to the project inits, or maybe you could introduce an optional
protocol that would let the app say it was ready.
Shai Almog
May 3, 2017, 12:56:01 AM5/3/17
to CodenameOne Discussions
Clear the ~/.cn1 directory content and run the app as if it's running on the first install in the debugger. What's different about that execution and the second execution.
This is what's happening on the server. I'm guessing you create some resources the first time around and those fail. You need to deffer them for later.
This is what's happening on the server. I'm guessing you create some resources the first time around and those fail. You need to deffer them for later.
Dave Dyer
May 3, 2017, 2:09:50 AM5/3/17
to CodenameOne Discussions
The startup doesn't do anything except load the splash image,
but perhaps static initializers for the entire app are being run.
but perhaps static initializers for the entire app are being run.
Dave Dyer
May 3, 2017, 12:46:13 PM5/3/17
to CodenameOne Discussions
One bandaid that occurs to me is that since you're already running the startup 10 times (or so) to make
all the screen shots, you could just make it one more, and ignore the first run.
Shai Almog
May 4, 2017, 1:05:18 AM5/4/17
to CodenameOne Discussions
It's probable that your static initializers are at fault.
It's a problem specific to your app it doesn't make sense to patch that and hide an actual problem that will probably impact your first install on the device.
It's a problem specific to your app it doesn't make sense to patch that and hide an actual problem that will probably impact your first install on the device.
Dave Dyer
May 4, 2017, 2:26:09 AM5/4/17
to CodenameOne Discussions
it it is basically the sheer size of the app, there's not a lot I can do about that.
How about an option to let me supply the splash screens?
How about an option to let me supply the splash screens?
Shai Almog
May 5, 2017, 12:49:28 AM5/5/17
to CodenameOne Discussions
There is an option to let you supply splash screens.
Reply all
Reply to author
Forward
0 new messages