A Godot 4 editor plugin that exports your project for mobile and ships it — to TestFlight, the App Store, Firebase App Distribution and Google Play — without leaving the editor.

It adds a Release tab next to 2D/3D/Script with one column per destination: the store's recent releases on top, a Release button underneath, and a live build log at the bottom. The work is mainly done by Godot's headless exporter and fastlane.

What it does

• One click per destination: patch the version, export the preset, upload the artifact.
• Live log streamed from the running build, with a Stop button that kills the whole process tree (not just the shell).
• Fetch pulls the current release list from each store so you can see which build numbers are already taken before you upload another one.
• Release notes are written once and delivered everywhere they can be: the TestFlight changelog, the Firebase App Distribution release note, and the Google Play changelog. They are also archived to release-notes/<version>-<build>.md.
• Version name and build number are written into export_presets.cfg, so a manual export from Project → Export produces the same build.

In the Release tab

Notes, tester groups and the debug flag are remembered per project, so they survive an editor restart — and they never leak into your other projects.

In the Setup tab

A checklist of everything the plugin needs — Ruby, Bundler, fastlane, Xcode, the Godot binary, export presets, the config resource, the fastlane files, installed gems, credentials, .gitignore, and every target's own validation — each row with a Docs ↗ link straight to the page that explains it.

Above it, the buttons that fix what is missing, greyed out once their step is done:

Nothing here ever overwrites a file that already exists — the fastlane files are yours to edit, and a plugin update leaves them alone.

Configuration

Three resources, edited in the Inspector, every field documented on hover:

Pick the export preset first and the rest follows. The platform is read out of the preset, and that decides which stores you can pick, how the build modes are labelled, and which fields are shown at all. Targets are ordinary resources, so add, duplicate and remove them freely.

Target fields are grouped as Source, Destination, Build, Native project and Testers — export preset, store, Play track, fastlane lane, column label, build mode, artifact path, debug build, enabled, Xcode project/scheme/plist/PCK paths, tester groups, and skip build processing wait for TestFlight.

Build modes

PCK only is the mode that matters once you have edited the Xcode project by hand — capabilities, entitlements, extra frameworks — because a full Godot export overwrites all of it.

What each destination does

Runs outside the editor, identically

Every release is a plain shell script driven by a plain KEY="value" file, so nothing is locked inside the editor:

# Repeat the last release the panel configured
addons/app_release/scripts/release.sh .release_tools/run_<target>.env logs/manual.log

# Or run just one phase: export, upload, or all
addons/app_release/scripts/release.sh .release_tools/run_<target>.env logs/manual.log upload

On CI, one headless command replaces the panel:

godot --headless --path . \
    --script addons/app_release/scripts/ci_release.gd -- \
    --target play_internal --version 1.4.0 --build "$GITHUB_RUN_NUMBER"

bash addons/app_release/scripts/release.sh .release_tools/run_play_internal.env

It runs the same validation the panel runs, patches the version, and writes the run configuration; both commands exit non-zero on failure, so a job fails where the problem is. No fastlane/.env is needed on a runner — the lanes read plain environment variables from your CI secrets.

Credentials

Secrets only ever live in fastlane/.env and in the key files it points at, both outside version control. The plugin does not read, store or transmit them — it hands fastlane the environment and gets out of the way.

Requirements

Windows runs through scripts/release.ps1, which ships untested — the plugin is developed on macOS. Bug reports welcome.

Documentation

• Repository and README — full setup, daily use, CI, troubleshooting
• TestFlight and the App Store — Apple Developer Program, App Store Connect API key, signing, ExportOptions.plist, build numbers
• Google Play — Play Console, keystore, the first manual upload, service account, tracks, AAB vs APK
• Firebase App Distribution — Firebase project, App ID, service account, tester groups
• Architecture — how the pieces fit, for contributors

Tested with GUT, RSpec and bats-core — GDScript, Ruby and shell each have their own suite, run on every push.

Get in touch

Found a bug, hit a store behaving differently than described, or want a feature? Open an issue on the repository — that is the fastest way to reach me, and it keeps the answer where the next person will find it. A log excerpt from logs/ plus your Godot and fastlane versions makes a report much easier to act on. Pull requests are welcome too.

Windows users especially: scripts/release.ps1 ships untested, so reports from there are genuinely useful.

More of my work: github.com/chris-prenissl

MIT licensed. Free, open source, and yours to fork.