Describes how to use the charts and info presented on the Quality page. We track the percentage of customers who are experiencing failures (crashes, unresponsive events, and JavaScript exceptions) and the most common causes of the issue.
To view the Quality page:
-
Go to your Dashboard and find the app.
Note You can view your app's quality only if it is listed in the Store and appears below the Apps in the Store title.
- Click Details in the app's tile to see the App summary page.
- In the left menu, click Quality to see the app's quality info.
- Review the filters at the top of the page and set the criteria of the apps that you want to review.
Note In order to view app quality data, you must enable telemetry data collection for your account. If you have not been not collecting telemetry data and then enable it, it might take several days before you start to see telemetry data.
The failure rate data comes from a sampled set of customers. This sample is designed to closely represent the actual customers who have installed the app, and is not limited to those who have experienced failures. The data only considers failures that occurred during the initial period of usage.
Note You may see a warning that the sample set is not statistically significant. This means that we have not yet obtained enough data yet to consider it an accurate representation of your app's quality and performance.
Downloadable .cab files
If you build your app's package with debugging data to make an .appxupload package, .cab files will be available for the most common failures. A Download link in the table indicates that a .cab file is available. You can download the .cab file and open it in the Microsoft Visual Studio debugger to get more information about the problem. For more information, see Debugging and testing Windows Store apps.
JavaScript exception rate
When a JavaScript exception occurs (in an app that uses JavaScript), it is recorded and tabulated.
The chart displays the average rate that these exceptions occurred per computer per day. The table lists the most common exceptions for which we've collected data.
Crash rate
When an app exits unexpectedly, a crash is recorded along with the location in the program code where the crash occurred.
The chart displays the average crash rate per computer per day. The table lists the most common places where a crash occurred and for which we've collected data.
App unresponsive rate
When an app stops responding to user input, an unresponsive event is recorded. The app's module in which the event occurred is also recorded.
The chart displays the average unresponsive rate per computer per day. The table lists the most common places where the app has become unresponsive and for which we've collected data.
Remarks
In cases where the majority of your app's customers are experiencing failures, you will see a list of failures in the table, while the failure rate may display as zero (since customers may not have been able to use your app long enough to be included in our sampling).
By reviewing your quality data, you can understand issues customers may be experiencing with your app, and fix them in your next version. By comparing the quality reports from one version of your app to the next, you can determine if customers are having a better experience with later versions.
All dates and times used in the analytics reports, charts, and downloaded data are shown in UTC.
Build date: 3/19/2013
