iOS and Android apps that you build and download in the Apps section of the On-Demand Portal need to be signed so that you can load them onto any device or submit them to any store. Windows apps do not need to be signed.
Signing iOS apps is available only on Mac OS computers at this time. You can use either Mac OS or Windows to sign Android apps.
- The .ipa file downloaded from the Apps section of the Portal.
- A development or distribution certificate stored on your computer's keychain. (If the certificate was created on a different computer, you can obtain the .p12 certificate and double-click it to install it to your keychain. You need to specify the certificate password.)
- A development provisioning profile that includes device IDs for testing or a distribution provisioning profile.
- Java 7 (or later). Go to the Java SE Downloads page, and download and install the JDK.
- Xcode 8.
- A Mac OS computer. (Xcode 8 requires Mac OSX 10.11.5 or later.)
For details on creating these required files, see iOS Publishing Guide for AEM Mobile.
- The unsigned .apk file downloaded from the Apps section of the Portal.
- A valid .p12 certificate for signing Android apps.
- Java 7 (or later).
- A Windows or Mac OS computer.
For details on creating a .p12 certificate for Android, see Android Publishing Guide for AEM Mobile.
- Your Mac OS computer must include Xcode 8 (or later). Make sure that you launch Xcode at least once before signing an app.
- Your Windows or Mac OS computer must include Java 7 JDK or later.
- The Mac OS computer must include the development or distribution certificate in its keychain. You can double-click a .p12 certificate and specify the password to add it to your Keychain Access utility.
See the requirements section above for details.
Click the Download the AEM Mobile Signing Tool icon in the upper right corner of the Apps section of the Portal. The same signing tool works for signing both iOS and Android apps.
Launch the App Signing Tool, click iOS or Android, specify the source app and certificate information, and sign the app.
For iOS apps, choose the development certificate and development provisioning profile for test apps. Or, choose the distribution certificate and distribution provisioning profile for submitting apps to the App Store.
The first time you sign an app, you must click Allow or Always Allow in order to complete the signing process. If acceptable, click Always Allow to avoid these prompts when signing apps.
For Android apps, if you specify a .p12 certificate, specify the password. If you specify a .keystore file, specify the keystore password, the private key alias, and the private key password.
Load the signed app onto your device, or submit it to the store.
The AEM Mobile Signing Tool does not have an iOS option
If you see only an Android tab, it's likely that you're using a Windows computer. Signing iOS apps requires a Mac OS computer.
Signing the app requires the system admin password to be entered multiple times
In the Keychain Access utility, make sure that your certificate is added to the "login" keychain, not the "System" keychain. You can drag and drop the certificate to move it.
I installed the new version of the signing tool, but I still see options for a p12 certificate and password
Uninstall (trash) the previous version of the signing tool, and then install the new version.
(iOS) Error signing the app
If you get an error signing the app, you can view the log file for more information. The aemm-sign-tool.log file is saved in your home folder.