Earlier versions
Rebuild an earlier version of your app and send it where new builds go, so that you can test it. Your app itself doesn’t change.
Rebuild an earlier version
To rebuild an earlier version:
-
On the Releases page, under Versions, click the version.
-
At the bottom of the version’s drawer, click Go back to this version.
If you open the version that your testers have, FlutterFlow goes back to the version before it.
-
Read what FlutterFlow will do for each store:
- App Store: it rebuilds the version for iPhone and uploads it to TestFlight.
- Google Play: it rebuilds the version for Android. If FlutterFlow is connected to Google Play, it also uploads the rebuilt version there.
-
Click Go back.
Result: FlutterFlow rebuilds the version under a higher build number and sends it where every new build goes: TestFlight for the iPhone app, and Google Play for the Android app when FlutterFlow is connected to it.
Test the rebuilt version, and then submit it for review. See Add testers and Submit for review.
What doesn’t change
Going back to an earlier version rebuilds that version for the stores, and nothing else changes:
- Your app: the changes that you pushed after that version stay in your app, so the next version that you send includes them again. To change your app back, see Undo a push
- The stores: a version that’s in review, rolling out, or live in a store stays as it is. FlutterFlow doesn’t submit the rebuilt version for review. You do that yourself.
Keep later changes out
The changes after the version that you went back to are still in your app. To ask the agent to remove them, click Ask the agent in the Go back dialog, or in the message that appears after you click Go back.
A new thread opens with a request already written that asks the agent to remove those changes. Review it, and send it.