Xcode doesn't search all keychains when checking code signing identity

Originator:jeremy.knope
Number:rdar://7006473 Date Originated:25-Jun-2009 11:20 AM
Status:open Resolved:
Product:Developer Tools Product Version:3.2 & 3.1.3
Classification:Other Bug Reproducible:Always
 
25-Jun-2009 11:20 AM Jeremy Knope:
Summary:
Xcode no longer searches the user's keychains when checking the code signing identities set in the build settings.  In previous version of Xcode (3.1.1 and earlier I believe) the listed code signing identities would be from all available keychains.  The codesign utility still searches keychains like it says it should, but Xcode bails before trying in it's dependency checking step, only scanning the default keychain now.

Steps to Reproduce:
1. Store a code signing certificate in a non-default keychain
2. Set a target to have code signing identity of that certificate's name
3. Hit build

Expected Results:
Xcode should successfully build & codesign the target's product with the named certificate

Actual Results:
Xcode bails immediately after hitting build on it's 'checking dependencies' step saying it can not find the code signing identity in the user's keychains.

Notes:
This problem was introduced in one of the iPhone SDKs first, but now is a problem in Xcode 3.2 on 10.6 and Xcode 3.1.3 on 10.5.

Comments

Doing a project clean seems to reset the search to cover all it should cover. Not an optimal solution if you have a big project, but better than none.

By vance9876 at 2009-07-27 14:38:48.694885 (reply...)

Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!