iOS build fails on xcode-archive, codesign issue

Bitrise Build Issue Report template

Description of the issue

Hello. My bitrise build for iOS stopped working for some reason. It complains about not finding codesign groups. I haven’t changed anything related to a code signing for some time so it’s really weird.

Resolving CodeSignGroups...

Resolving CodeSignGroups...

Filtering CodeSignInfo groups for target capabilities

Filtering CodeSignInfo groups for export method

App was signed with NON Xcode managed profile when archiving,

only NOT Xcode managed profiles are allowed to sign when exporting the archive.

Removing Xcode managed CodeSignInfo groups

Failed to find Codesign Groups

generated export options content:

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "">

<plist version="1.0">





</plist> <nil>


Where did the issue happen?

Bitrise with Xcode 13.1.x, on macOS 11.4 (Big Sur) stack.

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



  • 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? : first failed build was on October 26th

Local reproduction

Can it be reproduced on your own Mac/PC by following our local debug guide? No, seems to work fine locally. But on my machine I have development provisioning profiles installed so it might be the reason why it works.

Local reproduction: Linux / Android (docker based) stack builds

Can it be reproduced by running the build locally, after doing a new git clone of the repository into the /tmp directory and running the build from there with the Bitrise CLI ( Bitrise CLI )? If no, can it be reproduced with Docker (using the same docker images / environment we use on Related guide: Redirecting… .

Build log

Hello, did you solve your issue? Is so, can you tell us how?
We have the problem and did not find working solution yet

Typically with an issue like this, we need to be able to view the log and the settings. In order to do this, we need support access enabled. Opening a ticket with support is the best course of action.

I will take a guess here. Please check what version of Xcode Archive you are using. This step was recently updated and a new version, version 4, was released. This new version changed the name of the step input for the export method and set the default to “development”. If this step was updated in your workflow, please check the value for “Distribution method” to see if it is correct.

1 Like

Hello, I had the same problem, but I solved it by downgrading the version of the xcode-archive step.
In my case, I downgraded from version 4.0.2 to 3.3.2.

1 Like

Thank you! It was exactly as you said, I had to add a distribution method to this step inputs. Thank you very much!

@_ymimura @nminary so you just have to check if your workflow uses xcode-archive v4. If yes just add distribution_method inside its inputs.

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