‘Application Not Responding’ is a state in which the app is frozen and does not respond to any user input. This happens when the app’s UI thread is frozen for more than 5 seconds. This is a great section for Product Owners and Developers to stay on top of app performance.



  1. Share any ANR issue with your team using the public link.

2. Utilize the ANR analytics section for any new screen, screen redesign, to compare from version to version, or to compare AB test screen versions.

Appsee aggregates ANR issues by screens. You’ll get a high level overview of how many issues your app has, how many sessions are crashing, how many users are affected by crashes, and on average how long is there between crashes.

It’s great to review the daily ANR graph side by side with your version release dates so you can understand if any new version has caused a peek in ANR.


If you click into an ANR issue, a new window will open with more information regarding that specific issue. You’ll have access to all of the sessions that experienced this ANR. You can also utilize the statistics tab to help you identify commonalities between the sessions.


One way to prioritize the ANR issues is by the screen that is experiencing ANR. If the ANR screen is on a payment screen or registration screen, this might also be an issue to prioritize. The statistics tab can also help you understand how to prioritize your ANR. For example, you can look at the session index. This will show you if the user is in their first session, or their 100th session. If the ANR is mostly happening to new users, you might want to consider increasing the priority on fixing this issue.  

Recommended Article:

  1. Learn more about ANR and how it differs from an app kill and unresponsive gestures.