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.
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
SampsaPlaysome
Nov 04, 2020 11:43
How is this not fixed yet? Makes differentiating between incremental builds really tedious