Search Issue Tracker
Fixed
Fixed in 2021.3.25f1
Votes
1
Found in
2021.3.24f1
Issue ID
UUM-25333
Regression
No
[iOS] Screen.safeArea returns incorrect values with Xcode 14.1
How to reproduce:
1. Download and open the attached project
2. Build and deploy the project to iOS
3. Observe the Xcode console
Expected outcome: Screen.safeArea returns a positive "y" value
Actual outcome: Screen.safeArea "y" value is returned as a zero
Reproducible with: 2020.3.44f1, 2021.3.17f1, 2022.1.24f1, 2022.2.3f1, 2023.1.0a26
Reproduced with: iPhone 6S (iOS 13.3.1), iPhone 12 Pro (iOS 14.2.1)
Comments (2)
-
mwalus
Jun 13, 2023 12:48
Hello. When this fix will be propagated to 2022.3 LTS?
-
mwalus
May 10, 2023 06:05
Hello.
I do have same issue. SafeArea value is not updated after rotating of device thus it is not possible to render UI correctly (i. e. controls are below top notch).Cant wait for fix.
BR
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
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- Addressables Profiles and Analyze windows no minimum window size
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “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
Resolution Note (fix version 2021.3.25f1):
Doesn't reproduce in 2021.3.25f1