Search Issue Tracker
Fixed in 2020.1.X
Votes
1
Found in
Issue ID
1217055
Regression
No
Android App Build is 0 for Crash Reports
1) What Happened?
When receiving a crash report from an Android device, app_build metadata is missing.
2) Steps to Repro
1. Create a Unity project that will generate a crash after starting.
2. Enable Cloud Diagnostics.
3. Build for Android and launch the app.
4. Wait for the app to crash.
5. Restart the app so that the crash report can be sent.
Expected: app_build number is the same as in the Player Settings.
Actual: app_build number is 0.
Does not reproduce on PC or Mac Standalone or iOS builds.
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
- PlayerPropertiesChanged event fires before Player Properties are applied
- Opening Media Pop-out in “Before You Start” Tutorial throws “Styles” and “Styles_Dark” messages in the Console window
- Play Mode Scenario selection/highlight is too long and out of its bounds when the Play Mode Scenario window is opened after maximizing
- Asset name is not shown in the Undo History window when a sprite is modified
- Moving a Tab to a floating window fails when floating windows are docked next to each other
SampsaPlaysome
Nov 04, 2020 11:43
How is this not fixed yet? Makes differentiating between incremental builds really tedious