IMPORTANT INFO ABOUT GOOGLE PLAY APP SIGNING
Read this important information about Google Play App Signing here, before you start uploading applications to Google Play!
When you publish an app in the Google Play store, Google expects that app to be signed with a certificate. When you create an Android app with Twixl Publisher, we take 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" so to speak), otherwise it will not be accepted on Google Play.
The keystore information will be saved as part of the build setting for that app on the Twixl platform. This means that, if you migrate to a different machine, you only need to add the account in the macOS app. We take care of the rest! For more info on how to setup your account in the macOS app, see: Add your Twixl account
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