Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2018.3.X
Votes
0
Found in
2018.3.0a5
2018.3.0a6
Issue ID
1064440
Regression
Yes
[Android] Crash on start if Auto Generate Lighting is enabled
Steps to reproduce:
1) Download attached project and open in Unity
2) Check the Lighting tab and make sure Auto Generate lighting is enabled
3) Build and Run project on a device
Observe the crash
Reproduced with:
2018.3.0a5, 2018.3.0a6
Not reproduced with:
2018.2.1f1, 2018.3.0a4
Devices under testing:
Reproduced with:
VLNQA00126 Samsung SM G800F (Galaxy S5 Mini)*, OS:6.0.1, CPU:armeabi-v7a, GPU:Mali-400 MP
Not reproduced with:
VLNQA00030 Lge LG D802 (G2)*, OS:4.4.2, CPU:armeabi-v7a, GPU:Adreno (TM) 330
VLNQA00036 Motorola XT1032*, OS:5.1, CPU:armeabi-v7a, GPU:Adreno (TM) 305
VLNQA00003 Razer Phone*, OS:7.1.1, CPU:arm64-v8a, GPU:Adreno (TM) 540
VLNQA00101 Samsung Galaxy Note 8, OS:8.0.0, CPU:arm64-v8a, GPU:Adreno (TM) 540
Note: Did not crash if Lighting is generated manually
---------------------------------------------
Fixed in:
2019.1.0a2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Rigidbody2D.Slide API does not have the needed configuration when creating a 2D Top-Down character controller
- Opening reference for "Playables"component redirects to a missing page
- Sprite Renderer image is changed when switching Mask Interaction and changing Sprite to a shared Sprite
- An unsigned integer is not compared with an integer correctly in player when using IL2CPP backend
- Graphical artifacts are being rendered in Scenes that are loaded during run-time when GPU Resident Drawer is turned on
Add comment