18

I'm trying to build and archive the application. After compiling, an alert window appears requesting the "codesign wants to sign using key "my account Name" in your keychain" and the buttons Always Allow, Deny and Allow, when i press Always allow or allow, nothing happens, only deny works.

I enabled the "Allow all applications to access this item" in private key info but it didn't worked for me.

I'm using VNC remote Mac (El Capitan) and Xcode 7.2 .I'm not using any third party utilities and i did not install any mouse related apps.

I have tried below links

Having issue with allowing codesign to use my keychain

https://forums.developer.apple.com/thread/25092

https://apple.stackexchange.com/questions/212622/keychain-wont-let-copy-passwords-after-10-11-1-update

I'd like know reason behind this issue and how can i resolve it ?

enter image description here

Community
  • 1
  • 1
iReddy
  • 467
  • 1
  • 5
  • 12
  • Are you trying to do build and archive from command line? Is your key chain(login) unlocked? – Vasanth Feb 24 '16 at 04:28
  • No, I'm archiving through Xcode like Xcode/Product/Archiving and my login key chain is unlocked – iReddy Feb 24 '16 at 16:32
  • I have the same issue, but mine is requesting a password for the key chain. I don't know any password. – random Jun 08 '18 at 10:37

6 Answers6

28

Had the same problem, tried many things and it felt like total voodoo. One of these two eventually solved the problem for me:

  • Got rid of all expired/revoked certificates in my Keychain Access.
  • Locked my login keychain in Keychain Access (it then prompted me for password for unlocking.)

Hope this helps anybody!

gilm
  • 7,690
  • 3
  • 41
  • 41
  • 1
    Thanks, this worked for me. I think all I needed to do was to lock my login keychain, I didn't delete my expired certs. – Chris.B Nov 28 '17 at 15:36
  • 2
    retarded, but true. Even created new login keychain and re-imported certs etc. Seems the system prompt fails when the keychain is presently unlocked. thanks for figuring this out and posting! – codeslapper Dec 27 '17 at 15:48
  • 1
    WOW, this helped! – Klaas Oct 07 '19 at 13:56
19

Enter your mac user password and hit Always Allow.

laxman khanal
  • 998
  • 1
  • 8
  • 18
  • 1
    Entering the mac user password is what did it. For 2 hours I kept entering my developer password. They need to be more clear with that, smh. Thanks for the answer! – Lance Samaria Oct 01 '18 at 03:29
4

Please don't press "Allow" press "Always allow" only

Divesh singh
  • 409
  • 4
  • 12
1

You need to do it on the machine itself, closing all the vnc connections. Mac determines the click originates from the connected devices nor from any remote controlled device.

Code Tree
  • 2,160
  • 4
  • 26
  • 39
1

Restarting Xcode and trying again fixed it for me. :/

Cannoliopsida
  • 3,044
  • 5
  • 36
  • 61
0

I logged in as root (go to your terminal su -). It allowed me to select "Always Allow". This in return enabled me to archive and upload my build to the app store.

mah927
  • 13
  • 3