Quick fixes for the problems people hit most: the preview, a stopped turn, conflicts, the Figma plugin, builds, store uploads and review, credits and keys.
Updated Oct 26, 2026
Help searches the articles; the common problems are one click away.
In the editor
Problem
What to do
The preview won't compile
Send the console's first error to the assistant, or fix it in Code.
You can't click in the preview
The assistant is testing it: wait, or press Stop.
The turn stopped early
Its edits are kept: ask it to continue, or Try again.
A file changed while you typed in Code
Keep mine or Use theirs.
Two chats changed the same lines
A chat still working settles them itself; one that already ended keeps what is live, and its repair (or Settle these lines) asks you which to keep and uses credits. See Revisions and undo.
Edit in the preview waits
A chat is changing the app: edit when it finishes.
The bar says offline or updating
Nothing is lost; drafts and messages send once it's back.
A panel shows a display error
Try this panel again, or Reload builder.
The Figma plugin refuses the code
A code works once, for 15 minutes: make a new one. If the plugin says it is out of date, download the current one and import its manifest again. See Build from a Figma design.
Builds
Problem
What to do
The build button is off
Use the fix on the red check above it.
Google sign-in fails on Android
Add the fingerprints from Build › Signing key to Firebase.
Android won't install the APK
Uninstall the old copy: another key signed it.
The build number was used
Set a higher one in Build.
The stores
Problem
What to do
An Apple account is required
An owner or admin connects the App Store Connect key in Publish.
TestFlight refuses the upload
Raise an approved version (1.0.0 to 1.0.1), or build again for a used build number.
TestFlight stays on processing
Check status; answer any export compliance question in App Store Connect.
Apple refused the submission
Do what the step says (often a demo account, screenshots, or a price: choose Free in the form), then Try again.
Google's first upload fails
Upload the AAB once in Play Console, then I uploaded.
Google refuses the upload over AD_ID
An SDK reads the advertising ID: answer Yes in Play Console › App content › Advertising ID, then Try again. An app without ads can block the permission and build again.
A Play release was saved, not sent
A new app's first release waits for Send app for review in Play Console; with managed publishing, Send changes for review.
A build or store text says Saved in Play Console
FluxNative never sends uploads or store pages for review. Check Play Console › Publishing overview, then Send changes for review: Google sends every waiting change together.
Credits and keys
Problem
What to do
You're out of credits
The agent pauses with its work kept. Add credits (Free buys credit packs too) or upgrade, then Continue in this chat. A first build that stops shows only the tabs it built; the rest wait in App as Planned.
