We’ve heard several reports that our game does not work on Android Oreo. It launches to a black screen and is unresponsive. This only happens with Oreo that just came out and no other Android version as far as we know.
We’re on Unity 5.6.3. Anyone else experienced this? Is there anything special we should do to ensure Unity works on the new Android version?
I don’t personally have an Oreo device but I’ve had reports from several friends that do as well as lots of 1 star Google Play reviews It was also not working on the Android O beta. The game seems to load to a black screen and just sit there. It doesn’t force close or crash.
We are using Unity Ads and Google Firebase.
I don’t believe anything would be wrong with our build settings but here’s a screenshot of them:
Hey,
I have been able to reproduce the issue you are describing. Even with your project, Chris. Seems that it is related to permissions. Example error “Failed to get permission info for com.sec.android.provider.badge.permission.READ, manifest likely missing custom permission declaration” which means that permissions are undeclared. This issue might be not related to Unity, however, I forwarded a bug to our developers.
Ran into the same issue when building with 5.6.3f1 but the app works properly when built with 2017.1.0f3. The 2017.1.0f3 version shows the runtime permission dialogs but the 5.6.3f1 version does not. After granting the required permissions to the 5.6.3f1 app in the device’s app settings, the app launches successfully.
Unity devs, is there a chance another patch version will be released for 5.6.3 that incorporates the 2017 Oreo permission fix? We’d like to stay on 5.6 for a while longer if possible as we bought the pro license.
Hey @RaceCat ! We got a fix on it’s way that is going all the way down to 5.5. Can’t promise any ETA’s, since updates for different versions come out at different freqiencies.
@akwkong That’s weird… In our testing 2017.1 was affected too. (From bug report: ‘Reproducible: 5.6.3p2, 2017.1.0p5, 2017.2.0b6, 2017.3.0a6’)
Maybe it is just timing and Android O got an update?
Might need to ask @IevaUnity about this.
Looks like I’m having a permissions issue as well on 5.6.3p1. I’m trying to get the location permissions (using an asset called Online Maps from the Asset Store) but the app isn’t asking me for it so Input.location.isEnabledByUser just evaluates to false. I have to manually go into the Settings app and enable it. Hopefully this will get fixed in the next patch as well.
@Evaldas_Unity I tried again with 2017.1.0f3 on my Mac to double check and I saw the runtime permission dialogs on my Nexus 5X running build OPR6.170623.013. I downloaded 2017.1.1f1 and also saw the runtime permission dialogs appear. Happy to hear you are fixing this on versions down to 5.5, thanks!
Yay, I’m not the only one! Any update yet on when a fix will be rolled out to the latest version of Unity?
I was having a very strange bug where randomly during gameplay just the visuals would freeze up and just jitter back and forth between two frames rapidly. The odd thing was that the game was still functional underneath the frozen visuals and if you could manage to load a new scene the issue would resolve (otherwise the game would CTD after a few seconds). Anyone else experienced this issue?
I updated the Android SDK which apparently hadn’t downloaded the 8.0 Oreo update yet, now I can’t get past this black permissions screen bug that everyone is having
Here are some updates:
So, the fix went out to 2017.2.0b11 and should be available in the upcoming days.
The fix will also land in 2017.1.1p2
No set dates for 5.5 and 5.6 (very likely 5.6.3p4) but they are coming : )