Upgrade

Updates ship for free on CodeCanyon for the lifetime of the item. Here's how to move to a new release without losing your configuration.

Before you upgrade

Because everything user-configurable lives in .env, the upgrade path is much simpler than in most Flutter templates:

• Your .env file is not tracked by git — it survives the upgrade.
• Your Firebase files (google-services.json, GoogleService-Info.plist, firebase_options.dart, firebase.json) are not tracked — they survive.
• Your android/app/keystore.jks is not tracked — it survives.

If you have those four things saved, you can rebuild the app on any fresh copy of the source.

Recommended: use git

The smoothest upgrade path is:

1. On first purchase, commit the ZIP contents to a private git repository of your own.
2. When we ship an update, download the new ZIP and commit it on top of your branch.
3. Resolve any merge conflicts — usually only in files you've customized (assets, app icon, custom strings).

Manual upgrade (no git)

1. Back up your .env, the four Firebase files, and your keystore.
2. Download the new ZIP from CodeCanyon.
3. Unzip it to a new folder.
4. Drop your saved files back in at the same paths.
5. Run make setup && make run-android to verify.

Upgrading Flutter itself

We track Flutter's stable channel. To move your local Flutter to the latest stable:

flutter upgrade

If a new Flutter release introduced a breaking change we've adapted to, our release notes on CodeCanyon will call it out.