Repro Steps
How to automatically mask the screens reported in Repro Steps
Repro Steps is your go-to tool for understanding what led to a bug or crash in your app. This guide will help you make the most of Repro Steps.
What are "Repro Steps"?
Repro Steps capture and present all the actions a user takes in your app before encountering a bug or crash. These steps are grouped by the app view, and you can view user steps alongside relevant screenshots. It's like having a play-by-play visual and written record of the user's actions leading to the problem.
Where can you find "Repro Steps"?
To find the Repro Steps, simply scroll down below the bug details. If you are on the crash reporting tool, you will find them in the occurrences page of a crash below the crash details. Check the screenshot below to find them
Understanding the Setup
Repro Steps are organized by the different screens in your app that users interact with. Each screen view visited by the user contains a set of chronological steps, giving you a clear picture of what led to the reported issue.
Understanding Logged Data and Captured Events
Logged data captures user interactions, such as swipes, scrolls, taps, and more. It provides insights into how users engage with your app. The captured events track app states, including background/foreground transitions, activity changes, and memory warnings.
How can you enable Repro steps?
Repro Steps is by default enabled with screenshots for bug reporting, and enabled without screenshots for crash reporting. So do you need to change anything here? If yes, you can use the following properties:
You can change the value of the Issue Type.
You can change the value of the User Steps Mode.
Examples
Enable with Screenshots for both Bug Reporting and Crash Reporting:
Enable with No Screenshots for Crash Reporting.
Completely disable for both Bug Reporting and Crash Reporting.
Last updated