Xcode Archive failed, error: exit status 65

Question & Answer Builds
1

Build fails while creating archive by giving error exit status 65

It seems to be an issue with the wildcard provisioning profile. Builds locally just fine and with a clean clone.
We are not using automatic signing in the Workflow.

Last lines of the Xcode’s build log:
Check dependencies
Code Signing Error: No profiles for ‘***’ were found: Xcode couldn’t find any iOS App Development provisioning profiles matching ***’. Automatic signing is disabled and unable to generate a profile. To enable automatic signing, pass -allowProvisioningUpdates to xcodebuild.

Code Signing Error: Code signing is required for product type ‘App Extension’ in SDK ‘iOS 11.4’

** ARCHIVE FAILED **

The following build commands failed:

Check dependencies
(1 failure)

##Environment:

Where did the issue happen?

Stack: Xcode 9.4.x, on macOS 10.13 (High Sierra)

Which build Step causes the issue and which version of the step?
Xcode-archive@2.4.6

##Reproducibility:

  • 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?
    Our last successful build was November 20th. We rebuilt that commit but it still fails.

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 bitrise.io will get when it does a git clone in the clean environment! If possible please note which sections you tried.
Local build works and so does building the clean clone.

Local reproduction: iOS

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 bitrise.io)? Related guide: Redirecting… .
Failed at a different step in the CLI: Build to Xcode Project

Build log

Please copy paste the build’s bitrise.io URL here (or if the issue happens somewhere else then the full logs), or if you can’t share the url / log here then send the url or full log through a private channel (e.g. email - Contact us ), with a link to the related Discuss issue.
URL sent via email

2

Hi @nieyoub23!

Can you please include a build URL so we can take a look at the issue?

3

Hi @bitce. I sent a URL via email. Sandor replied that the archive is looking for the wrong bundle ID for OneSignal, but we have a wildcard provisioning profile for that and one for our app.

4

Oh I see now, thanks, let’s continue this discussion there in that case :slight_smile:

5

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