#Android studio apk store app android#

Now when Code Build runs the buildspec.yml file, it will be able to export the specified variables.Īs things stand right now, when your pipeline runs, Code Build will be able to download the private key to sign and build your Android app and upload the signed bundle to an S3 bucket.

There you'll see an option to add environment variables through key value pairs. On the screen that pops up once you do this, select the Additional Configuration dropdown. Next, select Edit > Environment like in the screenshot below: To do this, first go to the AWS Code Build console and pick your build project for your Android app. Finally, run Gradle's release command from the command line.īefore you can run this script in Code Build, you'll need to add the variables to the Code Build environment. Next, export all the variables required for the adle configuration to work correctly. It fetches the release key from the bucket specified and saves it into a local file on the Code Build server into the location specified. app/build/outputs/bundle/release/app-release.aab Open adle within your app directory in Android Studio and add the following code block to it: android /app/releaseKey.jks Throughout this tutorial make sure to use the correct name and alias for your key. You can also choose whatever alias you want. Generate a private key using keytool like this: keytool -genkey -v -keystore my-release-key.jks -keyalg RSA -keysize 2048 -validity 10000 -alias my-alias Google has fairly decent documentation on it that you can find here.

#Android studio apk store app how to#

The main thing to figure out is how to sign the Android App Bundle. You'll be uploading this to an S3 bucket soon. Once you've created your service account and given it the appropriate permissions, make sure to download the service account key and keep it safe. To see how to create a service account and give it access to the Google Play Publisher API, look here. You can read more about how Google uses OAuth2.0 for server to server communication here. To be able to use the Google Play Publisher API, you will need a Google Play Service Account key.Ī service account is an account that can act on your behalf when servers are communicating with each other. How to Get Your Google Play Service Account Key Once it gets a 200 response, the Lambda will then trigger a Slack notification. Uploading the bundle to S3 will trigger a Lambda, which will download the bundle and upload it to the Play Store using the Google Publishing API. The Code Build project will sign the Android app from the command line and upload the artifact to an S3 bucket. Pushing to the master branch of your Android app repository is going to trigger Code Build. This Code Pipeline will have Code Build as one of its stages. The above image shows you a general overview of how we'll structure the whole thing.Įssentially, there needs to be a Code Pipeline set up on AWS for your Android repository. Here are the resources we are going to be using for this tutorial: This is a valuable use of your time for a number of reasons, like creating observability and prioritizing processes. Once we've uploaded the app bundle, we'll trigger a Slack notification. We'll use Android Studio and AWS as a cloud infrastructure provider. In this article, I'm going to explain how to automatically upload an Android App Bundle (.aab file) to the Play Store's beta track.