In this article you can find more information about tasks associated with generating and publishing iOS and Android mobile apps:
- For both Android and iOS, check how you can define a custom domain name for your mobile app;
- For iOS, check how you can enroll as an Apple Developer, and learn more about creating certificates and provisioning profiles;
- For Android, check how to create a keystore and some of the best practices for managing one.
Customizing the Mobile App Domain Name
In some cases you might need to change the domain name associated with your mobile app, like when you have internal security policies dictating that different mobile apps should have different associated domain names and SSL certificates.
You can customize the domain name for each mobile app in Service Center. By default, OutSystems uses the hostname set for the environment in Administration > Environment Configuration.
Note: The domain name set for your mobile app should match the Common Name (CN) or a Subject Alternative Name (SAN) specified in the SSL certificate you have configured in your web server for serving HTTPS requests.
To define a different domain name for a mobile app, do the following:
In Factory > Applications, click the name of the mobile app you want to configure.
In Native Platforms tab, click the "Change" link in the Domain Name column.
Enter the new domain name for the mobile app and click Apply.
You will need to regenerate the mobile app for the changes to take effect.
Enroll as an Apple Developer
The first step to generate an iOS app package (IPA) is to register as an Apple Developer. You have two types of developer programs that you can choose according to your requirements:
Apple Developer Program – The standard Apple Developer account allows you to build applications and distribute them on the public App Store, potentially reaching millions of end users all over the world. Your applications must follow specific guidelines in order to get approved by Apple.
Apple Developer Enterprise Program – With the Enterprise Developer Account, you are not obliged to follow the App Store Guidelines, but you can only distribute your applications to employees within your organization. The apps cannot be submitted to the public App Store, they should be distributed by an internal enterprise store or an MDM (Mobile Device Management) solution.
After understanding the differences between Apple Developer and an Apple Developer Enterprise program, you should enroll in one of them. If you have requirements for both use cases, you can create two different accounts, one for the Developer Program and one for the Enterprise Program. Then, depending on the application you want to build, you should use one or the other.
You can also enroll as an individual or an organization. If you wish to enroll as an organization you must provide additional information and the process can take a little longer but allows you to publish applications on behalf of your organization. If you choose the Apple Developer Enterprise Program, you must always enroll as an organization. Note that enrolling as an individual or organization has different annual fees.
To learn more about the iOS Apple Developer account, read the OutSystems post in Medium "Cruising through the Complexities of Signing Native Mobile Apps" or check the iOS official documentation.
Create a Certificate
Log in your Apple Developer account and select the option Certificates, IDs & Profiles.
The certificates you can use:
- For a development certificate, use the
iOS App Developmentcertificate type;
- For a production certificate, select the
App Store and Ad Hoc(for Apple Developer Program) or the
In-House and Ad Hoccertificate type (for Apple Developer Enterprise Program).
To create the certificate (
.p12 extension format):
Generate the Certificate Signing Request (CSR) File
To create your certificate you need to provide a CSR file. Apple will provide you with instructions on how to create one if you have an Apple machine, but if you don't have a Mac here's how you can do it on a Windows machine:
- Download the most recent version of OpenSSL;
- Start a new command prompt (Start → Run →
Execute the command to set the folder used on the OpenSSL installation:
Now call the OpenSSL to create the CSR and the private key:
<path_to_openssl_bin>\openssl.exe req -out <CSR_file_name>.csr -new -newkey rsa:2048 -nodes -keyout <privateKey_name>.key
<CSR_file_name>is the name for the CSR file and
<privateKey_name>is the name for the private key file;
After you run the command on your computer, it will generate a new CSR file with a public key embedded and a private key.
Download the CER and Create the P12 Certificate
Now that you have created the CSR file, go back to the Apple Developer Portal and upload the file. Follow the next steps on Apple's page to create a new Certificate (CER file format). This certificate includes both public and private keys and can be used for multiple apps.
Be sure to back-up the CSR and the CER files in a safe place.
If you're using a Mac, download the CER file, install it and export to the P12 file format. If you are using a Windows machine, open the command prompt and execute the following commands:
<path_to_openssl_bin>\openssl.exe x509 -in <certificate_cer>.cer -inform DER -out <app_pem_file_name>.pem -outform PEM
<certificate_cer> is the name of the certificate downloaded from Apple and
<app_pem_file_name> is the name for the PEM file.
Now you'll need to use the file you've just generated to run the following command and create the P12 file:
<path_to_openssl_bin>\openssl.exe pkcs12 -export -inkey <privateKey>.key -in <app_pem>.pem -out <app_p12>.p12
<privateKey> is the file generated when creating the CSR file,
<app_pem_filename> is the name of the created PEM file in the command executed before and
<app_p12> is the name you want for the P12 file.
You will be asked for a password, create one and remember or store it somewhere — you'll need to insert it in OutSystems. The P12 file created in the last step is the certificate to generate the iOS app.
Create a Provisioning Profile
A provisioning profile allows your application to be launched on Apple devices and use app services like Apple Pay or push notifications.
The provisioning profiles you can use are:
iOS App Development: this Development Provision Profile allows you to generate a development version (containing debug information) of your mobile app that can be installed and launched in a given set of devices for development tests. Only the devices specified for the provisioning profile will be able install and launch the app. If a given user's device is not authorized to install the app, the user will get a "Unable to Download App" alert message;
Ad Hoc: this Distribution Provisioning Profile allows you to generate a release version of your mobile app that can only be used in a limited list of devices. Use this profile to distribute your application to a limited group of end-users. Only the devices specified for the provisioning profile will be able install and launch the app. If a given user's device is not authorized to install the app, the user will get a "Unable to Download App" alert message;
App Store: this Distribution Provisioning Profile, available for the Apple Developer Program, allows you to generate a release version of your mobile app that can be published and distributed through the App Store. Use this profile when your application has been thoroughly tested and is ready to be made available to everyone through the App Store;
In-House: this Distribution Provisioning Profile, available for the Apple Developer Enterprise Program, allows you to generate a release version of your mobile app with no limitations on which devices it will run. Use this profile when your mobile app will only be distributed inside your company. It will not be subject to review by Apple because you will not be able to submit it to the App Store. However, you will have to handle the app distribution on your own.
To create a provisioning profile (
.mobileprovision extension format):
- Access your Apple Developer account and select the option Certificates, IDs & Profiles;
- Select Provisioning Profiles;
- Select the type of provisioning profile you want to generate, as explained above;
- Provide the information requested during the generation process. You will have to enter an App ID, which certificates to include in the profile and, for some types of provisioning profiles, which specific iOS devices will be allowed to launch mobile apps associated with the provisioning profile being generated. Note that if you later register additional devices in your Developer Account or add any app services, you will need to create a new provisioning profile and generate the mobile app again to propagate your changes;
- At the end of the generation process, you will be able to download the generated provisioning profile for later use.
In order to generate iOS mobile apps in OutSystems you will be asked to provide a provisioning profile along with one of the certificates that you associated with it in the steps described above.
Create a Keystore
A keystore is a file that stores a security key. You can use it to sign your Android apps. Signing the app is the way to identify the author of the application for an Android app. Check more information about it in the official documentation.
After you verify the availability of the keytool command, open a computer command prompt (Start → Run →
cmd.exe) and, if the keytool command is not available in the path, navigate to the Java "bin" directory. Execute:
keytool -genkey -v -keystore <keystore_name>.keystore -alias <alias_name> -keyalg RSA -keysize 2048 -validity 10000
<keystore_name>is the name you want to give to the keystore;
<alias_name>is the identifier name for your key.
Throughout the command execution, it will ask you some questions. Two of the questions are the keystore password and the alias password. The rest of the answers identify the owner of the apps using this keystore.
After the command executes, a new file named
<keystore_name>.keystore is going to be present in the folder location where you've executed the command.
Keystore File Recommended Practices
Store the keystore file in a place where you'll remember it because you'll need to use the same keystore to sign the app when updating it to publish to the Google Play store;
Create your keystore with a long validity (in the command example we are extending the validity of the keystore till 2044). If your keystore expires, you can't renew it and so you won't be able to update your app;
Keep your keystore file in a safe place. In case third-party has it can sign and distribute apps under your identity.
For more information, check the Android official documentation.