Code signing is required for product type 'Application' in SDK 'iOS 10.0' - StickerPackExtension requires a development team error

Question

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?

Solution 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?

Solution 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.

Solution 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.

Solution 4

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

Solution 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!

View more solutions

Comments

[jjxtra]

@aryaxt yea I hope my hours of pain can help other people not have hours of pain

[Aaron Krauss]

If I'm being 100% - I don't really understand why this worked. But it did, and the pictures made a big difference. Thank you, wise wanderer.

[Jeremiah]

I only had to uncheck and recheck the "Automatically manage signing". It then made me choose my team and had a popup confirming it was reseting some settings. Then it worked!

[Jack]

Don't forget to 'Close your project in Xcode and reopen it again'. This is important, at least to me :(

[Pablo Ezequiel Leone]

Don't scare if you don't have multiple targets. I didn't have any and the process worked like a charm. I wouldn't be able to realise of all this process, you are a genius!

[Kristian MT]

I had problems with certificate. Revoke didn't help, but after the clean and restart the certificate showed up. Nice!

[andrewoodleyjr]

Your solution really helped. I was a bit confused with "uncheck Automatically manage Signing in both the targets." This could be due to Xcode 8.0 and the pictures not lining up. Thanks for taking the time to provide the solution +1

[Yigit Yuksel]

I've tried this, but still i cant upload my project with deployment provision profile.

[thadk]

I was able to double click the project above the error in the left pane and the correct window appeared.

[hoi]

This is a simple and great answer!!

[Rafael Nobre]

It makes all issues that 'Fix issue' used to create available automatically :(

[Amos]

Thank you...This worked for me and afterwords I just had to choose my team developer account.

[Andrey Butov]

You probably saved me hours of work. You should send an invoice to Apple for nonsense like this.

[Yar]

in my case Automatically manage Signing wasn't actually checked by default and checking it solved my problem!

[Roger Binns]

Please can you clarify precisely what "Go to your app and click on the general tab" is. My app features in numerous locations on the screen, there are boatloads of menus, tabs etc. I just can't find what you have in your second screenshot or the mysterious "project editor" mentioned in the error message.

[GameSalutes]

I actually got a warning when submitting app saying "potential loss of keychain access" as signing identity didn't match my previous version. So I came across this post, and I just turned off the auto provisioning following your steps and pointed to my known identities as I don't trust the automation and prefer the "old ways" as it selected some new identity that it must have autogenerated and does not even exist on my account! Thanks for the tips! It seems Apple consistently breaks something with the publishing process each version of XCode.

[Mike Gledhill]

"Really apple? This was suppose to make our lives easier?" Unbelievable, isn't it ? We're almost in 2017, and Xcode still behaves like a spoilt child from the 1980s. All that money, and they refuse to employ an Xcode developer with skills in actually making this stuff user-friendly. It's a disgrace.

[Mike Gledhill]

Good tip... but frustrating that Xcode's upto v8.1, and we're still having to do dodgy workarounds like this. Are they ever going to make it user-friendly ?

[Jason Farnsworth]

@Jeremiah is spot on. Unchecking, rechecking, and restarting Xcode worked. Face. Palm.

[Darkglow]

We had this issue in combination with a apple watch and the apple watch extension. Worked here as well with Xcode 8.2.1. It looks like ProvisioningStyle = Automatic; wasn't set at all this changed after i clicked through your instructions. Further the watchkitExtension Project had no Code Signing Identity for the entry "Any wachtOS SDK" there i hat to put iOS Developer in, no matter if on a Release or Debung Configuration

[Supriya Kalghatgi]

I tried doing this ProvisioningStyle = Manual;. Unfortunately dd'nt help

[buildsucceeded]

This did it for me! Glad I searched before spending hours trying to fix.

[Sravan]

@SupriyaKalghatgi, Which XCode version you are using ?

[Dansp]

All technique in IT. Quick and open again. Thanks! haha

[lukecampbell]

I had to quit XCode as well. Quitting XCode is quickly becoming my standard debugging technique.

[prankin]

In addition to these steps I had to go to Product -> Scheme -> new scheme to get it to work. Thanks

[wottle]

Option 2 worked for me, since I'm not able to sign into the dev account on Xcode.

[lee]

Unchecked and checked Automatically manage signing also cannot fix the bug. I follow up your steps, then it's worked. Thanks.

[Programmer Hugo]

Best answer , normally I have to spend lots of time solving building issues

[Ka Mok]

The only solution that worked for me. Why is the suggested answer restarting?

[Stevey]

Also happened when my membership expired.

[Vasanth]

It's August 2017 with Xcode 8.3.3 this solution still works.

[Naishta]

This is cool stuff ! Works for the Appium Server automation tests. Just got a long pending Automation Server issue fixed at work !

[Ade]

I will never understand Apple Code signing. After years of doing this. smh, thank you.

[Raghav]

As a developer I feel awkward finding out that this solution actually worked for me. Bravo!

[neoscribe]

This is the closest answer. I had to use the menu File/Close Project, then Open Recently... this worked for me.

[John Halsey]

Yes! This works, although I did have to do a headstand for 5 seconds after I closed Xcode, and opening it up again.

[TheTravloper]

i deleted them. But are you sure that this won't cause any problem

[kalpa]

For me I did not face any problem. But for safe side just keep an copy of it.

[Andor Németh]

Umm and what should I import? This makes no sense to me.

[pyfyc]

I had the same error in the Signing Status section. I fixed it by removing PROVISIONING_PROFILE codes same you. After that the error in Signing section was gone. But I still cannot build my project with the same error: "Code signing is required ..."

[kalpa]

@pyfyc after deleting provisioning profile clean the project and try again.

[pyfyc]

@kalpa I have tried that many times but it did not solve the problem. Maybe my case is a bit specific, I also described it here: stackoverflow.com/q/65713315/4428219. You can take a look if you want. In the meantime I will try other suggestions from this thread. Thanks.

[pyfyc]

Thank you! Your answer helped me to solve my issue. Even there is no such option in my interface (xcode 12.3) but it started working when I was trying out your answer. I posted my solution here: stackoverflow.com/a/65739207/4428219

[xjsXjtu]

Unbelievable, but that's true.