Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2018.4.X, 2019.1.X, 2019.2.X
Votes
3
Found in
2018.3.0b7
2018.3.12f1
2019.1.0a1
2019.2.0a1
Issue ID
1144669
Regression
Yes
[Android] Android 9 devices with a notch are not in full screen, black bar is visible at the bottom of the screen
Steps to reproduced:
1. Open user attached project
2. Build & Run the project
3. Observe the black bar at the bottom of the screen
Expected result: devices with a notch should be in full screen, black bar should not be visible at the bottom of the screen
Reproduced in: 2019.2.0a11, 2018.3.12f1, 2018.3.0b7
Not reproduced in: 2018.3.0b6, 2018.2.21f1
Regression since: 2018.3.0b7
Devices under test:
Reproduced:
N/A, Xiaomi POCO F1 (POCOPHONE F1), Android 9, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
VLNQA00230, Oneplus OnePlus6T (ONEPLUS A6013), Android 9, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
No repro:
VLNQA00138, Huawei P20 Pro (CLT-L29), Android 8.1.0, CPU: HiSilicon Kirin 970, GPU: Mali-G72
VLNQA00136, Samsung Galaxy S9+ (SM-G965F), Android 8.0.0, CPU: Exynos 9 Series 9810, GPU: Mali-G72
VLNQA00101, Samsung Galaxy Note8 (SM-N950U), Android 8.0.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
iPhone Xs iOS 12.0
Comments (1)
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
- Different custom Shader behavior when GPU Resident Drawer is enabled
- InvalidOperationException occurs when binding 3D Rendertexture or 2D RenderTextureArray as Multiple Render Texture in RenderGraph
- Adaptive Probe Volumes Fails to Bake with Dilation Enabled and exception "Cannot allocate more brick chunks, probe volume brick pool is full" is printed
- AssertionException thrown and Mesh turns invisible when changing Material Offset manually via the Inspector or through SetTextureOffset() on a Mesh with more than one Material
- NavMesh is not usable when using empty Bounds in BuildNavMeshData
firetrap
Apr 23, 2019 10:08
Tested with devices without notch but with android 9 and i can reproduce the same issue.