Xcode continues to request a password to use the System Keychain

I run Xcode 4.3.2 under Lion 10.7.3, but every time I install the iPhone application on the device, it asks me about the username and password of the administrator.

I did everything suggested here and even reinstalled Xcode:

stack overflow

But so far nothing has happened.

Here is an image of a window that appears all the time:

Xcode 4.3.2 keeps asking for an admin user name and password

Any other suggestions to solve this?

+65
ios objective-c xcode
Apr 09 '12 at 3:25
source share
5 answers

The problem was that my Keychain developer certificate was under the " System " in the left pane, which is always locked, requiring my password to be unlocked!

Then I moved the developer certificate to " login ", which is always unlocked, and now everything works fine. The xCode annoyance requesting the password is gone.

Please see this image for more details: enter image description here

+138
Apr 14 2018-12-12T00:
source share
β€” -
  • Go to " Keychain Access "
  • Double-click the secret key according to the certificate to sign the application code.
  • Add "Xcode" to " Always allow the following applications: " in the " Access Control " section.
+37
Oct 22 '12 at 7:16
source share

Here is how I fixed it on Xcode 7.2 (also works in version 7.3):

1) Open KeyChain. 2) Select System, Choose Certificates category. 3) Select developer certificate and double click the private key. 4) Check Access Control and tick on 'Allow all item to access this'. 5) Restart Xcode and run the app on device. 
+14
Feb 25 '16 at 5:23
source share

I did this to solve the problem above:

  • Go to Keychain Access

  • Choose System β†’ Your Certificate β†’ Right-click β€œGet Information”

  • A window with certificate information will open β†’ Select the "Trust" section

  • From the drop-down list, select "Always trust"

enter image description here

+9
02 Sep '14 at 8:09
source share

In my case, the required private key certificate was saved in the chain System , Certificates . To fix the problem, I exported the certificate (including the private key) and moved it to the login chain, Certificates .

0
Nov 10 '17 at 13:08
source share



All Articles