When using Instabug Crash Reporting, each occurrence comes with user attributes, user data, and attachments if available.
Default attributes as well as any custom user attributes that you set are automatically sent to your dashboard with all crash occurrences.
Default attributes listed in each crash occurrence include:
- Date and time of crash occurrence in UTC
- App version
- OS version
- App view
- Device location
- Session duration
- Screen resolution
- Screen density
More details about how to set custom user attributes can be found here.
Custom data can be set and sent with each occurrence. To learn more about setting custom user data, check here.
Any custom files added by you can be sent with each occurrence.
Repro Steps help you reproduce a bug by displaying your users' actions in each view of your app. With each view, you will find a list of actions that tell you exactly what the user did in that view. More details can be found here.
This is enabled by default depending on your plan.
With each crash occurrence, you'll receive a detailed environment profile covering the last 60 seconds before the report was sent. This Session Profiler includes device data like memory load and battery state. This is enabled by default depending on your plan. More details about the information contained in the Session Profiler can be found here.
A whole host of logs are sent with every crash occurrence. These logs include:
- Console Logs: Default logs that are printed to the console when the application is running.
- Instabug Logs: Logs with different verbosity levels that you can add manually.
- User Steps: Every step the user has taken in the form of log entries.
- Repro Steps: Visual user steps prior to the crash occurrence in the form of images and GIFs.
- Network Logs: A log of each network request.
- User Events: A manual log of actions that a user has taken.
Updated 3 months ago
With occurrences all wrapped up, learn how to reach out to users who've encountered crashes to let them know you're on it.