Code Signing Errors Since updating to Xcode 8.3

Solar2D iOS
#1

Hey Folks,

At my wits end here. I have a project that compiled and signed without issue prior to my latest versions Xcode/Sierra upgrade. Regardless of what I try, I get code signing errors and can no longer successfully publish.

I have tried generating new certs, provision files, etc. to no avail. I can’t get any app to successfully publish, I’ve tried “Hello World” and other projects I’ve built in the past. I’ve tried previous certs that worked in the past.

I’ve also tried the current release build and multiple daily builds of Corona.

The project used to publish exactly as is without issue, I even pulled up prior versions to try, but now anything an everything fails.

I have checked the certs in keychain and all have a green check mark, but I get this warning each time:

WARNING: identity ‘AF035E619C44E4EDF429C09FB2558A9B741BC44C’ does not appear to be valid for codesigning.  You should open Keychain Access and verify that your signing identities are valid

and later these errors:

ERROR: build command failed: DEVELOPER_BASE="/Applications/Xcode.app/Contents/Developer"
 

BUILD ERROR: ERROR: code signing failed: sh: line 3: 41813 Trace/BPT trap: 5       “/usr/bin/codesign” --verbose -f -s “AF035E619C44E4EDF429C09FB2558A9B741BC44C” --entitlements “/var/folders/lc/wg_yb73543n_3sgckgxn5h080000gn/T/CLtmpJRgiw2/entitlements.xcent” 

If anyone else has had and fixed this issue, I would be tremendously grateful for any help you can provide. Thanks!

#2

These problems have the be the most annoying people can face. It’s always best to start fresh when hitting them. Make sure to remove all old keys and certs from Keychain Access. Remove them from the developer portal and start clean. Remove any provisioning profiles from ~/Library/MobileDevice/Provisioning Profiles as part of the clean up before starting. 

After you  have your new certs and keys, created, create new profiles and download them (either through Xcode or by downloading them to the above folder.

Then start Corona and see if the problem goes away.  In Keychain Access you may need to open up some of the key and cert categories to make sure you’re getting everything.

Rob

#3

Hmm. I have to take that back. No errors the first time, now I’m seeing them again… Arghh. Keep you posted.

#4

These problems have the be the most annoying people can face. It’s always best to start fresh when hitting them. Make sure to remove all old keys and certs from Keychain Access. Remove them from the developer portal and start clean. Remove any provisioning profiles from ~/Library/MobileDevice/Provisioning Profiles as part of the clean up before starting. 

After you  have your new certs and keys, created, create new profiles and download them (either through Xcode or by downloading them to the above folder.

Then start Corona and see if the problem goes away.  In Keychain Access you may need to open up some of the key and cert categories to make sure you’re getting everything.

Rob

#5

Hmm. I have to take that back. No errors the first time, now I’m seeing them again… Arghh. Keep you posted.