Search Issue Tracker
By Design
Votes
1
Found in
2019.4
2020.3
2021.2
2021.2.15f1
2022.1
2022.2
Issue ID
1411013
Regression
No
[Mobile] Screen.resolutions returns empty array on iOS/Android devices
How to reproduce:
1. Open the attached "1411013_Repro.zip" project
2. Build and run the Scene "SampleScene" on an iOS or Android device
Expected results: A list of supported/native resolutions are shown
Actual results: "Array is empty" text is shown
Reproducible with: 2019.4.37f1, 2020.3.31f1, 2021.2.17f1, 2022.1.0b13, 2022.2.0a8
Reproducible with:
VLNQA00313, Huawei Y6 Ⅱ Compact (HUAWEI LYO-L01), Android 5.1, CPU: MediaTek MT6735, GPU: Mali-T720
Samsung S5 - User
Samsung S6 - User
iPhone 13 mini (iOS 15)
iPad 6th generation (iOS 14.4.2)
Not reproducible with:
VLNQA00391, Xiaomi Redmi 9A (M2006C3LG), Android 10, CPU: MediaTek Helio G25 (MT6762G), GPU: PowerVR Rogue GE8320
----------, Oppo Reno Z 中国版 (PCDM10), Android 11, CPU: NOT FOUND, GPU: PowerVR Rogue GM9446
VLNQA00335, Samsung Galaxy S20+ 5G (SM-G986B), Android 10, CPU: Exynos 990, GPU: Mali-G77
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
We can only report supported resolutions since Android API level 23, while we can't at all for iOS.