To publish a Godot game on Google Play, you export a signed release Android App Bundle (.aab) from Godot and upload it to Play Console. If you publish from a new personal developer account, the first stop is a closed test, where at least 12 testers have to stay opted in for 14 days in a row before you can apply for production access.
Most Godot export guides end when the .aab file lands on your disk. This one keeps going: the export settings that Play Console cares about, the signing mistake that causes most failed uploads, and how to get a game through the two weeks of testing.
Export settings Google Play expects from Godot
Google's Android guide for Godot is clear on the format: for builds you intend to upload to Google Play, use an Android App Bundle. In the Android export preset (Project, Export, Add, Android), set Export Format to Android App Bundle (.AAB). An APK is fine for testing on your own phone, but it's not what Play Console wants.
An AAB export needs the Gradle build path. Install the Android build template into your project first, from the Project menu, then turn on the build option in the preset. Google's guide calls it Use Custom Build. Recent Godot 4 versions label it Use Gradle Build, so look for either name. Godot's own docs also list OpenJDK 17 among the prerequisites for Android export.
Two more settings matter for the upload. Google Play requires 64-bit architectures in submitted App Bundles, so keep arm64-v8a enabled. And Unique Name must match the package identifier you use for the app in Play Console. You can't change it after the first upload, so pick it with care.
Checklist of Godot Android export preset settings for Google Play: AAB format, Gradle build, 64-bit, unique name, version code, release keystore, Export With Debug unchecked
Seven settings to check in the Godot Android export preset before uploading to Play Console.
Fix the Android App Bundle not signed error
A common Godot question is why Play Console rejects the upload with a message that the Android App Bundle is not signed. In most cases the bundle was exported as a debug build, or the release keystore fields in the preset were empty.
Create a release keystore once. Google's guide points to Android Studio's upload key flow for this. Then fill in the three release fields in the export preset: the keystore path, the user (the key alias), and the password. When you export, uncheck Export With Debug. That checkbox is what turns the export into a release build.
Keep the keystore and its password somewhere safe, and note that export_presets.cfg can contain those credentials, so don't commit it to a public repository. With Play App Signing, Google holds the app signing key and your keystore acts as the upload key, but you still need it for every update.
Upload the build to a closed test
In Play Console, create the app, complete the setup tasks it lists, and open the closed testing track. Create a release, upload the .aab, add your testers by email list or Google Group, and send the release for review. Once it's approved, share the opt-in link.
Each new upload needs a higher version code than the one before. Raise the version code in the preset's version settings before every export, or Play Console will refuse the file. You can upload new builds during the test. Testers who stay opted in keep counting.
Four steps from Godot export to production on Google Play: export, upload to closed testing, test with 12 testers for 14 days, apply for production
The path for new personal developer accounts: the export is only the first of four steps.
Getting a Godot game through 12 testers and 14 days
Google's rule for new personal accounts is a minimum of 12 testers who have been opted in continuously for at least 14 days. A tester who leaves early doesn't count, and one who rejoins starts their 14 days again. Start with 15 to 20 people, so one dropout doesn't put you under 12.
Games have a harder time here than utility apps. A tester needs a reason to come back on day 9. Tell testers what to try: reach a certain level, test the controls on their screen size, play with sound off, report where they got stuck. Google's production application asks how testers used the app and what feedback you collected, so keep those notes.
Performance is the other thing to watch. A game that runs well on your phone may stutter on an older device. Ask testers for their device model when they report a problem, and fix the worst issues with a new build while the test is still running.
Where to find testers for a Godot game
Friends and family rarely add up to 12 people who stay for two weeks. The Godot forum has threads from developers asking for testers for this exact requirement, and other solo developers are in the same spot as you.
PeerPlay is a free exchange built on that idea. You test another Android developer's app, and they test yours for the 14 days. Get your signed AAB into a closed test first, then add the game to PeerPlay and bring a few spare testers in before day one.
Top comments (0)