Android C++ project black screen when packaged for shipping
When packaging a game for android with the shipping build configuration and for distribution ticked, the app (Whether loaded from a bat file or from the store directly) will always show a non-interactive black screen if launched for a second time onwards. The first time the game is launched the OBB verifier will run and the game will almost always launch as normal (I say almost, as there is a rare chance of it crashing or black screening here too), but any subsequent time will always result in a black screen with the only confirmed solution to be reinstalling the app. Disabling the OBB verifier causing the black screen to happen on first startup as well, although from the look of logcat the verifier is still packaged with the game, just not run.
This has been tested on an LG G3 and G2, and while killing a Google Play Service instance on the G2 appears to have allowed subsequent running of the game in one instance, this could not be replicated on the G3 or later on on the G2. This black screen also occurs regardless of whether Google Play services are actually enabled in the game or not (And the Google Play logon popup will not display on subsequent launches either). When the black screen happens, I do notice that the back button rotates to landscape, but no further progress is made after that.
Logcat doesn't seem to provide any much useful data aside from the suspicious lines below (The actual package name has been replaced):
(The lines above repeat a few times)
(I couldn't find any details about 'sudhakar' and there are no references to it when other apps launch, although this line is an error. Could this be an issue with not starting with 'com.'?)
(This is the last reference to the app until details about the user closing it)
Any potential insight into the cause would be greatly appreciated as reinstalling the app every time it needs to be run is proving a massive pain for our alpha testers.
asked Jun 12 '15 at 09:56 PM in Bug Reports
We have not heard back from you in a few days, so we are marking this post as Resolved for tracking purposes. If you are still experiencing the issue you reported, please respond to this message with additional information and we will offer further assistance.
answered Jun 22 '15 at 01:16 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here