When your app is responsive for 3 seconds or more, an App Hang is captured automatically
When your app hangs it causes user frustration and can lead them to abandon your app altogether.
An App Hang occurs when the main thread of your app fails to respond within a reasonable timeframe. This can happen due to tasks that consume a lot of CPU resources or when blocking I/O operations are performed on the main thread.
If your app remains unresponsive for 3 seconds or more we capture it as an “App Hang”. We detect Hangs automatically out of the box.
Here is how to view app hangs on the dashboard:
How are occurrences of App Hangs grouped:
Just like User Terminations, App Hangs are grouped together by screen.
What information is available inside the app hang:
- Stack trace
- Flame graphs to help debug the root cause of the app hang
- Patterns to highlight which subset of users have experienced app hangs
- Occurrences view, where you can view every occurrence of the frustrating experience and what has led to it
- Occurrences include the following debugging data:
- Metadata of the device
- Session Profiler to know the state of the device for the last 60 seconds before the app hang occurred
- Repro steps which is a visual step by step reproduction of the session of the user, screen by screen and interaction by interaction on the app up until the user triggered the termination
- Logs section including console logs and network logs for all API calls that were made during the session
An app hang is a mobile specific metric that is being picked up by Instabug to give you visibility on the frustrating experiences that the users are going through while using the app.
The data included in app hang enables developers to proactively pick up the frustrating experiences and how it happened and what led up to it. This gives them a chance to resolve those issues early on and keep the standard of quality of the app as high as possible.
Updated 6 days ago