FlutterFlow App Store stuck: deploy says finished, TestFlight never gets the build

If you have spent a week hitting Deploy and watching FlutterFlow report finished while TestFlight stays empty, you are not missing a hidden toggle. The same failure shows up in the FlutterFlow community every week: publishing failed in history, no Apple email, no build, no useful log in the builder.

This is a release problem, not a missing screen

The visual app can be complete. The store path is a different product: bundle identifiers, App Store Connect API keys, signing, privacy strings, and the hosted build queue FlutterFlow uses. Those fail independently of whether your home screen looks finished.

The threads that rank for this in 2026 are not agency think-pieces. They are people who already built the app and cannot get an IPA into App Store Connect. That is the job: finish the release, then finish the custom Dart the canvas never expressed.

The blockers that actually match the error

Production IPA still carrying the dev bundle ID. FlutterFlow environments can look correctly set while the uploaded archive still uses the `.dev` identifier. Apple then rejects the upload because the identifier cannot change on an existing app record.

App Store Connect API key contract. Deploy history says publishing failed and View Snapshot goes nowhere. That is almost always permissions on the key (App Manager), Team ID, or a stale key after you regenerated credentials in Firebase or Apple.

Queue vs. silent failure. Sometimes the job sits in Codemagic’s queue and later recovers. Sometimes it reports finished and never created a build. If App Store Connect has no processing build after an hour, treat it as a credential or identifier problem, not a wait.

Policy and plist, not code. Missing privacy policy URL, permission usage strings, iPad layout, or a debug build submitted as production. Apple’s rejection email is the spec; prompting the builder to “try again” does not write Info.plist.

What to freeze before you hire

Export or snapshot the FlutterFlow project. Write down the production bundle ID, Team ID, and whether you have an App Store Connect API key with App Manager. Screenshot the Deploy history line that says publishing failed. That package is enough for a 30-minute call.

Do not keep changing version numbers hoping the same key will start working. Each new build number without a new diagnosis just burns the queue.

Finish in FlutterFlow, or export?

Stay in FlutterFlow when the screens and data model are right and the failure is signing, listeners, or a handful of custom actions. Export when you need CI you own, modules the canvas cannot express, or a store account and keys that must live outside the builder. The first call is which of those you are in — not a rewrite pitch.

Next step

If the app is already built and the store is the wall, that is hire a FlutterFlow Expert work. Book a 30-minute call with the project link and the rejection or history screenshot. If the stack is Lovable, Bolt, or Cursor instead, use vibe-code rescue — same first call, different checklist.