Start here: recover from an error
Identify the failing layer, preserve evidence, and choose the safest recovery.
An error is easier to recover from when you stop changing the project and identify the first failing layer. Preserve the exact message, decide whether the issue is temporary or project-specific, and make one controlled recovery attempt.
The first five minutes
- Wait for any active Superapp change to finish.
- Do not send the same request repeatedly or begin several unrelated fixes.
- Copy the first meaningful error and note the action immediately before it.
- Check whether the last working version still builds or previews.
- Choose one matching guide below and test after one recovery change.
Identify what is failing
The agent keeps attempting the same fix
Stop the loop and continue with Escape an agent error loop. Restate the observed error and ask for diagnosis before another edit.
The latest version does not compile
Open Fix Swift and Xcode build errors. Start with the first compiler error rather than the final “build failed” summary.
The app builds, but the preview is stale or broken
Use Fix preview and runtime problems to separate an old preview, a launch crash, and incorrect app behavior.
A device build, capability, or Apple service fails
Check Fix signing and entitlement errors before changing certificates or project identity.
The change is broader than the fix
Return to a previous working version. See History and recovery before adding more repair prompts.
If you need help
Follow Collect diagnostics and contact support. Include the project name, affected screen, steps to reproduce, and the exact error. Never include passwords, private keys, recovery codes, or service-role secrets.