---
title: Mobile Super Debugger
description: "Open the mobile Super Debugger to inspect Guides and Surveys, review logs, verify SDK setup, and report issues."
product: guides-surveys
lang: en
last_updated: 2026-11-16
token_estimate: 2067
---
# Mobile Super Debugger

The mobile Super Debugger shows guide and survey conditions, SDK logs, and installation details inside your app. Use it to investigate why an experience doesn't appear, verify event flow, or collect information for a bug report. For web apps, use the [Amplitude Chrome extension](https://amplitude.com/docs/data/chrome-extension-debug).

> For AI agents: a documentation index is available at [/docs/llms.txt](/docs/llms.txt). Append `.md` to any page URL for markdown, or send `Accept: text/markdown`.

## Prerequisites

- Install and initialize the Guides and Surveys SDK and configure your app to handle the project's mobile URL scheme. Follow the setup instructions for [iOS](https://amplitude.com/docs/sdks/guides-and-surveys/guides-and-surveys-ios-sdk), [Android](https://amplitude.com/docs/sdks/guides-and-surveys/guides-and-surveys-android-sdk), [React Native](https://amplitude.com/docs/sdks/guides-and-surveys/guides-and-surveys-rn-sdk), or [Flutter](https://amplitude.com/docs/sdks/guides-and-surveys/guides-and-surveys-flutter-sdk).
- Install that build of your app on the device, iOS simulator, or Android emulator you use for debugging.

## Open Super Debugger

Open Super Debugger through project-level [Test User mode](https://amplitude.com/docs/guides-and-surveys/testing#test-user-mode) or Preview mode for a specific guide or survey. Both methods display a floating Amplitude logo in your app. Tap the logo to open the debugger.

### Use project-level Test User mode

Use Test User mode to browse available guides and surveys and choose one to debug.

1. In Amplitude, go to _Project Settings > Guides and Surveys_.
2. Add your user to the project's test users.
3. Open your app as that user and let the Guides and Surveys SDK initialize. If the app is already running, restart it so the SDK loads the updated test user setting.
4. Tap the floating Amplitude logo.
5. On the _Details_ tab, tap the guide or survey selector and choose an experience to preview.

Project-level Test User mode differs from the [Testing status](https://amplitude.com/docs/guides-and-surveys/testing#testing-status-function) on an individual guide or survey. Testing status controls who receives that experience. Project-level Test User mode opens the mobile debugging tools.

Turn off [Test User mode](https://amplitude.com/docs/guides-and-surveys/testing#test-user-mode) after debugging, then verify behavior as a regular user. Test User mode and preview sessions can change delivery behavior.

### Use Preview mode

Use Preview mode to open a specific guide or survey directly from the builder.

1. In Amplitude, open the guide or survey and click **Preview**.
2. Scan the QR code with your device, or open the preview URL on the device, simulator, or emulator where you installed your app.
3. After your app opens, tap the floating Amplitude logo.

If the QR code or URL doesn't open your app, follow [Mobile: preview doesn't open the app](https://amplitude.com/docs/guides-and-surveys/testing#mobile-preview-doesnt-open-the-app).

## Inspect a guide or survey in Details

Open the _Details_ tab to inspect the selected guide or survey and the conditions that control its display.

### Switch guides or surveys

Tap the name under _Guide / Survey_ to open the available guides and surveys. Search by name, then select an experience to open its debug preview. If the list is empty, tap **Refresh** to reload it.

### Review step and session data

The details section shows:

- **Step**: The current step and total number of steps, such as `2 of 4`.
- **User**: The user ID for the preview session.
- **Screen**: The screen name the SDK reports. Compare this value with the experience's screen targeting rules.

Tap the copy icon beside a value to copy it.

### Check limits, triggers, and throttles

Expand each row under _Debug_ to inspect its status and configuration:

- **Limits**: Check whether display or user-history limits block the experience. When available, use **Reset User History** to clear history and repeat a test.
- **Trigger**: Review the trigger condition, screen conditions, and target element for a pin, when applicable. Use this information to identify which condition still needs to pass.
- **Throttle**: Check whether throttling blocks the experience. Toggle **Ignore limits** to bypass throttling during the preview.

The status icons indicate the result of each check:

- **Checkmark**: The condition passes.
- **Warning triangle**: A condition blocks the experience, such as an unmet screen condition, a missing pin target, or a display limit.
- **Information icon**: The trigger is waiting, such as for an event or user action.
- **Error icon**: The debugger can't evaluate the condition, such as when session context is missing. Expand the row to inspect any available details.

A successful preview doesn't guarantee production delivery: retest without preview overrides to verify the experience's normal behavior.

### Debug pin placement

Expand **Pin Debugging** under _Advanced_ and enable **Reposition pins every 5 seconds** to re-evaluate pin positions periodically. Use this option when a pin's target moves as your app's layout changes.

### Restart or close a preview

- Tap **Restart Preview** to return to the first step and restart the preview.
- Tap **Close Preview** to end the preview and dismiss the debugger.

## Review SDK activity in Logs

Open the _Logs_ tab and expand a section to review timestamped entries, with the most recent entries first. Reproduce the issue during a preview to capture relevant activity.

- **View Hierarchy Updates**: Inspect the view hierarchy updates the SDK captures. Use these entries to investigate changes to screen elements and pin targets.
- **Analytics SDK calls**: Review the analytics SDK activity captured during the debug session. Use these entries to investigate event-based triggers.
- **General Logs**: Review SDK diagnostic messages, including warnings and errors.

In **General Logs**:

1. Enable **Show errors only** to limit the list to errors and warnings.
2. Enter text in **Search logs** to filter messages. Search is case-insensitive and works with the error filter.
3. Tap the pause icon to freeze the displayed list while you inspect it. The SDK continues collecting logs.
4. Tap the play icon to resume live updates.

Expand long entries to read their full contents.

## Verify the installation in Setup

Open the _Setup_ tab to inspect the SDK and user information for the current session.

- **SDK Versions**: Check the installed Engagement SDK version. Copy the version when reporting an issue.
- **Installation**: Check the installation type, such as a plugin installation. Expand **Configuration** to inspect options that differ from the defaults.
- **User**: Verify the user ID and properties the Guides and Surveys SDK has received. Expand **Properties** to inspect individual values, or use the copy icons to copy user information.
- **Event Flow**: Check whether the SDK has observed events flowing into and out of Guides and Surveys. Incoming events support event-based triggers; outgoing events report guide and survey activity.

If event flow hasn't registered, perform an action that sends an analytics event or interact with a guide or survey, then check again. These indicators reflect observed activity; they don't confirm that an event has arrived in Amplitude.

## Get help or report an issue

Tap the question mark button to open _Support_.

- Tap **Install and Initialize the SDK** to open the platform's Guides and Surveys SDK documentation.
- Tap **Guides and Surveys Overview** to open the general product documentation.
- Tap **File Bug Report** to prepare an email to the Guides and Surveys team.

To file a bug report:

1. Enter **Steps to Reproduce**, **Expected Results**, and **Actual Results**.
2. Tap **Send** to open your email app with a draft addressed to the Guides & Surveys team.
3. Review the draft and its diagnostic attachment, then send the email from your email app.

The attachment includes guide or survey context, SDK and device details, and captured debug logs. You need an email app configured on the device; on iOS, add an account in Mail if the debugger reports that Mail isn't available.

