Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2018.4.X, 2019.3.X
Votes
0
Found in
2018.4
2018.4.10f1
Issue ID
1190454
Regression
No
[iOS] Safe area resets to zeros after custom view is presented on iOS 13
Steps to reproduce:
1. Open attached "CustomViewRepro.zip" project
2. Build for iOS and deploy the Xcode project to the iOS device
3. Observe screen.safeArea.y value
4. Press on "SHOW VIEWCONTROLLER" button
Expected result: Screen.SafeArea values are the same after opening custom view
Actual result: Screen.SafeArea values become zero when custom view is opened (screenshots "before" and "after" attached)
Reproduced in: 2018.4.11f1
Devices reproducible with:
- iPhone X (iOS 13.0)
Devices not reproducible with:
- iPhone X (iOS 11.3.1)
- iPhone 7 (iOS 12.3.1)
- iPhone X (iOS 12.4)
- iPad Pro (iOS 13.0)
Note: Could not test on version other than 2018.4, because custom view does not show up properly.
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
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
Resolution Note (fix version 2018.4):
Fixed in 2018.4.22f1