Re: Signing identity error "-"
Re: Signing identity error "-"
- Subject: Re: Signing identity error "-"
- From: Quincey Morris <email@hidden>
- Date: Wed, 25 Jan 2017 00:00:40 -0800
- Feedback-id: 167118m:167118agrif8a:167118sLAf5NleaL:SMTPCORP
On Jan 24, 2017, at 20:36 , Susan <email@hidden> wrote:
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. I now need to make a change to an app but what used to compile without error is now failing at the codesign step with: Signing Identity: "-" As far as I can see, all of the account profiles are valid with expiry dates in the future. The only 'odd' thing is that some have a 'Download' button in the 'Action' column of the 'Provisioning Profiles' section of the account details - when I select the "Download All Profiles" button, they turn grey but never seem to download or disappear (even after waiting for several hours!). Looking at the 'developer' web page, all of my certificates and provisioning profiles are all active.
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. |
_______________________________________________
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