Bug 58251 - When looking for valid signing certificates, print out each invalid certificate and state why it's not valid
Summary: When looking for valid signing certificates, print out each invalid certifica...
Status: CONFIRMED
Alias: None
Product: iOS
Classification: Xamarin
Component: MSBuild (show other bugs)
Version: master
Hardware: PC Mac OS
: --- enhancement
Target Milestone: Future Cycle (TBD)
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2017-07-19 14:34 UTC by Rolf Bjarne Kvinge [MSFT]
Modified: 2017-10-09 05:25 UTC (History)
1 user (show)

See Also:
Tags:
Is this bug a regression?: ---
Last known good build:


Attachments

Description Rolf Bjarne Kvinge [MSFT] 2017-07-19 14:34:07 UTC
When diagnosing why code signing fails, such as:

> error : No valid iOS code signing keys found in keychain. You need to request a codesigning certificate from https://developer.apple.com.

it would be helpful to know why the existing certificates on the machine (if any) aren't applicable.

Such as:

"The certificate C is not valid because its prefix P does not match any of the app's prefixes P1, P2, ..."
"The certificate C is not valid because it expired on October 21st, 2015"
Comment 1 Rolf Bjarne Kvinge [MSFT] 2017-10-04 11:07:21 UTC
Partially implemented: https://github.com/xamarin/Xamarin.MacDev/pull/16
Comment 2 Rolf Bjarne Kvinge [MSFT] 2017-10-09 05:25:03 UTC
Partially fixed in https://github.com/xamarin/xamarin-macios/pull/2865

Note You need to log in before you can comment on or make changes to this bug.