1--- 2title: Submitting to the Google Play Store 3sidebar_title: Submitting to Google 4--- 5 6This guide outlines how to submit your app to the Google Play Store from your own computer and from CI. 7 8## Prerequisites 9 10- A paid developer account is required — You can create a Google Play Developer account on the [Google Play Console sign-up page](https://play.google.com/apps/publish/signup/). 11- You have to create a [Google Service Account](https://cloud.google.com/iam/docs/creating-managing-service-accounts) and download its JSON private key. 12- After that, you'll have to create an app on [Google Play Console](https://play.google.com/apps/publish/) and upload your app manually at least once. 13- You will also need to have EAS CLI installed and authenticated with your Expo account: `npm install -g eas-cli && eas login`. 14 15### Creating a Google Service Account 16 17See [expo.fyi/creating-google-service-account](https://expo.fyi/creating-google-service-account) to learn more. 18 19### Manually uploading your app for the first time 20 21Before using `eas submit -p android` for uploading your builds, you have to upload your app manually at least once. This is a limitation of the Google Play Store API. 22 23See [expo.fyi/first-android-submission](https://expo.fyi/first-android-submission) to learn more. 24 25## 1. Build a standalone app 26 27You'll need a native app binary signed for store submission. You can either use [EAS Build](introduction.mdx) or do it on your own. 28 29## 2. Start the submission 30 31To submit the binary to the Play Store, run `eas submit -p android` from inside your project directory. The command will lead you step by step through the process of submitting the app. See the [Configuration with eas.json](./eas-json.mdx) page to learn how to pre-configure your submission. 32 33> Although it's possible to upload any binary to the store, each submission is associated with an Expo project. That's why it's important to start a submission from inside your project's directory - that's where your [app configuration](../workflow/configuration.mdx) is defined. 34 35To upload your Android app to the Google Play Store, run `eas submit --platform android` and follow the instructions on the screen. 36 37The command will perform the following steps: 38 39- Log in to your Expo account and ensure that your app project exists on EAS servers. 40- Prompt for the Android package name unless `android.package` is set in the app config. 41- Ask for which binary to submit. You can select one of the following: 42 43 - The latest finished Android build for the project on EAS servers. 44 - Specific build ID. It can be found on the [builds dashboard](https://expo.dev/builds). 45 - Path to an **.apk** or **.aab** archive on your local filesystem. 46 - URL to the app archive. 47 48 > This step can be skipped if one of the following CLI parameters is provided: `--latest`, `--id`, `--path`, or `--url`. 49 50- Unless `serviceAccountKeyPath` is provided in **eas.json**, you will be prompted for the path to your Google Services JSON key. 51- The summary of provided configuration is displayed and the submission process begins. The submission progress is displayed on the screen. 52- Your build should now be visible on Google Play Console. If something goes wrong, an appropriate message is displayed on the screen. 53 54## Submitting your app using CI 55 56The `eas submit` command is able to perform submissions from a CI environment. All you have to do is ensure that all required information is provided with **eas.json** and environment variables. Mainly, providing the archive source (`--latest`, `--id`, `--path`, or `--url`) is essential. Also, make sure that the Android package name is present in your [app config file](/workflow/configuration.mdx). 57 58For Android submissions, you must provide the path to your Google Services JSON key using the `serviceAccountKeyPath` key in **eas.json**. You may also find the `track` and `releaseStatus` parameters useful. 59 60Example usage: 61 62```sh 63eas submit -p android --profile foobar 64``` 65 66## Automating submissions 67 68To learn how to automatically submit your app after a successful build, refer to the ["Automating submissions" guide](/build/automating-submissions.mdx). 69