Search Issue Tracker
By Design
Votes
0
Found in
2020.3.46f1
2021.3.22f1
2022.1.13f1
2022.3.0f1
2023.1.0b10
2023.2.0a8
2023.3.0a3
Issue ID
UUM-31506
Regression
No
Screen.resolutions returns resolutions that include the notch area when called on Macs with a notch
Reproduction steps:
1. Open the attached “ResolutionRepro” project
2. Go to File > Build Settings
3. Make sure that "Development Build", "Script Debugging" and "Wait for Managed Debugger" are checked and press “Build and Run”
4. When the Player prompts, attach the Debugger to the build through Console Window by pressing Editor and then the Player
Expected result: Resolutions without the notch area are reported
Actual result: Resolutions with and without the notch area are reported
Reproducible with: 2020.3.46f1, 2021.3.22f1, 2022.2.13f1, 2023.1.0b10, 2023.2.0a8
Reproducible on: macOS 13.2.1 (M1 Max, with notch)
Not reproducible on: macOS 12.6 (AMD, without notch)
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note:
Screen.resolutions API is working as designed, because it returns all full-screen resolutions that the monitor supports and these values are obtained directly from the display.