For some reason, it's good to have extra information when the application is crashing, As an example logged in username or Id.
I can see custom property exists when we want to send exception trace but this is not the case when the application is crashing. It's good to have some default set property at initializing time then we can see the value of property all the times in any crashes.
I can see something similar exists in other platforms
https://firebase.google.com/docs/crashlytics/customize-crash-reports?platform=unity
Hi there!
I can definitely see why this would help when application crashes. I'm going to add the product owners of our Diagnostics service to that they can look into this further.
Seconding this, I would always like to include some default information with the error report anytime my application crashes.
Hey there! We support attaching custom data to crash reports with User ID or via attachments. Do these features address your needs?
Unfortunately, key value pairs (custom properties) are only supported for handled exceptions at this time.
For my use case (enterprise related) we are looking to track a crash to a specific user/device, where users have a pre-assigned enterprise userId and deviceId that is different than an AppCenter identifier. I am using the crash attachment functionality to upload the mobile application database with user/device identifiers in it, but in order to link the crash to a user, I have to download the database for a given crash, open it and find/compare the unique information inside. Often times a user will indicate they experienced a crash at a certain spot or time in the application, and we want to find the associated crash report in AppCenter to attempt to triage. This process would be much quicker if properties could be associated to individual crash reports. An enhancement on top of that would be the ability to query for property values on individual crashes.
Edit: I see UserId is settable - that may help me a good bit. Thanks for the link.
This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment.
Any update here?
Most helpful comment
Hi there!
I can definitely see why this would help when application crashes. I'm going to add the product owners of our Diagnostics service to that they can look into this further.