Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
When trying to build Xamarin.iOS from TFS it is not finding our code signing key - even though I know that the code signing key is in Keychain on the mac where the build agent is running from.
We receive the following error:
ProvisioningProfile: AppName Dist Provision
SigningKey: iPhone Distribution: XXXXXX
/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/iOS/Xamarin.iOS.Common.targets: error : iOS code signing key 'iPhone Distribution: XXXXXX' not found in keychain.
Task "DetectSigningIdentity" execution -- FAILED
Keychains are per user, are you sure you're running the build agent with the user that has the code signing keys?
Not sure how to check this - I am logged in as the user that added the signing keys to the keychain?
That is the user I start the agent from.
There is only one user on the mac - and that is the user I used to run the agent as well as add all the certificates, keys and provisioning profiles.
It finds the profile- however, it does not find the appropriate key which I know is there.
I think I got past the first issue (had to move all my certificates and signing identities to the system keychain and give them trust access.
However now I get this:
The specified iOS provisioning profile 'XXXXX Dist Provision' could not be found
## Cross-referencing note
The user in Comment 4 has filed Bug 60299 about the "specified provisioning profile ... could not be found" error with additional information, so I will resolve this bug at this time.