Overview

Crash analytics dashboard

1. Navigate to Developer > Crash. You can view the total number of crashes, unique issues that caused the reported crashes, unique devices affected, and percentage of crash-free devices (crash free rate) for the selected date range.
   
2. The charts help you visualize the number of crashes, the types of crashes, and the timeline of crashes that happened over the selected date range across different platforms.

1. 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), impacted app version(s), the total number of crashes, and the total number of affected devices, and comments.
   

Crash grouping

1. Apptics automatically tracks each crash instance, groups them based on stack traces, and provides unique fingerprints for each crash. This means that you can save time triaging crashes and look into the unique issues behind those crashes.
2. For more clarity, you will see tags beside each unique issue listed in the console. One tag will notify the crash type, while the other tag will specify the app framework for which the crashes are reported, i.e., Native, React Native, or Flutter.
   

For Android, we have Apptics insights, our Android Studio plugin for crash reporting. It brings Zoho Apptics’ crash and error reporting directly into your IDE, allowing you to debug issues without switching tabs. It is available in Jet Brains marketplace alongside the other Android Studio plugins.

Analyze crash 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 crashes and the unique number of affected devices over time. You can view stats like the number of crashes 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.
   

Stack traces

1. You can find the symbolicated stack trace with the current threads by default to help you debug and solve the issue. Click on Show all threads to view the entire stack trace with all the threads. 

1. If you are not able to see symbolicated/deobfuscated stack traces for some reason, click on Symbolicate for iOS, and Deobfuscate
   for Android.

1. You can also view the full stack trace with raw data about the issue by clicking on the <> Raw text button.
   
2. Click on crash_log.txt to download the crash file and symbolicate it locally in the machine if required.
   

AI analysis

Analyze individual crash instances

1. Click on Show list in the crash 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.
   

Device timeline

1. Click on the individual crash instance to view the device timeline. It shows details of crash instances 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. Battery status
   
5. Network EDGE
   
6. Wifi strength
   
7. Device orientation
   
8. Device Id
   
9. Device model
   
10. UUID
    

Breadcrumbs and session data

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.
   

User info and custom properties

1. Click on View custom properties to check if there are any custom properties available for a particular crash.
   

1. Click PII is available to get the user info like the user ID and email ID (if available).

Note: Viewing user info is a role-based action and only the project members with the appropriate roles and privileges can view it. Whenever the user info is viewed, a record is created in the audit logs for the project in the Apptics console as per Zoho's privacy policy. 

Issue management

Prioritize issues

You can prioritize crashes based on severity. You can mark the severity as show stopper, critical, major, minor, or none.

Collaborate to resolve issues

1. Allow team members to comment, tag, and assign team members to resolve an individual issue promptly. 
   

1. Apptics provides the option to manage issues from within the console which you can use when you have not integrated Apptics with your project management tool. You can address and close issues from within the console. You can view all, open, and closed issues. 
   

Assign issues in Zoho Projects

1. If you are using Zoho Projects, you can integrate it with Zoho Apptics to assign these issues as bugs and manage them efficiently. (Refer to our Zoho Projects integration guide.)
2. Once you have enabled the Zoho Projects integration, you will see an additional column in the Unique Issues list as 'Project' with the 'Assign' option.
   
3. Click Assign to assign the individual issues as bugs in Zoho Projects.

1. Fill in all the details in the pop-up and click Assign bug. The issue will be assigned to the concerned person within your project.
   

Get instant notifications on crashes

1. If you are using Zoho Cliq or Slack, you can enable the integration Zoho Apptics to get instant real-time notifications of crashes reported in Apptics to your dedicated Cliq channel or Slack workspace.
   

For integration steps, refer to:

1. Integration guide for Zoho Cliq
   
2. Integration guide for Slack
   

Crash search

You can search for crashes based on specific user details like device ID or user ID, platforms, app versions, issue, and user groups.