Release builds
signing and uploading.
The commands that build a release, and how to sign it with your own keys. The build commands come from app/README.md; signed store builds were not made while writing this guide (unverified).
01Version number
In app/pubspec.yaml the line version: 1.0.0+1 is name + build number. Raise the build number for every upload. The server's version is in server/package.json and PRODUCT_VERSION in server/src/admin/manifest.ts.
02Android
Flutter runs natively on Windows: use PowerShell for the flutter commands and Android builds (iOS builds need a Mac). For the server, either install Node.js 22.12+ for Windows and use PowerShell (replace cp .env.example .env with Copy-Item .env.example .env; there is no openssl by default, so use WSL or any random 64-character hex string), or run the commands in WSL 2 (Ubuntu) or Docker. macOS and Linux users can ignore this note.
- Create an upload key (keep it and its passwords safe, forever):
keytool -genkey -v -keystore ~/upload-keystore.jks -keyalg RSA -keysize 2048 -validity 10000 -alias upload - Create
app/android/key.propertieswithstorePassword,keyPassword,keyAlias,storeFile, and editapp/android/app/build.gradle.ktsso thereleasebuild type uses asigningConfigbuilt from it. As shipped, release builds are signed with the debug key (signingConfig = signingConfigs.getByName("debug")) and Play will refuse them. - Build an App Bundle for Play:
or an APK:cd app flutter build appbundle --release \ --dart-define=API_BASE_URL=https://your-server.example.com
The result is influtter build apk --release --dart-define=API_BASE_URL=https://your-server.example.combuild/app/outputs/. - Upload the .aab in Play Console, fill in the data safety form, and release to a test track first.
Do not commit key.properties or the keystore.
03iOS
- Set your team and bundle id in Xcode (Rename).
- Build:
orcd app flutter build ios --release --dart-define=API_BASE_URL=https://your-server.example.comflutter build ipa --release --dart-define=..., or openios/Runner.xcworkspace, choose Any iOS Device, Product, Archive. - Upload the archive with Xcode Organizer (Distribute App, App Store Connect) or Transporter.
- In App Store Connect add the in-app purchases to the version, screenshots, and the privacy details.
Release builds were not run for this guide: unverified. The Podfile platform is 16.0.
04Listing wording
Describe the app as a forecasting-skill and calibration trainer: the user enters their own probability before seeing the crowd's, then learns from a Brier score and a calibration curve. Keep to what the app does. Do not call it a betting, trading or advice app, do not promise results, and credit the data source as described in Attribution. Use your own screenshots of your build.