0

At first I was getting an error that involved my signing identity. After signing out and then signing back in, I'm now getting the following errors. I think it has something to do with the the certificates or provisioning profile.

error: A cryptographic verification failure has occurred. *** error: Couldn't codesign /Users/x/Library/Developer/Xcode/DerivedData/SeedDemo-elhrfqwwnjtcgucmplbbubsbcjcd/Build/Products/Debug-iphoneos/SeedDemo.app/Frameworks/libswiftCore.dylib: codesign failed with exit code 1

Cœur
  • 37,241
  • 25
  • 195
  • 267
PCR
  • 43
  • 1
  • 7
  • 1
    Did you update to macOS Sierra? https://forums.developer.apple.com/thread/48637 – wottle Jun 17 '16 at 13:15
  • I did. Do you have any suggestions for fixing this? – PCR Jun 17 '16 at 21:46
  • 1
    Unfortunately, it seems like there is a code signing problem that is affecting people who upgraded to Sierra. Can you revert back to El Cap? I don't know of any known solutions, but a Radar has been submitted. – wottle Jun 18 '16 at 13:04
  • I gave a bit more information in another post (http://stackoverflow.com/questions/37826242/could-not-code-sign-a-mac-app/37883303#37883303), but it was deleted. I re-answered it and was down-voted, so apparently responding that something is a known bug with no known workarounds is frowned upon. :) – wottle Jun 18 '16 at 13:06

1 Answers1

0

This is a macOS Sierra problem that is affecting many other developers. Your options now are to revert back to El Cap, or to wait and hope for a resolution with the next Sierra / Xcode 8 beta. I wish there was a better answer, but at this time (6/26/2016), those are the only know solutions.

Some developers are reporting this fixed with macOS Sierra Beta 2 and Xcode 8 Beta 2, but I have not yet comfirmed on my spare Mac if this fixes the problem.

Also, some developers have reported that resetting the Keychain fixes is. In the Keychain Access app , go to "Preferences..." and click "Reset My Default Keychain".

wottle
  • 13,095
  • 4
  • 27
  • 68