My app has some bugs that show up in the health report. I was able to squash one, but there are a few others that I am having trouble interpreting. Is there any way to send exception information to the Store's Health report, so that I can know what part of the code is crashing. Have the health report, instead of gibberish like,,, STOWED_EXCEPTION_System.InvalidOperationException_80131509_EssentialVideoRecorder.dll!RHBinder__ShimExeMain I can see a message that I created, so that I'll know what is doing what. Thanks, John. PS
Is there any way to send exception information to the Store's Health report, so that I can know what part of the code is crashing
The event is logged in OS when your app crashes and the device will send the event to the Windows Store central crash reporting system. But to minimize network and CPU impact, only core crash meta data (like OS, app version and function failed) will be sent. You could follow the steps below with Health report to debug your app:
• Filter the page by Package Version (in the top of the page), to find the latest crashes
• Filter the trend graph by OS version and market to narrow down issues
• Review the breakout charts to determine if the issue corresponds to a particular OS version or device characteristics
• Once you have narrowed the issue to a particular version of the app, OS or device, go to the Failure Log to view stack traces and diagnose the possible source of the issue
More info, please look into this blog.
Alternatively, you can programmatically retrieve this data using the Windows Store analysis REST API. See Get error reporting data.