1. Navigate to Developer > JS errors. You can view the total number of JS errors, unique issues that caused the reported crashes, unique devices affected, and percentage of exception-free devices (crash free rate) for the selected date range.
   

1. The charts help you visualize the number of errors and the timeline of errors that were reported over the selected date range for the web app.
   
2. As you scroll to the bottom, you will see a list of all the unique issues along with details such as the issue description, the impacted OS version(s), app version(s), the total number of errors, and the total number of affected devices, and comments.
   

Analyze JS error reports

1. Click on the individual issue in the unique issues list to get more details.
   

1. The timeline graph gives you the total number of JS errors that happened and the unique number of affected devices over time. You can view stats like the number of JS errors caused by the unique issue, the affected devices, and the latest affected app version.
2. The other graphs give you an idea of the affected devices, OS versions, and app versions.
   
3. You can find the all stack trace threads to help you debug and solve the issue. 
   
4. You can also view the full stack trace with raw data about the issue by clicking on the <> Raw text button.
5. Click on js_error_trace.log to download the JS error log file if required for further analysis.
   

Analyze individual crash instances

1. Click on Show list in the JS error details page and you will see a list of all the crash instances that happened due to the unique issue.
   
2. The list includes details such as the affected device model, app version, OS version, device ID, time at which the crash happened, and the time at which it was received in Apptics.
   

1. Click on the individual JS error instance to view the device timeline. It shows details of all the error instances reported for the device.
   

1. The device timeline will give you the details on the device-specific information such as:
   
1. Apptics SDK version
   
2. App version
   
3. OS version
   
4. Network EDGE
   
5. Device Id
   
2. Click PII is available to get the user info like the user ID and email ID (if available).
   
3. Click on View custom properties to check if any custom attributes have been tracked for the particular crash.

Analyze breadcrumbs and session data

Drill down further and analyze session data — the traces of the events, API calls, and screens that were triggered in during the session in which the error instance happened. You can click on View user session details to view data for all the sessions associated with the device ID (and user ID if available).

1. The events trace shows the events that occurred when the issue occurred.
2. The API calls trace shows the list of all the API calls that were triggered while the issue occurred
3. The screes trace shows the list of all the screens that were visited when the issue occurred.