Home > Back-end >  Product > Archive error in Xcode related to Signing & Capabilities
Product > Archive error in Xcode related to Signing & Capabilities

Time:12-04

I have an Xcode project that I want to deploy to App Store.

When I run Product >Archive I receive an "Archive failed" error in the Signing & Capabilities section. (Please see the screenshots)

I tried both "Automatically Manage Signing" checked and unchecked. When "Automatically Manage Signing" is unchecked, I receive 2 errors:

"Failed to create provisioning profile. There are no devices registered in your account on the developer website..." and "No profiles for 'net.myprojectname' were found. XCode could not find any IOS development provisioning profiles matching 'net.myprojectname'

When "Automatically Manage Signing" is checked, I receive those same 2 errors even before I run Product>Archive.

I do have a provisioning profile that appears to be visible to Xcode when the Automatically Manage Signing is unchecked.

When I try to just build the project and run it on the simulator, it works fine. Again, all I want is to deploy the project to the App Store.

Do I really need a registered iPhone in order to do so? (I don't have one) Or is there another way to solve it?

Thank you in advance for any help. Auto signing option Non-auto signing

I tried Automatically Manage Signing checked and unchecked. I have created (and recreated) provisioning profile that matches my project name. I have tried running regular build beforehand. None of these actions solved the problem.

CodePudding user response:

Be sure you did those steps first:

  1. Register that net.myprojectname identifier in the Developer section Certificates, Identifiers & Profiles.
  2. Have an app created using that identifier in the App Store Connect.

If you did those the automatic signing management should work for you with no issue. Also registering a device is pretty straight forward (if you own one, obviously), just run the app on a device and it gets registered for you.

CodePudding user response:

I found the solution: my provisioning profile was for release, but Xcode (for reasons unknown to me) was trying to use a (non-existent) development provisioning profile. Once I tweaked Xcode to use the release profile, things started to work and I was able to build the archive.

  • Related