Code Signing Issue in Xcode Version 8

Code signing issue in Xcode version 8

I faced this too, and fixed it by:

1- removing all certificates of my account from keychain,

2- removing all provisioning profiles from xcode and then

3- downloading provisioning profiles again via xcode and also

4- adding certificates again to the keychain.

Code signing issue in Xcode version 8

I faced this too, and fixed it by:

1- removing all certificates of my account from keychain,

2- removing all provisioning profiles from xcode and then

3- downloading provisioning profiles again via xcode and also

4- adding certificates again to the keychain.

The code signature version is no longer supported

Notice

This answer is mostly for people using older versions of Xcode. My build farm was for a time stuck at Xcode 12.4 because some Mac minis couldn't be upgraded past Catalina. If you are using a recent Xcode 13+ this is not your issue. Probably cruft of some kind in your project.

If you're still using an Xcode 12 release it is time to let go. The only reason to use 12.4 would be because you're stuck on Catalina and new problems are cropping up that will not be worked around so easily.

codesign --generate-entitlement-der

Apple has changed the codesign signature to include DER encoded entitlements in addition to the plist encoded entitlements. This additional DER encoded entitlements section is required in iOS 15 and becomes the default behavior of codesign in the latest Xcode. To use codesign on an older machines with an older version of Xcode add the --generate-entitlement-der flag to your call to codesign.

If signing through Xcode, you can add this flag to the OTHER_CODE_SIGN_FLAGS setting in the Build Settings tab.

If codesigning at the command-line:

CODESIGN_ALLOCATE=$( xcrun --find codesign_allocate ); export CODESIGN_ALLOCATE
xcrun codesign --generate-entitlement-der ...

The source of this information was the Apple Forum thread and the answer from Matt Eaton in DTS at Apple.

In the Xcode 12.5 Release Notes there is also a reference to the new signature format. However, it seems the information is not entirely correct.

General advice

If you have a non-trivial setup like CocoaPods, you should probably de-integrate and re-integrate and of course do a project clean. These sorts of 'me too' answers really just add noise to the signal and anyone doing this sort of development should have already tried this.

Xcode 8 shows error that provisioning profile doesn't include signing certificate

To fix this,

I just enable the "Automatic manage signing" at project settings general tab, Before enabling that i was afraid that it may have some side effects but once i enable that works for me.

iTunes Connect submission code signing entitlements error Xcode 8

I wasted more than a whole day on this but I finally found the solution!

Somehow in my Build Settings, the "Product Bundle Identifier" was only my apps name instead of the unique Bundle Identifier (e.g. com.YX.AppName).

Click on your project, choose your App, press Build Settings and search for "packaging". You should find it there.

Found this by creating a brand new project and comparing every single setting.

In case this is not what is wrong in your project, these are the things I found on this topic before. Maybe one of these things might help you:

• project > Alt + Clean (Cleans the whole Build Folder)
• restarted xcode (that helped many others!)
• revoked all Provisioning Profiles and let Xcode create new ones (Xcode > Preferences > Accounts > View Details > Create next to iOS Distribution)
• checked that all App ID names where right
  
  
  • for com.AB.CDE the name has to be "com AB CDE"
• restarted PC
• checked that Xcode and macOS were the newest version

Xcode 8 shows error that provisioning profile doesn't include signing certificate

To fix this,

I just enable the "Automatic manage signing" at project settings general tab, Before enabling that i was afraid that it may have some side effects but once i enable that works for me.

---

Related Topics