1. Go to the Certificates page in your Apollo Apps backend

If the iOS version of your app has been generated at least once, you can go to the Publish > Certificates > iOS in your Apollo Apps backend to update your Apple Certificates.

There, click the "Edit my certificates" button at the bottom of the screen.  
After clicking this link, a warning message will appear asking for a confirmation. Click "Continue". You are now taken back to Step 0 in your iOS app submission process.  

Attention! This link is not available if the iOS version is "Ready to be tested" right after compilation. In this case you have to go to the menu Publish > Publication > iOS and click Modify to unlock the back office.
You will also won't be able to update the certificates if the status of the app is Validating for the App Store. 

2. Step 0 / Step 1 / Step 2 - Distribution Certificate

You have 2 choices, depending if the Distribution Certificate of your app is still valid (you may just want to update your Push Certificate), or if it is not.  

Case n°1: The Distribution Certificate is still valid
Step 0: select the statement which corresponds to the status of the app (most of the time, the app is already published on the store).
Step 1: Select "I want to use an existing distribution certificate", then click on Next Step without choosing anything else. The current distribution certificate will be used.
Step 2: Click on Next Step without choosing anything else. The current distribution certificate will be used.

Case n°2: The Distribution Certificate is expired
Step 0: select the statement which corresponds to the status of the app (most of the time, the app is already published on the store).
Step 1: Select "I want to create a new distribution certificate"
Step 2: Follow all the described steps. 

2.2: Click on the green button to generate a .CSR file, which will automatically be downloaded on your computer.

2.3: Login to your Apple Developer account https://developer.apple.com/account/ios/certificate/
Under the menu Certificates, use the top right + sign to add a new certificate.
Choose under the Production section “App Store and Ad Hoc”.  Then follow the steps until you are required to upload a .CSR file.

2.4: Upload the .CSR file previously downloaded from your Apollo Apps backend, and click on "Generate".
This will generate a .CER file.

Download that .CER file and go back to the submission process in your Apollo Apps backend.  

2.5: Delete the existing Distribution Certificate in the backend and upload the .CER file you have just downloaded.

Then go to the next step.

3. Step 3 - Use your existing App ID

Each application has a unique App ID, and this app already has one.

Step 3: Provide the Bundle ID of your app and its current version number on the store, as indicated on the screen.  
Then, go to the next step.

(If your app is not published on the store and you have chosen "New" at step 0, just skip Step 3 and go directly to the next step. )

4. Step 4 - Push certificate

4.1: Generate the .CSR file in your Apollo Apps backend. The file will be automatically downloaded to your computer.

Ignore Steps 4.2 and 4.3
Instead, select the App ID of the existing app, and click on Edit. Scroll down, and you should see the screen here bellow.
Make sure the line Push Notifications is checked, and under "Production SSL Certificate" click on the button Create Certificate.

4.4: Upload the .CSR file downloaded in your backend, and click "Generate".

4.5: When the Apple Push Service certificate is generated, click on "Continue" and then on "Download" to save the .CER file on your computer.

4.6: Delete the existing Push Certificate in the backend, upload the .CER file and go to the next step.

Attention: Only one push certificate per App ID is allowed, otherwise push notifications will not work in your application.
If there is an existing push certificate associated to the App ID, revoke it before creating a new one.

5. Step 5 - Update your Mobile Provision File (App Store)

If you update any of your Apple Certificates, you have to update your Provisioning Profiles in your Apple Developer Account, and replace the existing ones in the backend.

In the backend, skip steps 5.1 to 5.3, and go directly to step 5.4.

In the menu "Provisioning Profiles" https://developer.apple.com/account/ios/profile/, select your existing provision file for App Store. It should have the same name as your Apollo Apps project (in the example, it is debsapp) and click on Edit.  
The existing provision file can be Invalid (like in the example), or Expired.

Then, select the right App ID (it should already be the right one) and distribution certificate.  

- If you have created a new Distribution Certificate for this app, select it. If you have more than one, it is the one with today’s date.
- If you have used an existing Distribution Certificate, select the one with the same date as the Distribution Certificate you see in the Publish > Certificates > iOS menu in your backend.

Click on Generate, and download the new mobile provision file.

5.4: Delete the existing mobile provision file in the backend and upload the new one, then go to the next step.

6. Step 6 - Update your Ad Hoc Mobile Provision File

In your backend:  

Case n°1: You want to add new devices to test your ad hoc version of your app  
Follow steps 6.1, 6.2 and 6.3, then go to 6.7.

Case n°2: You do not want to add new test devices  
Skip steps 6.1 to 6.6 and go directly to 6.7.

In the menu "Provisioning Profiles" https://developer.apple.com/account/ios/profile/, select your existing Ad Hoc provision file. It should have the same name as your Apollo Apps project followed by "ad hoc" (in the example, it is debsapp ad hoc) and click on Edit.  
The existing provision file can be Invalid (like in the example), or Expired.

Then, select the right App ID (it should already be the right one), the right distribution certificate, and the devices where you will install your ad hoc version.  

Click on Generate, and download the new ad hoc mobile provision file.

6.7: Delete the existing mobile provision file ad hoc in the backend and upload the new one, then go to the next step.

7. Do I need to rebuild the app?

Updating the certificates do not require a new submission to the store.
You may or may not need to re-build the app, for testing purposes.

Case n° 1: You have not added any new test devices
You are done with the process, no need to click on Build my application.  

Case n°2: You have added new test devices at step 6
Click on Build my application in order to be able to install the app on the new devices.
When you are done, you can click on Modify to unlock the backend.



 

Did this answer your question?