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 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.
=== Overview ===
A provisioning profile who's name contains a comma, for example "Xamarin, LLC", does not appear correctly in Visual Studio. Attempting to use the profile gives you a "does not exist" error.
=== Steps to Reproduce ===
1. Have a provisioning profile set up that contains a comma in its name, e.g. "Xamarin, LLC"
2. In Visual Studio, right click the iOS project and go to "Properties > iOS Bundle Signing"
3. In the Provisioning profile dropdown menu, select the test profile. It will appear with the comma and everything after it truncated, e.g. "Xamarin"
=== Actual Results ===
Trying to use the profile gives a "does not exist error" because the name in VS does not exactly match the actual name of the profile.
=== Expected Results ===
The app builds and deploys successfully to a device
Based on the screenshots in the Desk case, the problem is with commas in the "Identity" field, not the "Provisioning Profile" field.
As such I believe this is a duplicate of bug 24940.
Provisioning profiles where changed for other reasons recently and this has been fixed as a side effect (and no longer a repro). The fix is in the next cycle, but unreleased yet. Marking as fixed for internal verification.