Whether you received an e-mail with automatic build log failure, follow the instructions below to solve the issue. There are several reasons why you cannot receive a valid binary you requested through Instant Build submission. In most cases, the reason why your build failed is written at the bottom of log page that SeattleCloud provides in email.
Almost all of you might notice a message at the beginning of the log file about private key failing to install. This is not the reason why your build failed(!!!not in all cases). As I mentioned above, you have to read the reason at the bottom of the file.
Let's analyse several cases.
1. Private Key file not found! PRIVATE_KEY_DOWNLOAD_AND_INSTALL FAILED
You have to consider this warning in case you have generated a Distribution Certificate with your personal CSR file and have forgotten to upload the .p12 key during the submission process. Follow the TUTORIAL to export the right .p12 certificate. Upload the .12 certificate along with Distribution and Provisioning Certificates.
Also, you can consider to create a Distribution Certificate signed with a CSR file provided by SeattleCloud. You can download it from HERE .
In this situation, the app builder machine failed to import the Private Key because the password provided on the website does not match with the one set in Keychain application.
On the website the password was introduced differently.
3. No matching provisioning profiles found. No provisioning profiles containing one of the following signing identities was found
Follow the instructions to solve the issue in case you have used SeattleCloud CSR file and the build failed.
Usually it happens when users have under their Apple Developer accounts several Distribution Certificates created on different days.
Let's consider that an user has previously uploaded to the website a Distribution Certificate created on Day X,2015. Then, he created another Distribution Certificate on Day Y,2016 and signed the Provisioning Profile with it. The user uploaded to the website the PP signed with the latest Distribution(from Day Y,2016) but did not upload the Distribution Certificate itself. As a result, the system will find in In-App Resources a DC created on Day X,2015 and a Provisioning Profile signed with DC from Day Y,2016. In this situation, the certificates won't match. You have to upload to the website the latest Distribution Certificate you used to sign the Provisioning Profile Certificate.
These are three main reasons why your build fails. If you get a different build fail, please consider to contact us.
How to read failed build logs?
Whether you received an e-mail with automatic build log failure, follow the instructions below to solve the issue. There are several reasons why you cannot receive a valid binary you requested through Instant Build submission. In most cases, the reason why your build failed is written at the bottom of log page that SeattleCloud provides in email.
Almost all of you might notice a message at the beginning of the log file about private key failing to install. This is not the reason why your build failed(!!!not in all cases). As I mentioned above, you have to read the reason at the bottom of the file.
Let's analyse several cases.
1. Private Key file not found! PRIVATE_KEY_DOWNLOAD_AND_INSTALL FAILED
You have to consider this warning in case you have generated a Distribution Certificate with your personal CSR file and have forgotten to upload the .p12 key during the submission process. Follow the TUTORIAL to export the right .p12 certificate. Upload the .12 certificate along with Distribution and Provisioning Certificates.
Also, you can consider to create a Distribution Certificate signed with a CSR file provided by SeattleCloud. You can download it from HERE .
2. Private Key import failed. PRIVATE_KEY_DOWNLOAD_AND_INSTALL_FAILED
In this situation, the app builder machine failed to import the Private Key because the password provided on the website does not match with the one set in Keychain application.
On the website the password was introduced differently.
3. No matching provisioning profiles found. No provisioning profiles containing one of the following signing identities was found
Follow the instructions to solve the issue in case you have used SeattleCloud CSR file and the build failed.
Usually it happens when users have under their Apple Developer accounts several Distribution Certificates created on different days.
Let's consider that an user has previously uploaded to the website a Distribution Certificate created on Day X,2015. Then, he created another Distribution Certificate on Day Y,2016 and signed the Provisioning Profile with it. The user uploaded to the website the PP signed with the latest Distribution(from Day Y,2016) but did not upload the Distribution Certificate itself. As a result, the system will find in In-App Resources a DC created on Day X,2015 and a Provisioning Profile signed with DC from Day Y,2016. In this situation, the certificates won't match. You have to upload to the website the latest Distribution Certificate you used to sign the Provisioning Profile Certificate.
These are three main reasons why your build fails. If you get a different build fail, please consider to contact us.
CONTACT US