Short black screen after Default.png

Solar2D iOS
#1

On clicking my app’s icon from an iPhone, the Default.png (or Default@2x.png or Default-568h@2x.png depending on type of iPhone) shows. There is no status bar because I’ve set UIStatusBarHidden = true.

–> Then the Default.png image fades to black and the status bar is visible for half a second.

Then the app’s main.lua loads my app’s main menu and the status bar is hidden due to display.setStatusBar (display.HiddenStatusBar) which is the first line in main.lua

What is accounting for that half a second where the status bar is showing and the screen is black and how can I fix it?  It happens every time I open the app. Thanks so much in advance!

#2

I also noticed that when using the latest daily build (2014.2126) and I think it is bug since I didn’t have that before…

#3

Thanks for replying!

I was using 2014.2122 when I posted this issue.

It also happened to you with 2126.

I tried it with the very latest build - 2135 - and still got this short black screen with status bar before the app loads

So then I just tried 2109 and the bug was not there.

How do we report this officially for Corona to know there’s an issue in the more recent builds?

#4

Hi @ranflas, @Renato,

Please submit a bug report on this to: http://developer.coronalabs.com/content/bug-submission

And remember to attach an entire working sample project that shows it occurring, not just a “main.lua” file. We need to be a bit more stringent about this, since too often we receive a bug case which is simply a “main.lua” file, and the actual issue lies somewhere in the user’s config.lua or build.settings.

Thanks,

Brent

#5

did anyone file a bug report on this ?

I released an app to the store, it suffers from this issue, and it really bugs me every time the app launches.

Cheers,

Tommy

#6

We are having the same issue.

We have not changed anything in the project that is critical and thus could create this behaviour.

I will file a bug with a working example asap.

Btw, we use Corona Enterprise build - 2123

#7

This is a bug and probably related to memory.

The Hello World example from Corona is showing this bug.

The only trick is that this bug it is not always happening. But, when it stops happening, I noticed that If I go to 2-3 other apps and then come back to the app the bug will show again. So, I am guessing that has something do to with memory…

#8

Hi all,

If this appears to be an issue with memory, I’m not sure what we can do about it, since Corona doesn’t have any control over the OS’s memory. What device(s) and OS versions is this occurring on? iOS and Android both? Which test devices within each platform?

Thanks,

Brent

#9

 I believe this is a Corona issue because:

  1. This not happens with other apps, only the ones made using Corona

  2. This was not happening before, so I would guess this is a bug introduced in a daily build

I am running iOS 7.0.4 on a iPhone 5.  I am using Corona 2014.2155 but this was also happening with 2014.2126.

#10

Hmmm… interesting. Do you have any guess which build it was not occurring in, as in, where there was no visible delay?

Thanks,

Brent

#11

Does not appear to be a memory issue.

The problem happens in builds from 2014.2122 through 2014.2135 and probably (untested) through 2156

There is no problem in build 2109 which is what we ended up using.

 

Hope that helps - thanks for working on this!

Been using Corona a lot more lately.

#12

Hi @ranflas,

Thanks for helping to pinpoint this. And this occurs on every Corona app, even “Hello World”, after you run some other apps and then return to the Corona app? I assume you’re force-closing the Corona app (thus cold-starting it) not resuming it from the backgrounded state?

Brent

#13 
And this occurs on every Corona app, even "Hello World", after you run some other apps and then return to the Corona app?

Yes. Just use a white Default-568h@2x.png and also use a white background (otherwise so you would not see the black screen between the Default-568h@2x.png and the app background.)

I assume you're force-closing the Corona app (thus cold-starting it) not resuming it from the backgrounded state?

Yes, you need to close the Corona app. Resuming from background doesn’t show the bug.

Just a clarification, I didn’t say that it was a memory bug, I said that is may have something related to memory, since it usually happens at the first time you open the Corona app. If you force close and open the Corona app in a row, usually the bug does not appear (at least for me). So I just go to other apps and then open again the Corona app and the bug appears.

#14

Obviously this requires building to the device to check for the error.

Feel free to test with “Hello World” on 2109 to see it working properly and 2122 to see the bug introduced.

The prototype I was working with was not much more than a few labels and buttons, but I did not try “Hello World”

I did force-close Corona when I was testing it.

It had nothing to do with running other apps and then coming back to this app - the half a second black screen with status bar happened every single time the app was opened (not resuming from the background state)

#15

One more note, from our experiences, we also have encountered this issue when we build (using enterprise) for android devices!

Tested Device: HTC Desire C

So this is not (in our experience) and iOS bug only

#16

I am always seeing this, however i didn’t think it was a bug until i read this thread, and i suppose its been a bug for a very long time because i have always noticed this…

#17

I’ve observed this issue on v2013.2100 of the Corona SDK only on Android and not on iOS, so not sure if this is indeed a bug in Corona or is there a configuration setting required to fix this. Any help on this would be appreciated though!

#18

I also noticed that when using the latest daily build (2014.2126) and I think it is bug since I didn’t have that before…

#19

I’m seeing this on iOS devices with an app built with Corona Daily Build 2153.

In my case, it happens every time I launch the app.  

If I launch the app, tap on home button, start another app, and the tap the home button, then tap on my app’s icon, it simply shows the last screen I was at, and no black screen.  

However, every time I restart the app (that is, fresh restart with Default png showing), immediately after the Default.png is displayed, I see a black screen long enough to be bothersome.  It’s not just a flicker of blackness.  It is a solid black screen with the status bar.  Please note, the very first line of code I have in main.lua is display.setStatusBar( display.HiddenStatusBar )

I have not tested my latest project with pre-Graphics 2.0 daily build, so I cannot say if this would still happen with older daily build.   That said, I haven’t seen this happen with my already released app made with pre-Graphics 2.0 version.   In addition, I haven’t done anything unusual with my latest project – only difference between this project and previously released apps are the use of latest widget and composer. 

Edit:  According to ranflas, this does not happen with daily build 2109, and vgtrnd mentions this happens with daily build 2100 on Android.   I’m not sure exactly when this issue was introduced, but it definitely did not exist in pre-Graphics 2.0 build.  I think it’s worth looking into this and get it fixed sooner than later.

Naomi

#20

I just built a test app and installed it on my iPad 4 using 2169.  I have a Default.png and Default@2x.png in my test.  I don’t have the iPad specific versions.  In my app, these are the first few lines:

display.setStatusBar( display.HiddenStatusBar )

local bg = display.newRect(display.contentCenterX, display.contentCenterY, display.contentWidth, display.contentHeight)
bg:setFillColor(1,1,1)

When I build and run this, I get no black screens.  I’ve upgraded my iPhone to 7.1 beta, so I’m going to have to update my Xcode before I can try it there.

I repeated the test on 2100 and I’m also not getting a black screen in between.  Now by default Corona SDK has a default black screen.  If you take too long to get something displayed, you’re going to get some black frames until Corona SDK has something to render.

I can’t reproduce this.

Rob