On Mar 29, 2012, at 23:41 , Martin Hewitson wrote:
> According to Keychain Access, all my certificates have a private key. At
> least I can expand the certificate and see the private key. Do I need to do
> something to tell Xcode about these? I followed the usual steps of installing
> certifica
They are all under Login->My Certificates. And I can see them under Login->Keys
as well.
Perhaps I'll try deleting all my certificates and getting new ones from the
Certificate Utility.
Martin
On Mar 30, 2012, at 08:52 AM, Roland King wrote:
> is that key (or those keys) in your 'login->keys
is that key (or those keys) in your 'login->keys' in Keychain Manager? I think
both the public and private keys need to be there. Not sure that just being
able to expand the certificate and see the key is enough.
On Mar 30, 2012, at 2:41 PM, Martin Hewitson wrote:
> According to Keychain Access
According to Keychain Access, all my certificates have a private key. At least
I can expand the certificate and see the private key. Do I need to do something
to tell Xcode about these? I followed the usual steps of installing
certificates, and as I said, this computer was able to submit app upd
But is the corresponding private key in your keychain? Xcode isn't complaining
about your certificates, it's complaining about your key.
(Sent from my iPad.)
--
Conrad Shultz
On Mar 28, 2012, at 23:32, Martin Hewitson wrote:
> "" is a valid identity. However, the private key for the asso
Dear list,
I'm having trouble submitting an app update to the Mac App Store. I'm not sure
if this is an Xcode issue or something else, so I thought I'd try here first.
I've updated this app many times using the same computer. This time I get the
error in the organiser on the page entitled "Choo
