---
title: "Fix preview and runtime problems"
description: "Separate stale previews, launch crashes, broken behavior, and data failures."
---
A preview can show an earlier successful build even when the latest build failed. First confirm which version is running, then distinguish preview infrastructure from a problem inside the app.

## The preview is from an earlier version

When Superapp warns that the preview is stale, read the latest build result. Fix the build before evaluating whether the requested visual change appeared. Relaunching an old successful preview cannot make failed code visible.

## The preview is unavailable

1.  Wait for the current build and simulator startup to finish.
2.  Restart the preview once if it timed out or disconnected.
3.  Check whether the latest build itself succeeded.
4.  If repeated restarts fail with no build error, preserve the message and contact support.

## The app launches and closes

Treat this as a runtime crash, not a preview refresh problem. Record the last visible screen and action, capture the crash or console message, and reproduce it from a clean launch. Common causes include forced assumptions, missing configuration, unavailable resources, and code that runs too early during startup.

## The app runs but behaves incorrectly

Describe one reproducible path: starting state, exact taps, observed result, and expected result. Test empty, loading, offline, denied-permission, and signed-out states separately.

## Data is missing or does not persist

-   Confirm whether the feature uses local storage or a backend.
-   Test relaunch, reinstall, sign-out, and a second device as separate cases.
-   Verify the active user and environment before changing access rules.
-   Do not test a destructive repair against production data.