Search Issue Tracker
Fixed in 2019.1.X
Votes
0
Found in
2019.1.0a10
Issue ID
1103404
Regression
Yes
[Android] App shows black screen when built without "Use 32-bit Display Buffer" option
App shows a black screen when built without PlayerSettings > Resolution and Presentation > Use 32-bit Display Buffer
Steps to Repro:
1. Open attached project
2. Open PlayerSettings > Resolution and Presentation
3. Uncheck "Use 32-bit Display Buffer" option
4. Connect a device to PC
5. Open Build Settings > Build and Run
Actual Result:
App screen goes black and Unity Splash Screen is never loaded
Expected Result:
The game should open correctly to the empty scene
Occurring with:
2019.1.0a10
Working with:
2019.1.0a9, 2018.3.0b12
Reproducible on device
1. Samsung Galaxy S4 mini, OS: 4.4.2, CPU: (ARMv7 32 bit) Qualcomm MSM8930AB Snapdragon 40, GPU: Adreno 305
2. Google Pixel 2, OS: 9, CPU: Octa-core (4x2.35 GHz Kryo & 4x1.9 GHz Kryo), GPU: Adreno 540
3. Samsung Galaxy S7 Edge, OS: 7, CPU: Quad-core 2.3 GHz Mongoose + quad-core 1.6 GHz Cortex-A53, GPU: Mali-T880 MP12
Environment:
Windows and Mac
Error StackTrace from Android Studio:
Check attached file
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- NullReferenceException is thrown when assigning PanelSettings asset to a UIDocument dynamically at runtime
- Crash on GfxDeviceD3D12Base::DrawBuffersCommon when disabling "Allow FSR2" parameter while in Play Mode with Direct3D12 set as graphics API
- Crash on vkGetInstanceProcAddr when setting graphics API to "Vulkan" on Fantasy Kingdom learning project
- Overlay Camera "clear depth" not working on Vulkan+Pixel8
- Shadows from Shadow Caster 2D using 2D Colliders show incorrectly when tiles are removed at runtime
Add comment