A Force Restart occurs when a user forcefully closes an app and immediately restarts it. The underlying frustration that prompts the user to restart the app often goes unnoticed by app developers, as it is not classified as a crash.
Instabug gives you visibility over Force Restarts, which are detected automatically. You can now detect these issues early on, and address them, so you can improve the app quality and retention.
- User opened the App
- The App was very slow
- User closed the App and opened it again
Force Restarts are captured by default. You can reach the Force Restarts section as shown in the screenshot below:
Similar terminations are grouped together by screen, as shown in the below screenshot.
Force Restarts are grouped by events that happened on the same screen.
- Patterns to highlight which subset of users has triggered the highest number of Force Restarts.
- 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 Force Restart was triggered.
- 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.
Instabug's Force Restarts feature can be a critical tool for developers seeking to enhance their app's user experience. By notifying you of user frustrations in real-time, it provides you with the opportunity to address issues promptly, maintaining user satisfaction and improving app performance.
Updated about 1 month ago