Error:
error: exportArchive: Provisioning profile “App Name” doesn’t support the Associated Domains capability.
error: exportArchive: Provisioning profile “App Name” doesn’t include the com.apple.developer.associated-domains entitlement.
I am getting a variety of signing issues that I’m not getting with an Xcode Build. This capability is definitely enabled in the entitlement file. I don’t understand why it’s not getting picked up by bitrise. Any assistance would be appreciated
It seems that you tried to create an App Store signed IPA, and you did upload matching signing files, but those are most likely outdated and do not include the listed capabilities (Provisioning profile “App Name” doesn’t support the Associated Domains capability.).
Please do not delete the previous provisioning profiles on bitrise.io, only the app store distribution one which you replace with the new one (but even that isn’t necessary usually).
Please let us know how it goes or if you have any questions!
The capability have to be enabled in both the project (from the logs it seems it is) as well as in the Provisioning Profile, and it seems the profile you uploaded to bitrise.io is probably and older profile and does not include these capabilities.
I believe I did that. I created a new Distribution Profile “ElsewhereQA_Xcode9” and uploaded that to bitrise. I also turned off pull requests for other profiles to try and make sure that the right profile is used. Could it be that they are cached?
Also the associated domains are turned on for both.
Actually, this link seems to be the same you copied the first time - can you please copy paste the new build’s URL? The one which you ran after you uploaded the new Prov Profile.
I had uploaded the profile before starting the build. It’s the same. I was thinking of starting a new build by deleting the old profiles. I just disabled the pull on them for this build.
@SWARM we just released a new Xcode Archive step version (2.3.6) - can you please upgrade to that and run a new build? If that would’t help please copy paste the new build’s url here
Closing as the issue should be solved now with the latest step version - if you’d still have the issue @SWARM please fill out a new #issues:build-issues report and we’ll check it ASAP!