Code signing is required for product type 'App

问题:

I am facing the below issue and am unable to build the application.

XXX has conflicting provisioning settings. XXX is automatically provisioned, but provisioning profile WildCard has been manually specified. Set the provisioning profile value to \"Automatic\" in the build settings editor, or switch to manual provisioning in the target editor. Code signing is required for product type \'Application\' in SDK \'iOS 10.0\'

I am also unable to choose a particular profile.

How to resolve this issue?

回答1:

Holy molly, I had to do all this in order for it to work. A picture is worth a thousand words.

• If you get this error while archiving then continue reading.

  

• Go to your app and click on the general tab. Under the signing section, uncheck \"Automatically manage signing\". As soon as you do that you will get a status of red error as shown below.

  

• Now here\'s the tricky part. You need to uncheck \"Automatically manage Signing\" in both the targets under your project. This step is very important.

  

• Now go under \"build settings\" tab of each of those targets and set \"iOS Developer\" under code signing identity. Do the same steps for your \"PROJECT\".

  

• Now do Xcode → Product → Clean. Close your project in Xcode and reopen it again.

• After this go to the general tab of each of your targets and check \"Automatically manage signing\" and under team drop down select your developer account

  

• Do an archive of your project again and everything should work.

Really, Apple? Was this supposed to make our lives easier?

回答2:

Great, now we can choose the profile for Debug and Release separately in the general tab itself as illustrated in the image below.

Also when you click on Automatically manage signing it does all process that are created by Fix issue in previous Xcode versions.

回答3:

Disabling automatic and then re-enabling has solved this for me in Xcode 8 GM seed. This can be done in the project settings, info tab for each target that needs to be signed.

回答4:

I hate to say it. I just quit Xcode and opened it again. Simple and effective :)

回答5:

For resovle this issue:

1. Go to Xcode/Preferences/Accounts
2. Click on your apple id account;
3. Click - \"View Details\" (is open a new window with \"signing identities\" and \"provisioning profiles\";
4. Delete all certificates from \"Provisioning profiles\", empty trash;
5. Delete your Apple-ID account;
6. Log in again with your apple id and build app!

Good luck!

回答6:

This is what I would call a classically Apple Xcode UX design bug.

The error said there is a bunch of stuff YOU DID WRONG LOCALLY.

The error actually meant \"we have a new agreement you did not accept online\".

After checking and unchecking the Automatic Signing button I got this agreement error to display:

Signing into the developer portal I was able to see a banner for the agreement update notice:

. Restarting Xcode 8 then cleared that error and only forced me to reselect the certificate I already had on my machine and tied to the project.

This could have been handled in a less confusing implementation, but this is how I fixed it. I am putting it here because it\'s way different than the steps everyone else gave.

Oh and yeah, having the pre-latest iOS 10 device and latest Xcode (I was on 7.3.1 or something) also threw errors until I updated.

回答7:

This is how it worked for me:

1. Kill Xcode and launch again
2. Open project again
3. Clean Project
4. Go to project settings > general > uncheck \'automatically managed profiles\' and than \'check\' again it will prompt for enable.
5. Now try archiving the source code

P.S Killing Xcode and launch again is the best thing to do if facing any random issue

回答8:

I fixed it doing this:

Set your team for all the targets of your project. Including the extensions. And left the automatic signing management.

回答9:

Steps:

1. Under General → Signing
2. Uncheck: Automatically manage signing
3. Select Import Provisioning

回答10:

I only needed to uncheck \'Automatically manage signing\', check it again, and rebuild.

回答11:

Click on Add Account if not signed in.

Then after select your team profile and check Automatically manage signing and leave everything else as is in Xcode. It will perform the remaining stuff by itself.

回答12:

The Untick-tick (check-uncheck) \"Automatically manage signing\".) of Xcode checkboxes don\'t work for me (as many suggested on the top).

It happens with frameworks linked in your project.

Solution:

• Find your framework or any other target that required signing.
• Go to Build settings
• Search Signing Identity
• Set Don\'t code sign manually.

回答13:

I ran into this type error by updating the Xcode version to 8.0, and under the Code signing is required for product type \'Application\' in SDK \'iOS 10.0\'

There is a warning:

isn\'t code signed but requires entitlements. It is not possible to add entitlements to a binary without signing it.

