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
- Frame Debugger is not disabled when switching Scenes if the Frame Debugger window is not open during the transition
- Standalone Profiler Targets another Project if a Standalone Profiler was launched in it before when switching between Edit or Play Mode Targets
- Crash on ForwardRenderLoopJob when opening a specific project
- [Android] Memory leak and eventual crash on Snapdragon 8 Gen 1+ devices when a Clear Pass is executed after Framebuffer Fetch
- PhysicsRaycaster ray length is incorrect when casting from rotated Camera
SampsaPlaysome
Nov 04, 2020 11:43
How is this not fixed yet? Makes differentiating between incremental builds really tedious