Non-fatal tracking in Zoho Apptics
Overview
Apptics provides a way to record the non fatal errors and exceptions that are caught in your app's try-catch blocks. Using the non-fatal module in Zoho Apptics, you can track and analyze non fatal errors similar to fatal errors like crashes and ANRs.
To start tracking the non-fatal errors in your app, you need to integrate our SDK with your app. Once the SDK integration is done, all the diagnostic info about the thrown exceptions from your code's catch blocks will be sent to our servers and then shown as detailed reports, similar to crashes module in the Apptics web console.
For SDK implementation, refer to:
Non-fatal errors and exceptions dashboard
- Navigate to Developer> Non-fatal in the left menu. You can view the total number of non-fatal errors, unique issues that caused the reported non-fatal errors, unique devices affected, and percentage of exception-free devices (exception free rate) for the selected date range.
- The charts help you visualize the number of non fatal errors and the timeline of errors that happened over the selected date range across different platforms.
- 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 non-fatal errors, and the total number of affected devices, and comments.
Error grouping
- Similar to crashes, Apptics automatically tracks every error instance and groups them based on stack traces.
- For more clarity, you will see a tag beside each unique issue that specifies the app framework for which the non-fatal error is reported, i.e., Native, React Native, or Flutter.
Analyze non-fatal error reports
Error tracking in Apptics includes symbolicated crash reports and error logs, stack traces, threads, device details, crash environment, breadcrumbs, and other diagnostic information to debug and identify the root causes of issues.
- Click on the individual issue in the unique issues list to get more details.
- The timeline graph gives you the total number of non-fatal error instances and the unique number of affected devices over time. You can view stats like the number of errors caused by the unique issue, the affected devices, and the latest affected app version.
- The other graphs give you an idea of the affected devices, OS versions, and app versions.
Stack traces
- 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.
- If you are not able to see symbolicated/deobfuscated stack traces for some reason, click on Symbolicate for iOS, and Deobfuscate
for Android. - You can also view the full stack trace with raw data about the issue by clicking on the <> Raw text button.
- Click on crash_log.crash to download the error report file in you local machine.
AI analysis
Click on AI analysis to get an AI-generated error analysis report which includes device information, crash summary, analysis, conclusion, and remedies if available.
Analyze individual error instances
- Click on Show list in the non-fatal details page and you will see a list of all the non-fatal instances that happened due to the unique issue.
- The list includes details such as the affected device model, app version, OS version, device ID, time at which the non-fatal error happened, and the time at which it was received in Apptics. Click on the individual instance to see more details.
- The device timeline will give you the details on the device-specific information such as:
- Apptics SDK version
- App version
- OS version
- Battery status
- Network EDGE
- Wifi strength
- Device orientation
- Device Id
- Device model
- UUID
Breadcrumbs, sessions data, and user info
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).
- The events trace shows the events that occurred when the issue occurred.
- The API calls trace shows the list of all the API calls that were triggered while the issue occurred
- The screens trace shows the list of all the screens that were visited when the issue occurred.
- Click on View custom properties to check if any custom properties are available for a particular crash.
- 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 update the severity of the individual issues and tag it as show stopper, critical, major, or minor issue.
Collaborate to resolve issues
- Allow team members to comment, tag, and assign team members to resolve an individual issue promptly.
- You have the option to manage issues from within the console if you have not integrated Zoho 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
- 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.)
- 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.
- Click Assign to assign the individual issues as bugs in Zoho Projects.
- 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.