{"slug":"troubleshooting","title":"Troubleshooting","summary":"Fixes for the problems people hit most: a preview that will not compile, a locked preview, a turn that stops, conflicts, failed builds, Figma limits, and credits.","body":"Start with the symptom below. When none fits, see [Get help](/docs/get-help).\n\n### The preview says it could not compile\n\nOpen the console from the preview toolbar and read the first error. Send it to the assistant: \"The preview fails with this error, fix it.\" Or fix the file in **Code** and click reload. The last revision stays in place while you repair it.\n\n### I can't click anything in the preview\n\nThe assistant is driving the preview during its turn. The badge says so. Wait for the turn to end, or press **Stop** in the chat to take it back.\n\n### A screen is greyed out in App\n\nIt is planned but not built. Ask the assistant to build it. A detail screen can also be greyed out until the app has shown a record to open.\n\n### The turn stopped before it finished\n\nEdits that landed are kept. Common reasons: you pressed Stop, the organization ran out of credits, or a question expired. Send a follow-up such as \"Continue where you left off.\"\n\n### My edit and the assistant's edit collided\n\nWhen both changed the same file differently, FluxNative keeps both sides as a conflict. Open the file, keep the right parts, and save. See [Revisions and undo](/docs/revisions).\n\n### A Design control is disabled\n\nEither the assistant is working, or the theme no longer has that value. Wait for the turn, or ask the assistant to restore the standard theme values. See [Design tokens](/docs/design-tokens).\n\n### A native build failed\n\nOpen the build in the Build panel, read the reason, and use **Fix with AI**, then **Retry build**. Failed builds are not charged. For iOS, check that the Apple account, the distribution certificate, and this app's provisioning profile are all in place. See [iOS builds](/docs/ios-builds).\n\n### Google sign-in fails on Android\n\nGoogle needs the SHA fingerprints of the key that signed the build. Copy SHA-1 and SHA-256 from **Build**, then **Signing key**, into Firebase or Google Cloud, or ask the assistant to register them when Firebase is connected.\n\n### Send to TestFlight says the Apple account is required\n\nConnect the organization's App Store Connect API key in **Publish**, **Readiness**. Only the owner can. A distribution certificate alone is enough to sign, but not to upload. See [Connect store accounts](/docs/connect-store-accounts).\n\n### TestFlight stays on processing\n\nApple can take a while. Open **Publish**, **Releases** and click **Check TestFlight status**. Also check App Store Connect for a pending export compliance question on the build.\n\n### Send to Play fails for a new app\n\nMake sure the app exists in Play Console with the same package name, and the service account was invited with release permissions. For a brand-new app, Google may require the first bundle to be uploaded by hand. See [Google Play testing](/docs/google-play-testing).\n\n### The store says this build number was already used\n\nBuild again. FluxNative gives every build a new, higher number. See [Versions and build numbers](/docs/versions-and-build-numbers).\n\n### Android says the app is not installed or conflicts with an existing package\n\nThe installed copy was signed with a different key. Uninstall it, then install the new APK. See [Android signing keys](/docs/android-signing).\n\n### My approval disappeared\n\nApprovals cover one exact snapshot. Saving the listing or changing the build clears approvals of the old snapshot. Approve the release again. See [Production release](/docs/production-release).\n\n### Figma import is rate limited\n\nLink imports count against Figma's file quota. Wait for the cooldown shown in the dialog, or use the Design Sync plugin, which does not use that quota. See [Import from Figma](/docs/figma).\n\n### The assistant asks for a key\n\nAdd it under [Connections](/docs/connections), then tell the assistant it is saved. Do not paste it into chat.\n\n### I'm out of credits\n\nGeneration stops until the plan renews or someone with billing access buys a top-up. See [Credits and plans](/docs/credits-and-plans).","sectionSlug":"help","sectionTitle":"Help","updatedAt":"2026-09-23T22:51:25.250Z","previous":{"slug":"settings","title":"Notifications and settings"},"next":{"slug":"faq","title":"FAQ"}}