Push your changes to your app, package them into a new version, and send that version to testers and store review. For your app’s first store version, see Send to testers instead.

Push

FlutterFlow builds a new version from your app, not from a thread’s copy. Unpushed changes in a thread aren’t in the next version.

To include a thread’s changes, select Push to your app in that thread. See Push.

What’s waiting

A line at the bottom of Overview counts the changes that you’ve pushed since your latest version. Each push is one change, so a thread that you pushed twice counts as two.

1. Open Overview.
2. At the bottom of the page, read the line about your changes. For example:
   • “3 changes since 0.1 · Booking reminders, waiting for the next release”: three pushes aren’t in a version yet.
   • “Nothing new since 0.1 · Booking reminders”: every change that you’ve pushed is already in a version.
3. To see the changes, select Show. The line lists up to five of the changes that are waiting, each with who pushed it and when. To open the thread that pushed a change, select the change. Under the changes, the line lists your last two versions and where each one is in each store.
4. To see every change, select All changes. The Changes panel opens. Under Next release, it shows how many changes are waiting, such as 3 changes waiting, and then your recent versions with the changes that each one included. Older versions are in Releases.

Version number

A new app starts at version 0.1 (0.1.0 in App Store Connect), and each build keeps that number until you change it. Rebuilding an earlier version uses that version’s original number, and FlutterFlow increments build numbers automatically. After you submit a version for App Store review, your next App Store submission needs a higher version number, unless Apple returns the version for changes, in which case you resubmit under the same number.

Your app’s version number lives in the app’s code rather than in a settings panel. To change it, ask the agent in a thread:

Example request

“Change my app’s version number to 1.0.”

For iPhone builds, the version number takes up to three whole numbers separated by dots (such as 1.2.3), each up to nine digits with no leading zeros (version 1.02 fails on iPhone). Push the change to your app so the next version you send to testers uses the new number.

Send to testers

On the Releases page, a bar at the top offers what you can send next.

1. Open Releases.
2. At the top of the page, find the bar for The next version. If a store is still waiting for you to send your current version for review, the bar offers Send for review instead. Submit or resolve the current version first.
3. Select Send to testers. The Send the next version to testers panel opens. A send to testers always sends your app with every change that you’ve pushed.
4. Optional: To send to only one store, clear the other store’s checkbox.
5. Select Send to testers.

FlutterFlow prepares the new version and uploads it for your testers: to TestFlight for the App Store, and to Google’s closed test for Google Play. See Send to testers.

Next

The next version3 changes haven’t been sent to testers.

Send to testers

Submit for review

After your testers have the new version, submit it for review. On the Releases page, select Send for review. See Submit for review.

The version that’s already live in a store stays live until the new version replaces it. On the App Store, it stays live until Apple approves the new version.

Troubleshooting

For problems with builds, version numbers, or store review, see Troubleshoot phone builds and store releases.