Xcode asking username & password every time I compile to device

26,757

Solution 1

For solution go to Keychain Access, and in the top left navigation, move your Developer certificate from "System" to "Login".

Actually problem is Developer certificate is under "System", and it is locked every-time, so it will require a password to unlock, whereas when certificate is in "Login" section it will resolve that.

Solution 2

In keychain remove your development and distribution certificates from System and place them under Login. It will ask once and you have to select Always allow

That worked for me. Hope it works for you aswel.

Solution 3

In Xcode 7.1, I didn't find Login so I have given access to Xcode and codesign for the certificate key by following steps:

  1. Open Key Chain
  2. Go to Certificate under System
  3. Click on closure, right click on private key and select 'Get Info'
  4. Click on 'Access Control' tab
  5. Add Xcode and coding under 'Always allow access by these applications:'

It solves my problem.

Solution 4

Is the /Developers directory from the old Xcode still on the drive? I just had a user with this issue that was also experiencing build fails with code that other users were able to build successfully. Some of the file associations cause the new Xcode (moved to the /Applications folder) to reference components in the old /Developers folder. Once we removed the folder and emptied the trash, everything worked as expected.

Share:
26,757
edwinjomathew
Author by

edwinjomathew

Updated on July 11, 2021

Comments

  • edwinjomathew
    edwinjomathew almost 3 years

    I use an admin account for the development. But every time I compile to a device Xcode is asking for admin username & password. I googled the issue. But none of the solutions worked. I tried the workarounds from this post, but it didn't work

    Authorize a non-admin developer in Xcode / Mac OS

    I also tried disabling and enabling the DevSecurityTools but it didn't work. I am using Xcode 4.3.1 installed on Mac OSX Lion 10.7.3.

    Is there any way to fix this?