You are here:   Table of contents / Ios Submission Process / Updates Of The Ios App

iOS - Build fail troubleshooting guide

If you selected the Solo process (you are in charge of updating your app to the App Store) to update an app created outside GoodBarber already published on the App Store, please read below, if your iOS app build fails.

If GoodBarber is taking care of your iOS app updates/publication to the App Store, contact our Support  in case of an iOS build fail.

When an iOS build fails: 
1 - In your backend, go to Sales channels > iOS App > Certificates  
2 - Open http://developer.apple.com  > Certificates, Identifiers & Profiles > Certificates in another window 
3 - Verify there is one Distribution Certificate with the same date in the Apple Developer account and in the backend


1

Can't find the distribution certificate used in the backend

The Distribution Certificate used in the backend should ALWAYS be visible in http://developer.apple.com  > Certificates, Identifiers & Profiles > Certificates 
This is true both in Apple Developer accounts ($99/year) and Apple Enterprise Developer accounts ($299/year).

When a Distribution Certificate is revoked in the Apple Developer account, it may still appear as valid in the backend.
The backend only registers the creation and expiration date of a certificate to be able to tell you when it's expired.
The backend is not connected with your Apple Developer account. 

If you can't find the Distribution Certificate used in the backend:
1 - Verify that you are logged into the right Apple Developer account/in the right Team.
(If you were in the wrong account or team, log into the right one and check again!)
2 - Renew the iOS certificates (or ask GoodBarber to do it for you )

picture

2

The dates of the mobile provisions don't match with the distribution certificate

In a regular Apple Developer account ($99/year),  the Distribution Certificate and Mobile Provision files are valid for 1 year. 
Therefore, they should have the same expiration date (+ or - 1 day). 

In an Apple Enterprise account ($299/year), the distribution certificate is valid for 3 years and the Mobile Provision files are valid for 1 year. 
Therefore, the dates won't necessarily match.
 

picture

If the expiration dates don't match: 

1 - Go to http://developer.apple.com  > Certificates, Identifiers & Profiles > Provisioning Profiles
2 - Select the Mobile Provision file of your app and click on Edit 
3 - Choose the Distribution Certificate used in the backend (with the same expiration date)
4 - Generate the new Mobile Provision file and download it.
5 - Delete the old Mobile Provision file from the backend and upload the new one.
6 - Repeat the operation with the Ad Hoc Mobile Provision file. 

Warning
If the app is being distributed internally (using an Apple Enterprise account - $299/year), continue the iOS submission process until the end and send the new version of the app to your users. 

picture

3

Two distribution certificates have the same date in the developer account

You should NEVER create 2 Distribution Certificates on the same day! 
In this case, even if the date of the Distribution Certificate and the Mobile Provision files match, the build may still fail. 

When 2 Distribution Certificates are created on the same day:
=> they have the same date.
=> it is impossible to know which one you uploaded in the backend. 
=> it is impossible to know which one to choose when creating the Mobile Provision files 

If 2 Distribution Certificates have the same date: 
1 - Revoke both of the Distribution Certificates with the same date 
2 - Renew the iOS certificates  (or ask GoodBarber to do it for you )

Warning:
If your app is for Internal Distribution (using an Apple Enterprise account - $299/year), the current version of the app will stop working from the moment you revoke the certificate in use. 

Continue the iOS submission process until the end and send the new version of the app to your users. 

picture

4

Too many boxes checked in the App ID

If all the above is correct, maybe the problem is the App ID.

1- Go to http://developer.apple.com   > Certificates, Identifiers & Profiles > App IDs
2 - If there are other boxes checked except the 2 default ones, Push Notifications, uncheck them 
3 - Go to the menu Provisioning Profiles
4 - Select the Mobile Provision file of your app and click on Edit 
5 - Make sure you have the right Distribution Certificate and App ID 
6 - Generate the new Mobile Provision file and download it.
7 - Delete the old Mobile Provision file from the backend and upload the new one.
8 - Repeat the operation with the Ad Hoc Mobile Provision file. 

Warning

If the app is being distributed internally (using an Apple Enterprise account - $299/year), continue the iOS submission process until the end and send the new version of the app to your users. 

picture

5

Everything looks Okay, but the build fails

If you carefully verified all the points mentioned above, and the build keeps failing: 

1 - Go to http://developer.apple.com   > Certificates, Identifiers & Profiles
2 - Go to the menu Certificates > take a screenshot showing ALL the Distribution certificates
3 - Go to the menu App IDs> select your App ID > Click on Edit > take a screenshots of ALL the list of services 
4 - Go to the menu Provisioning Profiles> select your Mobile Provision file (app store) > click Edit > take afull page screenshot 
5 - Do the same with the Mobile Provision file ad hoc 

Contact the Support  , explain your problem and provide all the screenshots listed above (you can send them all at once in a .zip file).