Learning & Support


Android: About the Keystore

Twixl Support Team Updated: - Created :


    As of Twixl Publisher 15.4, Twixl Android apps will now be Android App Bundles (with extension .aab instead of previously .apk). This requires that you use the new Google Play App Signing method in order to publish these .aab files.

    When you publish an app in the Google Play store, Google expects that app to be signed with a certificate. Before Twixl Publisher 15.4, when you created an Android app, we took care of creating this "keystore" for you in the background. Every update of your app had to be signed using the same keystore information (the app's "fingerprint" so to speak), otherwise it would not be accepted on Google Play. In this situation, if you ever lost your keystore, you needed to publish a new app with a new package name, and could no longer update your existing app.

    Google Play App Signing solves that problem (requires Twixl Publisher 15.4 or higher). If you lose your keystore or think it may be compromised, Google Play App Signing makes it possible to request a reset to your upload key, so you can keep updating your app.

    Migrating your Google Play app from another platform, such as Adobe DPS, etc.

    If you are moving to Twixl Publisher from a platform like Adobe DPS, you will have created an Android keystore using the Keytool via terminal, according to the instructions outlined in Adobe's documentation

    During that process you generated a keystore with an extension .p12. In order to update your existing Adobe DPS app to an app created with Twixl Publisher, you can use the 'Import' option in the Code Signing tab of the build settings for that app. When importing the .p12 keystore, you will also need to provide the password you used to create it. For more info on how to manage your Build Settings on the Twixl platform, see: Build Settings overview

    Was this article helpful?

    0 out of 2 found this helpful