Search Issue Tracker

Fixed

Fixed in 2021.3.31f1, 2022.3.11f1, 2023.1.16f1, 2023.2.0b12, 2023.3.0a6, 7000.0.0a1

Votes

15

Found in

2021.3.28f1

2022.3.4f1

2023.1.3f1

2023.2.0a23

2023.3.0a4

7000.0.0a1

Issue ID

UUM-41818

Regression

No

[iOS] Screen.safeArea is incorrectly updated when rotating the device

--

-

How to reproduce:
1. Open the attached Project "SafeArea-unity"
2. Build and Run the Scene "SampleScene" on iOS
3. Observe the orange area on the device
4. Rotate the device
5. Observe the orange area on the device

Expected result: The orange area does not cover the notch of the device
Actual result: The orange area covers the notch of the device

Reproducible with: 2021.3.28f1, 2022.3.4f1, 2023.1.3f1, 2023.2.0a23

Reproduced on:
- iPhone 12 mini (iOS 14.1)
- iPhone 13 (iOS 15.0)

Comments (7)

  1. Maxon0407

    Oct 12, 2023 07:00

    Have that issue in 2022.3.1f1

  2. marvpaul

    Oct 04, 2023 06:46

    Faxing this issue in 2022.3.10f1

  3. mathiassnail

    Sep 03, 2023 06:08

    Hoping this gets merged soon, so we can release our portrait mode update 🤞

  4. AnawikiGames

    Aug 30, 2023 11:31

    It still doesn't work. iPhone X here.

  5. MauriceAbraham

    Aug 20, 2023 11:39

    Correction: I meant to say it was working in 2021.3.20f1.

  6. MauriceAbraham

    Aug 19, 2023 00:34

    To say that this is not a regression is misleading, since the safe area was correctly updating in version 2022.3.20f1. Now, when the device is rotated, it gets the screen width and height correctly, but adjusts using the safeAreaInsets from the original orientation, not the current orientation.

  7. rumorgames

    Jul 27, 2023 19:06

    This bug is STILL not fixed as of 2021.3.29f1.

    It's insulting this even has to be reported, let alone voted on. There are a number of similar reported issues going back years that vacillate between fix and regression. How is it possible that Unity doesn't even have the most basic of regression tests to ensure that essential APIs targeting core platforms perform as expected? What an embarrassment for such a visible and customer-facing issue to get blown off again and again.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.