Uploading to Google Play is very straightforward. When you create an Android build, Twixl Publisher will generate two app files, one with extension .apk. and a second one with extension .aab (Android App Bundle).
.apk : this is the original extension that you can still use for side loading and testing on your Android device, or for in-house distribution.
.aab : this is the format that is required for new apps or for updates of existing apps.
1. Prerequisites
- You have a Google Play Developer account.
- Your app is built in Twixl, and you have downloaded the generated .aab file (in the build folder).
- You have access to the private key file (.pepk) and upload certificate if needed (also in the build folder).
2. Steps to deploy your app
2.1 Log in to the Google Play Console
- Go to https://play.google.com/console and sign in.
2.2 Create a New App (if this isn't an update of an existing app)
- Click 'Create app'.
- Fill in the required information (App name, default language, app type, etc.).
- Accept the developer declarations and click 'Create app'.
If you update an existing app, you can start with step 2.2.
2.3 Upload the .aab File
- In the left-hand menu > Test and Release > Production > Create new release.
- Under the "App bundles and APKs" section > Upload > select your .aab file (from the Twixl build folder).
If you would first want to create an internal testing release, select 'Testing' in the left bar menu in stead of 'Production'. The workflow is exactly the same as for a production release.
2.4 App Signing with Google Play (Handled Automatically)
By default, Google Play uses Play App Signing, which means:
- Google manages the App Signing Key used to re-sign your app before distribution so it is always possible to identify yourself as the rightful owner to update an app.
- You sign your .aab file using an Android keystore, which is already embedded in your Twixl-generated build.
No manual action is needed here unless this is your first release and Google asks you to provide the Upload Key certificate or a private key export (.pepk file).
If prompted:
- Always select: 'Let Google manage and protect your app signing key.'
- Upload the .pepk file (from your Twixl build folder).
Do not click 'Change app signing key' as it may revoke access for your current upload key.
2.5 Complete Release Details
- Add release notes.
- Click 'Next' through the steps (Device compatibility, App content, etc.).
- Make sure all policy sections (Data safety, Ads, Target audience, etc.) are completed under Policy.
2.6 Add artwork
Also upload your artwork, showcasing what to expect and attracting the user to download the app. Check the latest Google Play requirements and guide for artwork here.
2.7 Review and Publish
- Review your release.
- Click 'Start rollout to production' > 'Roll out'.
Google will process your submission and review it. If it's your first release, this may take a few days.
3. General remarks
Android Keystore
When you publish an app in the Google Play store, Google expects that app to be signed with a certificate so you can identify yourself as being the rightful owner of an app.
Twixl Publisher takes care of creating this "keystore" for you in the background. Every update of your app will have to be signed using the same keystore information (the app's "fingerprint"), otherwise it will not be accepted on Google Play. If you are migrating your app from another platform, check out this paragraph specifically. The keystore information is automatically saved as part of the build setting for your app on the platform.
If you move from another system and need to add an existing keystore to the Twixl platform, check this help article.
Advertising ID
Google is constantly changing the security approach during the upload process. Currently they ask for apps if they use advertising ID.
Here we advise to answer 'Yes' and indicate 'App functionality' and 'Analytics' in the list of options.
Cleartext traffic warning
Google Play might return a warning about cleartext traffic in the Pre-launch Report. Although we recommend to always use https, Google still allows http-requests but warns you about this only at this point. While we are aware this might change in the future, it is important you prepare to only use secure https links. For the time being, however, you can continue deploying your app in Google Play.