Repro Steps show you all of the interactions a user makes with your app up until a bug or crash is reported, grouped by the app view. For each view that a user visits, all of the steps that they commit are captured and displayed as logs next to the relevant screenshot. Repro steps can be found below the bug details.

Logged Data

Captured Events

UI Interactions

For the following gestures, only the gesture is logged and displayed:

• Swipe
• Scroll
• Pinch
• Tap
• Double tap
• Enabling/disabling a switch
• Changing the value of a slider
• Editing a text field.

Lifecycle Events

Whenever one of the following lifecycle events occurs, it will be captured and shown on the timeline:

• Application is moved to the background
• Application is moved to the foreground
• Application becomes active
• Application becomes inactive

Extra Details

Depending on the event, you'll find further details displayed as part of the log statement.

• Tap and double tap: the SDK always tries to first capture the text rendered inside the UI that the user is interacting with, then we fall back to capturing the icon only with the buttons and navigation items, then, we fall back to the accessibility labels.
• Switch: both the accessibility label as well as whether the user enabled or disabled the switch are logged.
• Slider: both the accessibility label as well as the value that the user moves the slider to it are captured.
• Text fields: first, the SDK tries to capture the placeholder, then we fall back to the accessibility label.

Examples

Here are some examples of how steps look like:

• Tapped on the button "Send"
• Double tapped on UI that contains "Instructions"
• Started editing “Password“
• Enabled the switch “Push Notifications“
• Moved the slider “Text Size“ to 10%
• App went to the background
• App became active

User Privacy

Disclaimer

A disclaimer will be shown at the bottom of the report. It helps your users view all the screenshots taken for the Repro Steps before sending a report and can delete them as well.

Private Views

On your side, you can easily mark any view that might contain sensitive info like payment details as private. Any private view will automatically appear with a black overlay covering it in any screenshot.

📘

Effect of Private Views

When adding a view to the list of private views, here are the list of things it will affect:

• Views will be blacked out in screenshots
• Views will be blacked out in repro steps
• Views will be blacked out in the View Hierarchy. Text views will be replaced with ****
• Videos will not be blacked out due to limitations regarding media projection
• To black out screens in videos/screen recording, you can use Android’s FLAG SECURE

Adding Private Views

To make a view private, you use the following method:

//Should be added in the activity with the view, takes any number of views
Instabug.addPrivateViews(view1, view2, view3)

//Should be added in the activity with the view, takes any number of views
Instabug.addPrivateViews(view1, view2, view3);

Removing Private Views

If you'd like to remove a view from the list of private views, use the following method:

//Should be added in the activity with the view, takes any number of views
Instabug.removePrivateViews(view1, view2, view3)

//Should be added in the activity with the view, takes any number of views
Instabug.removePrivateViews(view1, view2, view3);

Auto Masking

📘

Good to know

• This feature requires a minimum Android SDK version of 11.13.0
• Auto Masking is supported only in screenshots (Repro Steps), not screen recordings.

🚧

Jetpack Compose

Auto Masking is available in Jetpack Compose starting from SDK version 13.4.0

This feature automatically masks sensitive data when screenshots are captured while protecting the user's privacy by default. This affects Bugs Reporting, Crash Reporting and Session Replay.

//build time
Instabug.Builder(this, "{INSTABUG_TOKEN}")
        .setAutoMaskScreenshotsTypes()
        .build()

//runtime
Instabug.setAutoMaskScreenshotsTypes()

//build time
new Instabug.Builder(this, "{INSTABUG_TOKEN}")
     .setAutoMaskScreenshotsTypes()
     .build();

//runtime
Instabug.setAutoMaskScreenshotsTypes();

Here are all the possible parameters.

//No Masking Applied
MaskingType.MASK_NOTHING

//Masks text labels, including buttons and titles
MaskingType.LABELS

//Masks images and video
MaskingType.MEDIA

//Masks Text Input
MaskingType.TEXT_INPUTS

Examples

📘

The Private Views API takes precedence over Auto Masking.

Disabling and Enabling

Repro Steps is by default enabled with screenshots for both bug reporting and session replay and enabled without screenshots for crash reporting.

val configurations = ReproConfigurations.Builder()
  .setIssueMode(IssueType.All, ReproMode.EnableWithScreenshots)
  .build()

Instabug.setReproConfigurations(configurations)

ReproConfigurations configurations = new ReproConfigurations.Builder()
                .setIssueMode(IssueType, ReproMode)
                .build();

You can change the value of the Issue Type.

//Bug Reporting, Crash Reporting and Session Replay
IssueType.All
//Bug Reporting Only
IssueType.Bug
//Crash Reporting Only
IssueType.Crash
//Session Replay Only
IssueType.SessionReplay

//Bug Reporting, Crash Reporting and Session Replay
IssueType.All
//Bug Reporting Only
IssueType.Bug
//Crash Reporting Only
IssueType.Crash
//Session Replay Only
IssueType.SessionReplay

You can change the value of ReproMode.

//Enable with Screenshots
ReproMode.EnableWithScreenshots
//Enable with NO Screenshots
ReproMode.EnableWithNoScreenshots
//Disable
ReproMode.Disable

//Enable with Screenshots
ReproMode.EnableWithScreenshots
//Enable with NO Screenshots
ReproMode.EnableWithNoScreenshots
//Disable
ReproMode.Disable

Then configure the SDK

//build time
Instabug.Builder(this, "{INSTABUG_TOKEN}")
    .setReproConfigurations(configurations)
    .build()

//runtime
Instabug.setReproConfigurations(configurations)

//build time
new Instabug.Builder(this, "{INSTABUG_TOKEN}")
                .setReproConfigurations(configurations)
                .build();
//runtime 
Instabug.setReproConfigurations(configurations);

Examples

📘

Screenshots are by default disabled for Crash Reporting.

For Crash Reporting, screenshots are by default disabled; however, if you are looking to enable screenshots in Crash Reporting, make sure to use the Auto Masking API. This API will automatically help you mask sensitive data in screenshots to protect the end-users' privacy.

Handling Screenshots and Mitigating Overhead

If screenshots are enabled, we capture a screenshot whenever a screen is changed, then attach this info to Crash Reporting and Session Replay. However, we have mitigation methods to avoid causing performance overhead on the device. If this happens, we pause the screenshot-capturing process when we detect that the device has any of the following states, and continue capturing screenshots after the device returns to normal:

1. High CPU throughput
2. High RAM utilization
3. Low-disk storage