Search Issue Tracker
Fixed
Fixed in 2022.3.23f1, 2023.2.16f1
Votes
0
Found in
2022.3.22f1
2023.2.15f1
Issue ID
UUM-67255
Regression
Yes
[Android] Splash screen is rendered outside the safe area when "Render outside safe area" option is set to false
Reproduction steps:
1. Open the attached project “ReproProject”
2. Ensure “Render outside safe area” is not marked at (menu: Edit > Project Settings > Player > Resolution and Presentation)
3. Build And Run on Android
4. Observe the app behaviour
Expected result: The splash screen doesn't cover the entire safe area of the screen
Actual result: The splash screen covers the screen safe area
Reproducible with: 2022.3.10f1, 2022.3.22f1, 2023.2.0b10, 2023.2.15f1
Not reproducible with: 2021.3.36f1, 2022.3.9f1, 2023.2.0b9, 6000.0.0b12
Reproducible with this device:
Pixel 4a Qualcomm SDM Snapdragon 730G (SM7150-AB), Adreno 618 (user's)
VLNQA00318, Oneplus OnePlus 7 Pro (GM1913), Android 11, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00231, Samsung Galaxy A5(2017) (SM-A520F), Android 8.0.0, CPU: Exynos 7 Octa 7880, GPU: Mali-T830
VLNQA00332, Samsung Galaxy XCover4 (SM-G390F), Android 9, CPU: Exynos 7 Quad 7570, GPU: Mali-T720
Not reproducible with these devices:
VLNQA00518 - Google Pixel 4 (Pixel 4), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 12
VLNQA00414 - Galaxy Note10+ 5G (SM-N976V), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 9
VLNQA00591 - Samsung Galaxy S23 (SM-S911B), CPU: Snapdragon 8 Gen 2 (SM8550), GPU: Adreno 740, OS: 14
VLNQA00278 - Xiaomi Redmi Note 7 (Redmi Note 7), CPU: Snapdragon 660, GPU: Adreno 512, OS: 9.0.0
VLNQA00139 - Vivo Xplay6 (vivo Xplay6), CPU: Snapdragon 820 MSM8996, GPU: Adreno 530, OS: 7.1.1
VLNQA00132 - Xiaomi Mi 5s (MI 5s), CPU: Snapdragon 820 MSM8996, GPU: Adreno 530, OS: 6.0.1
Testing environment: Windows 11 23H2 (22631.3007), Windows 11 (10.0.22621) 64bit (user’s)
Not reproducible on: No other environment tested
-
paradizIsCool
Nov 26, 2024 11:26
It seems similar issues are back with 2022.3.53.
My game does not render outside the safe area with 2022.3.38, but it does with at least 2022.3.52 and later. -
Fugo_Games
Jul 23, 2024 13:03
This caused Screen.safeArea to be (0,0,width,height) and Screen.cutouts to be empty arrays in some android devices (S20,S21,S22,S23) even though those phones have cutout areas and they had correct safe area values before.
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
- Standalone Player crashes with "TDerived GetOrLoad<TDerived>() where TDerived : T" when IL2CPP Code generation is set to "Faster (smaller) Builds"
- IndexOutOfRangeException and InvalidOperationException when logging XML string
- Script missing in "Assets/Settings/Mobile_Renderer/GlobalVolumeFeature" of "com.unity.template.urp-blank" template
- “Font Asset Creator - Error Code [Invalid_File_Structure]…“ error is logged when generating Font Assets from fonts with meta files from previous Editor versions
- Input.mousePosition returns (NaN, NaN, 0.00) when Scene view is opened
Resolution Note (fix version 2023.2.16f1):
Android: Splash screen size is set properly when "Render outside safe area" is false.
Resolution Note (fix version 2022.3.23f1):
Android: Splash screen size is set properly when "Render outside safe area" is false.