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.

Repro steps captured by Luciq

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

Location of Reprosteps inside a Crash Report

Location of Reprosteps inside a Bug Report

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.

Auto Masking

The default value is webViews. Starting from SDK version 19.2.0, WebViews are masked by default in screenshots to protect potentially sensitive content.

Redacting View Content in User Steps and Repro Steps

Starting from SDK version 19.7.0, you can use Luciq.viewsContentCaptureEnabled as a master privacy flag that controls whether User Steps and Repro Steps capture view content (titles, labels, text). When disabled, captured events still fire with the gesture, view class, and screen name. User Steps omit captured view labels, while Repro Steps replace view text and labels with non-identifying descriptors such as "a button", "a text", or "an image", the same descriptors used by UIView.luciq_privateView.

By default, viewsContentCaptureEnabled is true. Set it to false to redact view content from User Steps and Repro Steps.

Swift

Luciq.viewsContentCaptureEnabled = false

Objective-C

Scope and behavior

• Affects only User Steps and Repro Steps view content: User Steps labels are omitted, and Repro Steps labels use non-identifying descriptors. It does not affect Session Replay screenshots or bug-report screenshots — use the auto-masking APIs for those.

• Stored in memory for the current process and does not survive app restarts.

• Can be set before Luciq.start(withToken:invocationEvents:) so the value is applied as soon as automatic capture starts.

• Applies to events captured after the call. Previously-recorded steps are not retroactively redacted.

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:

Swift

Luciq.setReproStepsFor(.all, with: .enable)

Objective-C

You can change the value of the Issue Type.

Swift

//Bug Reporting and Crash Reporting  
.all  
//Bug Reporting Only  
.bug  
//Crash Reporting Only  
.crash

Objective-C

You can change the value of the User Steps Mode.

Swift

//Enable with Screenshots  
.enable  
//Enable with NO Screenshots  
.enabledWithNoScreenshots  
//Disable  
.disable

Objective-C

Examples

Enable with Screenshots for both Bug Reporting and Crash Reporting:

Swift

Luciq.setReproStepsFor(.all, with: .enable)

Objective-C

Enable with No Screenshots for Crash Reporting.

Swift

Luciq.setReproStepsFor(.crash, with: .enabledWithNoScreenshots)

Objective-C

Completely disable for both Bug Reporting and Crash Reporting.

Swift

Luciq.setReproStepsFor(.all, with: .disable)

Objective-C