Loading…

    How to publish your app to Google Play

    Written by the Fastshot team from the Fastshot user guides. Updated .

    Connect Google Play once, then build and choose a track: Internal, Closed, Open or Production. Google Play does not let a build service upload an app’s first build, so upload that first AAB by hand in Play Console. After that, Fastshot can send later builds to the track you pick.

    Start building your app

    Fastshot builds the AAB that Google Play takes and can send it to a track. A few Google Play rules shape the first release.

    1. 1. Connect Google Play

      Connect once, in the chat setup card (Connect Google Play) or under Google Play on the Android tab of the Publish view, and have an app in Play Console. Sign in with the Google account that owns the Play Console, or use a service account’s JSON key.

    2. 2. Build with Download only first

      Google Play does not let a build service upload the first build of an app. For an app with no upload yet, build with Download only, then upload that build’s AAB in Play Console by hand.

    3. 3. Match the package name

      Google Play package names are permanent: an app takes the package name of the first AAB uploaded to it. For an app that already has uploads, set the project’s Android package name to that exact name before building. A build under another name is a different app to Google Play.

    4. 4. Choose where the build goes

      Choose Download only, or a Google Play track: Internal testing, Closed testing, Open testing or Production. A build for Google Play is made first, then Fastshot sends its AAB to the track.

    5. 5. Read what Google Play did

      The card says Sent to Google Play with the track; As a draft if the app is still a draft in Play Console; Send for review in Play Console if the last update was rejected; or Not sent, with the reason and, where fixing it in Play Console is enough, Send again.

    6. 6. Keep version codes rising

      Google Play accepts each version code once per app, and an update needs a higher one. Each build’s version code is higher than the last. For an app with releases, set android.versionCode in app.json to the highest code Google Play already holds.

    Good to know

    • Android builds are signed with one keystore per account. An app that already exists in Google Play has to be signed with the upload key Google Play knows for it.
    • Once connected, the card checks with Google Play whether it can take builds of the project’s package name and says what is missing.
    • Builds are part of the paid plans.

    Frequently asked questions

    How do I publish my app to Google Play?
    Connect Google Play, build, and choose a track. Google Play does not let a build service upload an app’s first build, so upload that first AAB by hand in Play Console. Later builds can go to the track you choose.
    Why was my first build not sent to Google Play?
    Google Play does not let a build service upload the first build of an app. The AAB stays downloadable, so upload it by hand in Play Console; later builds can be sent.
    Can I change my Android package name later?
    Google Play package names are permanent: the app keeps the name of the first AAB uploaded to it. Builds made under a different name are a different app to Google Play and are refused for this one.
    What is the difference between an APK and an AAB?
    An APK installs directly on an Android device. An AAB (Android App Bundle) is the file Google Play takes, and an Android build nearly always makes one.

    Related: AAB builder, Build an APK without Android Studio

    Next lesson: How to publish an iPhone app to the App Store

    Start building your app