Quickstart
Sign in from the terminal and connect a Flutter project to Retrojet.
You need the CLI installed and a Flutter project. If you do not have a Retrojet account yet, the sign-in step lets you create one.
1. Sign in
retrojet login
Your browser opens the Retrojet console. Sign in (or create an account), check that the request comes from your terminal, and click Allow. Back in the terminal you see:
✓ Logged in to Retrojet.
Patch your Flutter apps in minutes, not days.
Working over SSH or on a machine without a browser? Use retrojet login --no-browser and open the printed URL on
any device. Check who you are signed in as with retrojet whoami.
2. Connect your project
Run this in the folder that contains pubspec.yaml:
cd my_flutter_app
retrojet init
✓ Retrojet is set up for com.acme.demoapp.
Created the app "demoapp" in Acme (app_id 6f1c2a4e-...).
Saved to retrojet.yaml. Commit this file.
retrojet init reads your package ID from every platform folder, then looks for an app with that exact package ID
in your organizations. If it finds one, it uses it. If not, it creates the app, named after name in
pubspec.yaml. The result is saved in retrojet.yaml:
# Retrojet configuration, created by `retrojet init`. Commit this file.
app_id: 6f1c2a4e-...
Commit retrojet.yaml. Every teammate and your CI then talk to the same app.
init stops if the package ID differs between platforms, for example com.acme.demo_app on Android and com.acme.demoApp on iOS. See Package ID must match.3. Release and patch
retrojet release and retrojet patch are being built. This section will walk through your first release and patch when they are available.The flow will be:
retrojet release android # build and upload the release you also submit to Google Play
# ...change some Dart code...
retrojet patch android # build a patch for that release and publish it to a channel
Then, in the console, promote the patch to stable when you are happy with it.