Signing on Android

When Enhancing your app, you are presented with a few different options for signing. In order to publish to Google Play, you must sign your app with a valid certificate, either by uploading your keystore during the Enhance process or by choosing to leave the app unsigned and manually signing it yourself after downloading your Enhanced app. The options are:

  • Upload a certificate for signing: We will asymmetrically encrypt your certificate in a keystore with a new password for maximum possible security on our end. This will be used to sign your app for you during Enhancing, and is the easiest option available that will allow you to publish your app. If you have already published your app and will be updating it, the keystore MUST contain the same certificate originally used to sign your app, otherwise it will be rejected by Google Play.
  • Sign for testing only: We will sign your app with the android debugging certificate, allowing it to be tested on your Android devices. If you wish to publish it after, you must sign it with a valid certificate before Play Store submission.
  • Leave your app unsigned: If you leave your app unsigned, you will have to sign it manually to allow you to run it on your devices. This is a suitable option if you are an advanced user and would like to manage signing yourself.
Important Note: Your app must be signed for release with a certificate from a valid keystore, either by uploading your keystore to Enhance or manually, before it can be accepted into the Google Play store.

Signing on iOS

Signing for iOS with Adobe Air requires a P12 format signing certificate, and Enhance is no different. Adobe provides instructions for getting a P12 signing certificate for iOS here.

You will need to upload the same P12 file used for signing your Adobe Air iOS application during the Enhance process to sign your iOS app.