Diagnostics Features

In this section, you will learn about the feature set available for the App Center’s Diagnostics service.

Crash and Errors Analytics

In App Center Diagnostics, you can view analytics data generated automatically by App Center to understand when a crash or error occurs in your app.

By default, App Center displays an app's crashes and errors per day in a side by side view.

Using the top-left tabs, drill down into Crashes and Errors. When you do this, the left chart indicates the number of crashes/errors per day, and the right chart shows the number of affected users. Filter the charts by app version, time frame and status for a more focused view.

App Center shows you analytics on crashes and errors


App Center Diagnostics groups crashes and errors by similarities, such as reason for the issue and where the issue occurred in the app. For each crash and error group, App Center displays the line of code that failed, the class or method name, file name, line number, crash or error type and message for you to better understand these groups at a glance. Select a group to view more information, and access a list of detailed issues reports and logs. This allows you to dive even deeper and use our feature set to better understand your app's behavior during a crash or an error.

App Center groups crashes and errors based on similarities

User Identification

App Center Diagnostics allows you to attach a user ID to your crashes and errors. To do so, use the App Center SDK in your targeted platform Android, Apache Cordova, iOS, macOS, React Native, tvOS, Unity and Xamarin. You will find the user ID associated to a crash or error when clicking on an issue inside of a group.

After attaching a user ID, you can use App Center's search feature to search for crashes with the specified ID. Learn how to do this by following App Center's search documentation.


User ID is not yet supported for WPF, WinForms, and UWP applications. Visit our diagnostics limitations page and our proposed Windows plan for more details.


In the App Center Diagnostics UI, you can attach, view and download one binary and one text attachment to your crash reports.

You can learn how to add attachments to your crash reports by reading the SDK Crashes documentation for your Android, Apache Cordova, iOS, macOS, React Native, WPF/WinForms and Xamarin apps.

To view and download the attachments, select a crash group, a specific device report and then click on the attachments tab.

App Center allows you to add attachments to your crash and error reports

Events Before A Crash

Track events leading up to a crash to capture useful information about the state of your app.

To define a custom event, check out our SDK Documentation for Android, iOS, macOS, React Native, Windows and Xamarin.

To view events before a crash, select a crash group, a specific device report, and then click on the events tab.

App Center allows you to track events leading up to your crash

Key Value Pairs

Xamarin developers can tailor the error report sent to App Center to include additional context for the error by passing a dictionary of string values (as key/value pairs) to the TrackError method. These properties are completely optional.

For example:

    using (var text = File.OpenText("saved_game001.txt"))
        Console.WriteLine("{0}", text.ReadLine());
catch (FileNotFoundException ex)
    Crashes.TrackError(ex, new Dictionary<string,string>{
        { "Filename", "saved_game001.txt" },
        { "Where", "Reload game" },
        { "Issue", "Index of available games is corrupted" }

Here the full exception (ex) is sent back to the App Center service, plus a dictionary containing additional debugging information as well.


This feature is only supported for Xamarin Errors today.

Export Diagnostics Data

App Center can export diagnostics (crashes and errors) raw data to Azure. Export diagnostics data to Blob Storage for customization of the data.

To export crashes, attachments and errors, you must call the Export Configurations API:

POST /v0.1/apps/{owner_name}/{app_name}/export_configurations

In the exportEntities field of the API property, you must indicate what type of data you wish to export: crashes, errors, attachments. When doing so, the full symbolicated crashes and corresponding stack traces will be exported.

Learn more about the benefits of, and how to export your data in the export documentation.


In a crash report, you can see the current threads that were active when the app crashed. The thread that crashed is highlighted in red for you to better understand the state of the app.

App Center shows you current threads at the time of the crash


Only the main thread at the time of the error will be available for WPF and WinForms reports

Configure Alerts

Stay on top of your crashes by configuring your App Center app definition settings to send an email when a new crash group is created. To configure these alerts:

  1. Log into App Center and select your app
  2. In the left menu, navigate to Settings
  3. Click on Email Notifications
  4. Select the box next to Crashes

App Center shows you current threads at the time of the crash

You can learn more about notification in our App Center dashboard documentation.

Create a Bug Tracker

You can integrate third party bug tracker tools with App Center to stay informed and better manage your crashes. Read the bug tracker documentation to learn how to get started.

Set Data Retention

You can set your diagnostics data retention to 28 or 90 days via our APIs, as listed in the App Center API documentation, or in the app settings page. If you change your retention setting from 90 to 28 days, any existing diagnostics data older than 28 days will be removed and any new data will only be stored for 28 days.

If you change your settings from 28 to 90 days, older diagnostics data will not be backfilled. If you would like to store your data for more than 90 days, export your raw data to Azure Blob Storage. Read the export diagnostics data section to get started.

Data retention setting in the app settings page