Search Issue Tracker
Won't Fix
Votes
0
Found in
6000.1.7f1
6000.2.0b5
6000.3.0a1
Issue ID
UUM-108995
Regression
Yes
The Android Player leaves dedicated space for the system navigation bar instead of occupying the whole screen
Reproduction steps:
1. Open the attached “IN-100673” project
2. Build and Run the Android Player
3. Observe the Android system navigation bar
Expected result: The bar is blue colored
Actual result: The bar is black/white colored
Reproducible with: 6000.1.0a1, 6000.1.7f1, 6000.2.0b5
Not reproducible with: 2022.3.63f1, 6000.0.23f1 (1b875411b5df), 6000.0.51f1
Reproducible environments: macOS 15.5
Not reproducible environments: No other environments tested
Reproducible with these devices:
VLNQA00372 - Galaxy S21 5G (SM-G991U), CPU: Snapdragon 888, GPU: Adreno 660, OS: 12
VLNQA00460 - Google Pixel 6 (Pixel 6), CPU: Google Tensor (Whitechapel), GPU: Mali-G78, OS: 14
VLNQA00403 - Galaxy Z Flip3 5G (SM-F711B), CPU: Snapdragon 888, GPU: Adreno 660, OS: 11
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Resolution Note:
The user project is using the setSystemUiVisibility (https://developer.android.com/reference/android/view/View#setSystemUiVisibility(int)) method, which was deprecated in API 30. Please try using the suggested WindowInsetsController API when launching to devices on API 30 or higher. As the user project uses setSystemUiVisibility and we use WindowInsetsController internally, the combination has undefined behaviour. The change that took place in Unity 6.1 is also necessary for consistant behaviour across API levels. If there is still an issue presenting with WindowInsetsController, please submit a new bug ticket.