Search Issue Tracker
Fixed
Fixed in 2020.3.X
Votes
1
Found in
2019.4
2020.3
2020.3.17f1
2021.2
2022.1
Issue ID
1378593
Regression
No
[iOS 15] Screen.safeArea.width returns incorrect value when device's orientation is switched to landscape mode
Reproduction steps:
1. Open the attached project "safeArea.zip"
2. Build and Deploy the project on a device
3. Hold the device in Portrait mode and rotate it to switch to landscape mode
4. Observe the values displayed in the Build
Expected result: The first value in the line "Safe" is smaller than the first value in the line "Real"
Actual result: The first value in the line "Safe" is equal to the first value in the line "Real"
Reproducible with: 2019.4.32f1, 2020.3.22f1, 2021.2.2f1, 2022.1.0a13
Reproduced on:
- iPhone 13 (iOS 15.0)
Does not reproduce on:
- iPhone 12 mini (iOS 14.1)
- iPhone 6 (iOS 12.4.8, safe area is supposed to be equal to actual)
- iPhone 7 (iOS 12.3.1, safe area is supposed to be equal to actual)
-
mhardy
Oct 18, 2023 22:59
Still occurs in 2022.3.10f1 but FIXED in 2022.3.11f1
-
KyryloKuzyk
Aug 02, 2023 10:17
The issue is still present in Unity 2021.3.29f1 LTS: in landscape orientation, Screen.safeArea reports wrong coordinates. This issue is not present in Unity 2020.3.48f1.
iOS 16.5, Xcode 14.3.1
-
PianistaCompany
Jul 28, 2023 10:57
The issue still persists when rotating the screen, even on the 2021.3.28 LTS version. Whether starting in Portrait mode or Landscape mode, the SafeArea continues to retain its unchanged values and does not provide updated results for screen rotation.
-
sotteson
Jul 26, 2023 02:29
Still seeing this regression on 2022.3.5f1.
-
camogram
Jun 29, 2023 02:54
Correction (wrong version): This has regressed in 2022.3.1f1
-
camogram
Jun 29, 2023 02:52
This has regressed in 2022.1.3f1
-
NUTRACTOR
Jun 13, 2023 23:57
This problem recurred in 2022.3.1f1.
If a built app is launched in portrait and then rotated to landscape, the safe area is not updated. -
Julian_Nementic
Feb 14, 2022 15:28
Any news on a potential back-port to 2020.3 LTS?
-
Lukas_1234
Jan 20, 2022 12:32
An estimate on, when or in which version of 2020.3.X this fix will be included, would be great.
It is blocking our iOS release and we were hoping it would be part of Unity 2020.3.26.
-
benlkabam
Jan 13, 2022 16:18
Is there any plans to integrate this fix into the 2019 LTS?
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
- [Dragon Crashers] Build fails in U6
- [Dragon Crashers] 4 Shader error messages on import
- [Dragon Crashers] Readme text is white on light grey
- Cursor stays in front of the first character when entering text in the TextMeshPro field
- Searching in Hierarchy causes unwanted component calls
Resolution Note:
Fixed in 2022.1.0a14
Resolution Note (fix version 2020.3):
Fixed in 2020.3.32f1