Search Issue Tracker
Fixed in 2018.2.X
Fixed in 5.6.X, 2017.1.X, 2017.2.X, 2017.3.X, 2018.1.X
Votes
1
Found in
5.6.4p3
Issue ID
972995
Regression
No
[iOS] Incorrect splash image is displayed after launching the app on iPhone X
To reproduce:
1. Open project attached by the user (iPhoneXSplashBug)
-- In the player settings notice that for iPhone X different splash was set.
2. Build and run it on iPhone X
3. After app launches notice that firstly green splash is shown (correct behavior) and then it switches to the red one.
Expected result: Only one (green) splash screen should be displayed
Reproduced with: Unity 5.6.3p4, 2017.2.0p4, 2017.3.0f2, 2018.1.0a7
Device: iPhone X iOS 11.2
Fixed in: Unity 2018.2.0a4
Backported to: 5.6.5p3, 2018.1.0b12, 2017.2.2p2, 2017.1.3p3, 2017.4.1f1
Comments (16)
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
- Lights on Renderer Features break when rendering at lower resolution with "Forward+" Rendering Path
- [Android] High GPU usage is reported when the device is rotated into landscape orientation and the application is Vsync bound
- Aspect ratio toolbar doesn’t have tooltip to display contextual help or information when hovering over it
- Particle System isn't playing in Play Mode when it's out of view in Scene view, Simulation Space is set to "World", and Culling mode is set to "Pause and Catch-up"
- [Android] GameObject not rendered when rendering is performed with the help of "BatchRendererGroup"
dmitry-K
Feb 17, 2018 09:56
Still got this bug on unity 2017.3.1p1
amandajohnstonehart
Feb 12, 2018 02:53
Which version will the fix be in (and when)?
wilduser
Jan 22, 2018 18:19
Also not fixed in 5.6.5p1. Will it ever be fixed? You should call it Unity "Amateur" instead of "Pro".
wilduser
Jan 22, 2018 11:22
When is the future release coming out?
wilduser
Jan 12, 2018 14:58
Using 5.6.5f1 and the problem is still not fixed.
peterahou
Jan 08, 2018 13:46
In which version is this fixed? I'm still experiencing the issue in 5.6.5f1