My solution is go to the TARGET → General → Signing -> click the Enable signing... button, and I solved the issue.

回答14:

If you are finding the following screen and facing the problem of code signing required, then one of the following solutions may help you.

Solution 1. As said before, sign in with an Apple ID. Then you will get options like this, if you enter correct bundle identifier. Then select the appropriate profile from the list.

Solution 2. If you don\'t want to sign in with your Apple ID, then change a small flag in project.pbxproj file. Find the following text in the project file.

/* Begin PBXProject section */

Change flag ProvisioningStyle = Automatic; to ProvisioningStyle = Manual; Refer to the following image. After changing the flag, you will see the options to select appropriate profile from the list.

回答15:

In unit test target

Xcode 7:

• Must have provisioning profiles set (the same as in app target)
• Must have \"don\'t sign\" under certificates

Xcode 8:

• Must have \'None\' set for provisioning profiles
• Must have certificates set (the same as in app target)
• (Must also have \'None\' set for deprecated provisioning profiles)

回答16:

All answers looks fine but i found still issue so i changed settings in Build like this in XCode 9.0 - Sharing it so it could help someone.

回答17:

Firstly in general tab -> signing section -> select a development team, manage signings

Similarly if you are working with multiple pod files select each pod target separately and go to general tab -> signing section -> select a development team, manage signings

repeat the same process for all pods in your project

Clean -> Build the project.

This worked for me

回答18:

Even when installing the Watch OS application extension, the same error occured in Xcode 8.1:

After updating the Provisioning Profile to Empty in Project of Build Settings, everything work fine.

&& Code Signing Identity to iOS Developer in every targets Build Settings.

回答19:

I upgraded to Xcode 8, and iOS 10, but I had the problem.

I fixed it by going to project general tab, signing section.

Click \"Enable signing.....\"

That is it.

回答20:

If you get this error while compiling in Microsoft Mobile Center

❌ Code signing is required for product type \'Application\' in SDK \'iOS 10.3\'

** ARCHIVE FAILED **

be aware that Mobile center doesn\'t yet support automatic signing with certificates of type app-store, ad-hoc and enterprise. Automatic signing only works with development certificates.

There are two things you can do to work around that limitation:

1. Use a development certificate. You\'ll have to create a new one in the developer.apple.com portal, download it to your machine, export it to a .p12 file using keychain, then finally provide it to Mobile Center. You know the drill.

2. Disable automatic signing. You will find that setting in Xcode in your project targets. Once disabled, a little \"i\" button will be displayed next to the \"Xcode managed profile\" label. Click that button, some info about the profile will be displayed. On the top left corner of that window, a \"PROV\" icon is displayed. That is the provisioning profile that you should provide to Mobile Center. Drag and drop the icon into the corresponding field in Mobile Center.

.

回答21:

in Build Setting change in Signing

Clean and Archive your code , Hope it will help you .

回答22:

1.1: If you are using p12 and a provision file, but not using AppID to log in, do not Select Automatically manage signing.

Which means you don\'t need to set your team. Just select your provision file and the machine code signing identity in Build Settings, like this Build Settings. Make sure the parameters are set as well.

And then go back to General. You will see General set, and that\'s OK.

1. If 1 does not work, try as other answers said, clean your project, delete the derived data folder, quit Xcode, and open again.

回答23:

Just download your provisioning profile again from your developer account. And sign out all developer accounts from Xcode → Preferences → Accounts → *Select Account showing at left and press -(subtract sign)

After deleting all accounts, press the + sign (add) button and sign in with all developer accounts.

It will work like a charm...

回答24:

It is because you have not choosen a team when you created the project.

I am such fixed. And I choose it in build settings, but invalid. I must create a new project.

\"I choose it in build settings, but invalid. I must create a new project.\" is wrong.

It is invalid because I have not chosen it in extension. You must choose a profile at your project\'s all extension, and there is no need to create a new.

[2

回答25:

I did everything and didn\'t worked. I uninstalled Xcode 10 and installed Xcode 9.4 then it worked out of the box !

回答26:

If you still have problem then please try this.

Build Settings -> User Defined -> Provisioning profile (Remove this.)

It will solved my issue.

Thanks

回答27:

After applying all the solutions above, The same issue I was getting. i.e

So I solved this by removing the provision profile in build sending. Please find the images which will make you more clear