Code Sign Error: Broken security profiles that contain any key signing certificates were not found

Question

I think I have reached the nadir level of iOS . After switching to a new Mac and creating an archive for distribution, I got an error:

Code sign error: unused collateral profiles that contain any of keychain signature certificates were not found

Then I deleted all certificates and keys and provisioning profiles and made a “hard reset” (deleting all keys, certificates and profiles), following Apple's instructions manually, with the same error. Then I did another hard reset, and then Xcode processed it all through Organizer, made another archive - just to see the same error.

I have all the certificates ( WDRCA , Developer ID Cert Authority , iPhone Dev , iPhone Distribution ) shown in Keychain Access, Xcode shows that it sees dev and distribution certificates, as well as provisioning profiles, everything is marked with a green checkmark and a “valid” status .

Signing the code in the application shows the correct option and the distribution is selected.

What's really bothering is that a Google search mistakenly shows one technical note from Apple, which is not very useful, 2 tweets and 3 results in Japanese - and nothing more. I contacted one of the twins, and he said that he corrected it with a tough result, which I did twice.

Any ideas on where to go or what to do next?

Answer 1

After nine hours of pulling my hair, cursing and burying my head in my hands ... All I had to do was create a new project, transfer the files manually, and the error disappeared. Argh.

Refresh . I believe that my own answer is correct, does not mean that these other answers were incorrect - I did not have the opportunity to try any of them.

Answer 2

This is fixed using Organizer → Teams (select your team) → Refresh (in the lower right corner).

Answer 3

After removing all devices/profiles/certificates and adding/creating it still doesn't work here either .... also removing the Xcode prefixes didn't help.

but it seems in the project settings, check the assembly settings in CODE_SIGN_IDENTITIY , in my project the first line was set to the old profile, but it doesn’t appear in the list only if you open the drop-down list after deleting that it worked.

Answer 4

I had this problem. Finally, I realized that the identifier is case sensitive. For example, if your product name is "StackOverflow", it automatically tags an identifier named com.yourcompanyname.StackOverflow. (this, of course, can be changed by going to the goal summary). The problem is that the application identifier is on the developer portal. Make sure that the identifier in the portal matches that in Xcode.

Answer 5

I have the same problem as installing Xcode 4.3 (switching from / Developer to / Applications). I found this post to change the Xcode directory

in the terminal, check which path it is installed to:

/usr/bin/xcode-select -print-path

and then if it is still installed in /Developer , install it in /Applications :

sudo /usr/bin/xcode-select -switch /Applications

which worked for me to be able to upgrade to 4.3.2, but that did not help solve the problem mentioned .... so maybe this will help you.

Answer 6

i met the same problem.

The answer to the problem is simple.

you need to go to your apple develpoer website to apply and download a profile for your application.

after double-clicking the download file, you can see the file in the project organization in xcode.

package identifier name is a type e.g. com.yourname.appname

the xcode device selects the ios device and the target code must select a distribution that is one of the files in the project organization in xcode.

fyi

Answer 7

I encountered the same problem after upgrading to Xcode 4.3.2 and SDK 5.1 . Everything was fine in the previous version of Xcode with the SDK 5.0 . After many hours of hair pulling, I created a new distribution certificate in iOS Provisioning Portal->Provisioning-> Distribution Tab and after downloading and installing it in Xcode (drag-and-drop) it works for archiving after selecting a new certificate in the Code Signing area for mine target.

Answer 8

A few days ago I had the same problem.

The problem is the lack of proper resource allocation profiles; My mistake was that I added the new device to the portal and did not re-download the distribution profile from the developer's site.

Today I had the same problem; while it worked perfectly with the developer profile, I could not archive or create the distribution package.

I had to go to the portal and manually reload my distribution profile because new equipment was added, although I do not actively use it in the developer's profile (I did not check the checkbox to add it to this position)

Hope this helps someone

Answer 9

I went straight to "but, it seems, in the project settings, check the build settings in CODE_SIGN_IDENTITIY, in my project the first line was set to the old profile, but it does not appear in the list only if you open the drop-down list after deleting that it worked. "

And that sounds like a trick.

Answer 10

I fixed it by updating the package identifier in the project settings> target> appName on the "Information" tab.

Answer 11

I had this problem and fixed it by returning my schema to Debug, not Release.

Answer 12

I had the same problem after updating OS / xcode, so it's worth a try. the solution was simple for me, go to the ios support portal. ensure that the application certificate for the application is valid and not expired. download it again and double click on it to install. this should fix the problem.

Answer 13

I had this error while trying to create a release version - there were no problems for debug collections. Baffling, because in the signing section of the assembly settings code I had the same profile.

The solution for me was to create and upload a new distribution provisioning profile, although it is not used from the settings.

Answer 14

I found a solution that was not here, looking at the errors and looking at my raw .app file, I found a solution.

Go to your goal and then "Set up phases" instead of "Build settings."

Ensure that the storyboard is presented in the Compilation Sources section. For some reason, Xcode did not add the storyboard to this area of ​​my file when I copied the storyboard.

PS I had to add another .m that I wanted in the project to this area (the ones I dragged, not created in the project)

Hope this helps

Answer 15

In the Target settings in Sumary, check if the Bundle Identifier is exactly the same as in itunesconnect.com

as an example:

Bundle ID: com.mycompany.myapplication

Answer 16

I fixed mine by analyzing instead and checking for this error. He indicated that my package identifier was not lowercase, as in the provisioning profile.

Answer 17

I really had this problem, but whenever I tried to get into the organizer, it caused the Xcode to crash. To solve this problem, I included my goals and changed everything under the code signing identifier for iPhone Developer. The default target is the profiling profile that I wanted and it worked.

Answer 18

What worked for me was to select "Do not enter code" and then build. This creates an error, but it seems to clear everything that xcode hangs on. Then select the correct training profile and build. For me, this has resolved similar problems in the past.

Answer 19

Corrected. I went to Project-> general-> found the option "no profile profiles." Fix Issue Button. Click on it. Automatically fixed

Answer 20

Cause of error

If you do not have a valid provisioning profile loaded into your Library / MobileDevice / Provisioning Profiles system folder, you may encounter this error.

Decision

Log in to your Apple Developer account from Xcode-> Preferences-> Accounts, and then download a valid provisioning profile.

Go to Target-> General and select the desired command.

Now go to “Project Build Settings” - “Code Signature Identification” and select “ iOS Developer ” and “ Automatic ” in the Provisioning Profiles profiles. Your application will run smoothly.

Answer 21

In the build settings, find

General> Authentication> Package Identifier and Command Parameters. Fill out the Bundle ID and select a team. (this is basically your post). Of course, as written in others, you will need the right developer account or team account. This solution worked for me and resolved the build error.

Answer 22

This is because of the SUDO permission that you specified when adding the platform.

Follow this link Ion code Error sign: There are no remaining preparation profiles