Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2017.4.X, 2018.2.X, 2018.3.X
Votes
0
Found in
2017.4.11f1
Issue ID
1085662
Regression
No
[iOS] Wrong Screen.safeArea on iPhone on Start()
To reproduce:
1. Open attached project "test.zip"
2. Open "scene.unity" scene
3. Build for iOS
4. Deploy Xcode project to iOS device
5. Observe in the top right corner Screen resolution(first line) and Safe area(second line), safe area on Start() is reported bigger than screen resolution
Expected result: Screen.safeArea is shown that same as screen resolution or small on Start()
Actual result: Screen.safeArea reports bigger than the screen resolution on Start()
Reproduced on:
2017.4.12f1 2018.1.9f2 2018.2.11f1 2018.3.0b4 2019.1.0a3
Device reproduced on:
iPhone 7 Plus iOS 12.0
Notes:
Didn't seem to reproduce on:
VLNQA00144, Samsung Galaxy S9 (SM-G960U1), Android 8.0.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
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
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
shubhamswaraj2021
Aug 19, 2020 13:29
good one <a href="https://www.lyricsauto.com">lyricsauto</a>
kilicbatuhan1205
Dec 01, 2019 11:49
Still not fixed in Unity 2018.4.13f1 LTS.