Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2018.3.X, 2018.4.X
Votes
1
Found in
2017.4.0f1
2018.2.16f1
Issue ID
1102732
Regression
No
[iOS] Screen.safeArea does not change when Screen.width and Screen.height are changed using Screen.SetResolution
Screen.safeArea is using original device resolution and not current resolution so changing resolution using Screen.SetResolution does not change Screen.safeArea
To reproduce:
1. Download attached project "BugUnityProject.zip" and open in Unity
2. Open "SampleScene" scene
3. Build for iOS
4. Deploy the Xcode project to the iOS device
5. Press button "Set Resolution 320x480" or "Set Resolution 640x960"
Expected results: Current resolution changes and Screen.safeArea changes with it
Actual results: Current resolution changes, but Screen.safeArea remains the same as on start
Notes:
- This issue does not reproduce on Windows Standalone, macOS Standalone, and Android (Mono)
- Could not check on Android (IL2CPP) because build fails - Errors are shared in Comments section
- You can force Screen.safeArea refresh by changing the orientation
Tested with:
- iPhone SE, iOS: 11.4.1 - Reproduced
- iPhone 7s Plus, iOS: 12.0 - Reproduced
Reproduced on Unity 2017.4.0f1, 2017.4.16f1, 2018.1.9f2, 2018.2.17f1, 2018.3.0b11 and 2019.1.0a10
Comments (7)
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
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
- Previously deleted “DefaultLookDevProfile“ is present when upgrading the Editor version
- [Ubuntu] UI text and buttons are missing spaces in Unity Version Control > New Workspace window
- "Inherit attribute is not supported" warning is shown but attributes are available in VFX Graph Output and Update blocks
ameliafernandez404
Dec 28, 2020 15:31
Yes i am also facing this problem can anybody help me out ?
GravityJack
Jun 20, 2019 00:25
I'm experiencing this issue on 2019.1.7