Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2017.4.X, 2018.4.X, 2019.3.X, 2020.1.X
Votes
0
Found in
2018.4.18f1
Issue ID
1225171
Regression
Yes
[2018.4] A grey screen fades in between the storyboard launch screen and the first Unity scene
Reproduction steps:
1. Open attached project "Project.zip"
2. Change the platform to iOS and Build
3. Open the info.plist in the Xcode generated project. You will see that the "Launch screen interface file base name" field is set with "OriginalsSplash.storyboard"
4. Build and Run the Xcode project on a device
Expected result: There should be no grey screen between the storyboard launch screen and the first Unity scene.
Actual result: You will see a gray screen between the storyboard launch screen and the first Unity scene.
Reproduces on: 2018.4.18f1, 2018.4.19f1
Does not reproduce: 2018.4.17f1
Devices reproduced on:
iPhone 11 iOS 13.3.1
iPhone 6S iOS 13.3.1
Note: Changing the "Launch screen interface file base name" field in the .plist with "OriginalsSplash" fixes the issue
Comments (1)
-
AcidArrow
Apr 20, 2020 19:35
Please note that the workaround suggested does fix this issue, but it makes the orientation issues come back (where the orientation of the launch screen is wrong for a bit before switching to the correct one).
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android][BiRP] Depth processing is handled incorrectly on certain Android devices when using 2 camera's
- [APV] Cancelling Display Dialog Error is thrown after Adaptive Probe Volumes tab is open in Lighting Window
- [APV] NullReferenceException is thrown when baking Adaptive Probe Volume for a Terrain with Non-GI Contributing Tree Prototypes and multiple APV objects with different LayerMasks are present on the scene
- Hands are not recognized when using Hololens 2
- "OnTriggerExit2D" is called before "OnTriggerEnter2D" when object is destroyed immediately
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a5
Resolution Note (fix version 2017.4):
Fixed in 2017.4.38f1