You have 2 options when exporting your app for iOS:

• Binary app (.ipa) – this iOS binary version can be published to the App Store etc.
• xCode project (source code) – you get HTML/CSS/JS + the PhoneGap library configured as an xCode projects.

The Appery.io platform provides a cloud based building app service that is programmed as a
Cordova app for iOS, which you can publish to the App Store. Before you build the binary file, make sure you have the following:

• Apple certificate (*.p12).
• Apple provisioning profile (*.provision)**.
  • A Beginner’s Guide to iOS Provisioning Profiles.
• Bundle ID (com.company.*)** – you can find it in your Apple certificate.

Appery.io comes with iOS binary file settings where you can configure everything you need to package the app for iOS. Go to your project, click App Settings > iOS Binary> Release. If the Release box is checked, JavaScript assets will be minified to reduce the binary size.

Generating iOS Certificates

The following links will help you generate the iOS certificate and submit the app to the Apple App Store.

Windows

• How to Create a Provisioning Profile and p12 for iOS in Windows

Mac OS

• App distribution guide (from Apple).

Certificate management can be accessed under the Resources tab. This is where all of your certificates are stored. Certificates can be imported or automatically generated (in the case of Android). Click Import certificate to upload the certificate from your desktop.

Once the file and platform are chosen, type the certificate name and its password. Click Import certificate to upload the file. The imported certificate will be listed with all of the others.

The certificate can be set to use by default. That means that all applications will use this certificate if another isn’t specified in App settings. Check Default to make the certificate used by default. If you are a team member, the team admin or team lead should give you permission for this action.

By clicking Export to zip the certificate will be downloaded as a ZIP archive. The archive will also contain additional text files with certificate passwords. Click Delete to remove the certificate.

Once the certificates are uploaded they can be chosen from the application settings. To choose a certificate for iOS binary, go to the App settings > iOS binary and choose a certificate. When [use default] is selected, the certificate marked as the default will be used. Certificates can be set for all binaries.

After registering with Apple as a developer you can get provisioning profile files or generate them. In the builder, click Change to open the Files Manager. At least one certificate must be provided to build a certain binary. In other cases, when exporting this binary in the builder you will get an error message.

Keys and Settings

The latest Cordova plug-ins (starting from the Libraries version 4.1 JQM and 1.1 Ionic) require adding keys and values when the app is being approved by the Apple App Store. The plug-ins that come bundled with your app, the keys are set by default. To view or modify the settings, click the Options button.

Here are some examples.

If you want to run an Appery.io app in the iOS Simulator:

1. Open [app_name].xcodeproj with Xcode.
2. Select the correct scheme to run: [app_name] > iPhone X or [app_name] > iPad X in the top-left part of the Xcode window.
3. Click Run in the top-left corner of the Xcode window (PushApp is the app name).

Running the Appery.io app on a iOS device is a more involved procedure than running it in the simulator. Notice that steps #1 and #2 are optional if you have already completed them for a different app.

1. Add the certificate to the keychain. Double-click on the .cer file and confirm adding the certificate. You can now see the certificate in the keychain window. Repeat this process for the distribution certificate.
2. Open the [app_name].xcodeproj with Xcode.
3. Select the [app_name] project file at the top of the project navigator.
4. Select the Build Settings tab, and proceed to the Code Signing section (PushApp is the app name).
5. Find the Code Signing Identity group and open it. If you use the app source code you built and exported from Appery.io, there should be 2 sub items – Debug and Release.

7. Open the General tab of the [app_name].xcodeproj. Find the Bundle Identifier parameter, and set its value to the corresponding value of the allowed application identifiers for your provisioning profile.
8. Select the correct scheme to run: [app_name] > [Your connected device's name] and click Run

This section lists a number of helpful hints when submitting your app to the App Store.

When submitting your app for review you might need to answer the following questions.

Question

• Is your app designed to use cryptography or does it contain or incorporate cryptography? (Select Yes even if your app is only utilizing the encryption available in iOS or OS X.)
• Does your app qualify for any of the exemptions provided in Category 5, Part 2 of the U.S. Export Administration Regulations?

Answer
Appery.io database is not encrypted bye default. If you encrypt the database data by any means in your app (by either iOS frameworks or any third-party), then you should consider answering "Yes" to both questions.

Question
Does this app use the Advertising Identifier (IDFA)? The Advertising Identifier (IDFA) is a unique ID for each iOS device and is the only way to offer targeted ads. Users can choose to limit ad targeting on their iOS device."

Answer
By default an Appery.io app does not use Advertising identifier.

Troubleshooting iOS Build

The following is a list of the most common reasons the iOS build might fail. Please review them and try to export again if you come across any issues:

1. Bundle ID doesn’t match the Provisioning profile – Please check to make sure your Bundle ID matches the Provisioning profile.
2. Bundle ID incorrect format – The Bundle ID provided has an incorrect format. The Bundle ID format is: com.companyName.appName. This is NOT a valid Bundle ID: XZCSDF.com.companyName.appName.
3. Expired certificate – Please make sure your certificate hasn’t expired.
4. No certificate uploaded – Please make sure you have uploaded a valid certificate.

Troubleshooting iOS Mobile Submissions

Check the app permissions. For instance, if you have telephony selected in UIRequiredDeviceCapabilities (Project > App settings > iOS keys), and you are submitting the app for the iPad as well, the App Store will not accept the app as you cannot make calls from an iPad.