Re: Signing identity error "-"
Re: Signing identity error "-"
- Subject: Re: Signing identity error "-"
- From: Susan Mackay <email@hidden>
- Date: Sun, 05 Feb 2017 17:17:44 +1100
I had to rebuild my iMac a few months ago and I restored from my Time Machine backup.
One of the gotchas is that any private keys that were installed for signing certificates need to be re-installed when you re-create your developer environment. Depending on exactly what happened when you restored from backups, these keys may not have been restored. (They live in your user’s “login” keychain.)
Note that there is nowhere to restore these keys from, except from a backup you’ve made. That means, if they were not restored with your system for some reason, you should be able to retrieve a copy of your old login keychain file from a suitably old backup, putting it back onto your hard disk under a new new. You can then open it in the keychain utility, and export the private keys to a .p12 file, then import them into your current login keychain.
However, this is all irrelevant if your restoration from backup did restore the old keychain file.
Not sure how “irrelevant” it is but the backup was a full restore form my TimeMachine backup. I would hope that this restored everything. What version of Xcode, and what platform (macOS or iOS)? Is your current version of the Xcode the same as the one used before your restored your Mac? It seems that the “AI” Xcode uses to manage provisioning profiles changes from version to version. I’d be inclined to try changing every app and framework target that make up your app to *not* use code signing at all (via the build settings pane for each target). Hopefully, you should be able to build successfully.
I’m using Xcode 8.2.1 (8C1002) which is the latest (according to the app store updates). Of course the Xcode itself is running under MacOS but the app is for iOS.
The version is more recent than the one that was restored. However this problem has existed since the restore when the version was the same.
I’m not sure now to *not* use code signing. In the “Build Settings”, ’Signing' section of the ‘Target’ settings I set the ‘Provisioning Profile’ to ‘Automatic’ and it set the ‘Code Signing Entity’ to “Don’t Code Sign’. However a build still creates the same signing error. Also tried setting this on the ‘Project’ level and the same result.
If there is a better way to do then then can you please let me know. Then, I’d change the main app target to use the appropriate/correct code signing setting in the Info pane of the project (not the Build Settings pane). Then try building and (if that works) archiving your app. Xcode should either do what it needs to do automatically, or it may tell you how to change the settings for the frameworks. This approach lets Xcode do its thing as far as possible, which may be more successful than trying to puzzle out individual build settings.
Thanks for the help (and apologies for not responding sooner)
Susan |
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden