xcodebuild 13.3 Beta 2 gives "does not support provisioning profiles, but provisioning profile has been manually specified" error

My team's app has several dependencies on Swift Packages via Swift Package Manager, and uses manual specification of the provisioning profile when built on CI via xcodebuild.

This has worked fine for many versions of Xcode through 13.2.1, but with Xcode 13.3 Beta 2 we get an error for each package like this:

error: [package name] does not support provisioning profiles. [package name] does not support provisioning profiles, but provisioning profile [profile name] has been manually specified. Set the provisioning profile value to "Automatic" in the build settings editor. (in target '[target name]' from project '[project name]')

(The bracketed parts are different for each package.)

Our xcodebuild command looks like this:

/usr/bin/xcodebuild -sdk iphoneos -configuration Release -workspace [path to workspace] -scheme [scheme name] clean build archive CODE_SIGN_STYLE=Manual CODE_SIGN_IDENTITY=[redacted] PROVISIONING_PROFILE=[redacted] PROVISIONING_PROFILE_SPECIFIER=

(Yes, there is nothing following the last =.)

Web search results for that error message are almost always from a few years ago and have to do with CocoaPods, with the fix being in the Podfile. We're not using CocoaPods but rather Xcode's Swift Package Manager integration.

We need Xcode 13.3 because it fixes a crash on iOS < 13 when back-deploying async/await code.

Anyone else seeing this? Thank you.

Post not yet marked as solved Up vote post of tthomas Down vote post of tthomas
1.3k views
  • This issue has returned in Xcode 14.0.1 and 14.1 Beta 3. I haven't yet tested 14.1 RC. Issue presents exactly the same as described above.

  • Forgot to mention that after my original post, the issue was fixed in the GM of Xcode 13.3, and continued to be fixed through 13.4.1, which is what my team is currently using on CI. We want to move to 14 or 14.1 now, but can't because this issue has returned in those versions.

Add a Comment

Replies

This issue has returned in Xcode 14.0.1 and 14.1 RC. It had been fixed in the GM of 13.3, and remained fixed through 13.4.1. Now it is back, presenting exactly as described above.

Have you found any solutions? I'm seeing this on Xcode 14.1 (14B47b) and can't seem to find any other references to this issue besides your question here.