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.
Currently MD has two combo boxes for selecting the signing identity and provisioning profile. Each has explicit and automatic options. Automatic is better because it's less likely to break between different developers on the same project, but specifying an explicit item is sometimes necessary for disambiguation.
It's confusing to have two combo boxes, because most of the permutations are redundant or broken.
Each identity can match multiple provisioning profiles. Each provisioning profile exactly matches an identity. So explicitly specifying the identity is redundant. The exception to this is the two variants of automatic identity: "automatic (developer)" and "automatic (distribution)", which filter the keys that MD considers when doing automatic matches.
Multiple provisioning profiles can match a single app ID, and one provisioning profile can match multiple app IDs (wildcard) so we can automatically pick a valid provisioning profile this way.
This means the two primary valid sets of options are:
* Automatic identity, automatic provisioning profile:
MD will find a provisioning profile that matches the app bundle ID, and an identity that matches the provisioning profile.
* Automatic identity, explicit provisioning profile:
MD will find an identity that matches the provisioning profile.
We can simplify the selection UI and make it harder to break things by reducing it to a single combobox, like Xcode. This would list all the provisioning profiles, and provide two automatic (developer/distribution) options, which would correspond to the above uses. In addition, we could show a little more info about each item, such as the pairings of identities/profiles, and the values that the automatic options would resolve to.