Apple Worldwide Developer Relations Certification Authority

Bitrise Build Issue Report template

Description of the issue

We updated our provisioning profiles and certificate earlier this week because they expired and since then no build is succeeding. They are all passing locally though.
The error seems to be different on our existing bitrise app and on a fresh new app that we created for testing.

However, google searches on both errors give the same solution:
“In keychain if I choose always trust , Xcode archives failed. When I changed to system defaults , Xcode archives successfully.”

Unfortunately, we couldn’t find any way to go and change those settings on Bitrise because we don’t have direct access to the keychain.


Where did the issue happen?

Which build Step causes the issue and which version of the step?

steps-certificate-and-profile-installer 1.10.3
steps-xcode-archive 2.8.6


  • Does a “Rebuild” help? (You can trigger a rebuild from the Build’s page, by clicking the “Rebuild” button in the top right corner of a finished build) : NO
  • Does a rebuild without caches help? (You can remove the Cache:Pull and Cache:Push steps temporarily to not to use the cache, or you can delete all the caches on the Settings tab of the app. : NO
  • Does the issue happen sporadically, or every time? : Every time
  • Does upgrading the build Step to the latest version help? : NO
  • When did the issue start? : After updating provisioning profiles + certificates

Local reproduction

Can it be reproduced on your own Mac/PC by following our local debug guide? Please follow at least the first section (“Testing with a full clean git clone”) to make sure to test the state of the code what will get when it does a git clone in the clean environment! If possible please note which sections you tried.

Local archives on OS X 10.15.4 / Xcode 11.7 are working fine with the new provisioning profiles.

Build log

First log is coming from our original app on Bitrise, it fails very early in the build.

Second log is coming from a fresh new app using the exact same yml and provisioning profiles / certificate. It seems to manage the whole build but fails at the very end still because of code signing issues.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

I apologize for the delayed response. This just reached my queue.

There was a missing intermediary certificate that was causing this problem. The cert has since been added to our stacks, so you shouldn’t be seeing this anymore.