- A Google Play Developer account. Sign up at https://play.google.com/console/signup
- A desktop or laptop. You cannot do this from a phone.
An iPhone (Swift) app cannot go to Google Play. To reach Android users, add an Android app to the same project, see Convert your app between iOS, Android, and web.
Watch the Android and Google Play walkthrough
The video starts with adding Android to an iPhone project, then shows the Google Play connection and build dialog. Continue below for the full build and upload instructions.Build the AAB in Rork
- Open your project and click Publish at the top of the page, then open the Google Play section.
- Click Connect Google Play and sign in with the Google account that manages this Play Console app.
- Click Build AAB for Play. Rork builds a release AAB signed with a persistent upload key that is unique to your project.
- When the build finishes, choose how to deliver it:
- Send to Google Play uploads the AAB to your internal testing track for you. This appears once Rork verifies that your Google account can manage the Play Console app.
- Download App Bundle for Play Console downloads the signed
.aabfile so you can upload it by hand. Download APK in the same dialog is for testing on a device: Play Console does not accept an APK, even renamed to.aab.
- If you downloaded the file, continue with Upload the AAB in Play Console below.
Rork needs the app to already exist in Play Console before it can send a build. If Rork says Create Play Console app, create the app listing first, then let Rork check access again.
Upload the AAB in Play Console
Log in to the Play Console at https://play.google.com/console/developers and click the Create App button on the right side.











If Google Play expects a different upload key
Rork shows Upload key doesn’t match Play Console when the app in Play Console was first uploaded with another key, for example builds you uploaded by hand before publishing from Rork. Google then refuses every App Bundle Rork signs, and rebuilding or sending again does not change that. The message names both keys by their SHA-1 fingerprint: the one Play Console expects and the one Rork signs with. To publish from Rork, reset the app’s upload key to Rork’s. The Play Console steps were checked on 2026-11-11:- On rork.com, open Publish, then the Google Play dialog. Download upload certificate is under the Upload key doesn’t match Play Console message; if the dialog does not show that message, send the build from it once. Sending needs edit access to the project, so with view access ask an editor to do this step. The link saves
upload_certificate.pem, the public certificate of the upload key Rork signs this project with. - In Play Console, open the app, then Protected with Play > Play Store protection > Manage Play app signing.
- In the Upload key certificate section, select Request upload key reset, enter a reason, upload
upload_certificate.pem, and select Request. - When Google confirms the new upload key, open the Google Play dialog in Rork again and send the build.