Make sure the Profile Name follows the standard naming convention: App Name App Store Distribution

Click Generate

Download it

Install the provision profile on your computer by double-clicking

Keep this file somewhere safe

Create App Store Listing

Start in your browser, navigate to App Store Connect

Log in

Click My Apps

Click the plus (+) button in the top left of the screen

Click “New iOS App”

Bundle ID: choose the one created on Developer Portal

For convenience, make the SKU match the Bundle ID created earlier

Click Create to create the first version listing

Resign and Upload the IPA

Once you have received the IPA from Entegy create a new directory and place the IPA inside.

In the developer centre create and/or download an App Store provisioning profile.NB: take note of the distribution certificate used to create the provisioning profile. The certificate used can be seen in the provisioning profile edit menu (usually the latest certificate).

Take the IPA and unzip it (rename it to a zip file and extract it into the same directory as the IPA.)

Now there will be a payload folder with OneApp.app inside.

Move the provision to the same directory as the payload folder.

Generate an entitlements plist using the following process:

Rename downloaded mobile provision to embedded.mobileprovision

Open up a new command line window in the directory.

Check that you are in same directory

Generate a provision plist using the following command with the provision directory:security cms -D -i /embedded.mobileprovision > provision.plist

Now Create a new plist with the app entitlements using the following command:/usr/libexec/PlistBuddy -x -c 'Print :Entitlements' provision.plist > entitlements.plist

Where provision.plist is the plist generated from the previous command.

This leaves you with a directory with the following items

The Provided IPA (Now a ZIP file)

The Payload folder

The embedded.mobileprovision file

The provision.plist file

The entitlements.plist file

Copy embedded.mobileprovision into the OneApp.App file. (Right click the .app file and click show package contents.)

Navigate back up to the directory with the provisioning files.

Open up a new command line window and view existing distribution certificates using the following command:security find-identity -v

This will give you a list of certificates installed in the keychain. Look for the ID of the certificate used when creating the provisioning profile in the first step. The list item should look something like this:30) LQ47FXL4SPT5PZ3KGQK8J2WGCBWUN99NB0C5KWAM "iPhone Distribution: YOUR COMPANY PTY LTD(OPTIONAL_TEAM_ID)"

Before code signing ensure that there is no existing signing by removing the signing directory. This can be done by executing the command:rm -rf Payload/OneApp.app/_CodeSignature/

Take the ID from the entry (in this case LQ47FXL … 5KWAM). Using that ID go back to the command line in the provisions directory and execute the following command:/usr/bin/codesign -f -s IPHONE_DISTRIBUTION_ID --entitlements /PATH/TO/entitlements.plist Payload/OneApp.appWhere IPHONE_DISTRIBUTION_ID is the ID from the previous command. And the paths point to the corresponding files.

The OneApp.app structure should now be signed with the provided distribution certificate.

The payload now needs to be bundled back up into an IPA. This can be done using the following command:zip -qr app-resigned.ipa Payload/

Drag the ipa onto the program window, and wait for “Deliver” button, then click.If the process fails it is likely due to the wrong provisioning profile used or the wrong distribution certificate being used. It is required that the certificate used is the one used when creating the provisioning profile in the dev centre. Press next and wait for the bundle to upload. Once the application uploads continue the store submission process as usual.

Fill In Version Information

Enter your store information

Select the build you wish to tie to the version. This will take a few minutes to appear after you upload it

Fill in pricing information

Click Save

Submit Version for Review

Select the release type

Manual release – after the app is accepted, a Release button will appear

Automatic release – as soon as the app is accepted, it will be released

At the top of the page, select Submit for Review

Answer the questions and click Save

It can take a few days for your App to be approved

If your app was not approved, review the notes in the Resolution Center and make any necessary changes to the app or version information then resubmit

Provide Entegy with your Apple push notification certificate

We require this to enable custom notifications for your app. This process can only be completed after (or during) you have created an App ID on the Apple Developer Center. You need to upload the push certificate in the store listing page in Core.

You should see an entry called “Apple Push Services: “ followed by the bundle ID of the app. It should have a dropdown to the left which indicates it is matched with the private key

If you can’t find the certificate or it doesn’t have a private key, it may be in a different Keychain from the one with the private key. You need to click and drag the certificate into the Keychain with the private key

Right-click on the complete certificate and export it as a .p12 file, specifying a passwordMake sure you save the .p12 file and password securely. You will require both of these items when you create your build’s store listing.