Bug 27746 - Provision Profiles Containing Commas Do Not Appear Properly in the Dropdown List
Summary: Provision Profiles Containing Commas Do Not Appear Properly in the Dropdown List
Status: RESOLVED FIXED
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: 3.9
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Joaquin Jares
URL:
Depends on:
Blocks:
 
Reported: 2015-03-06 18:30 UTC by Jimmy [MSFT]
Modified: 2016-06-01 18:05 UTC (History)
8 users (show)

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

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:
Status:
RESOLVED FIXED

Description Jimmy [MSFT] 2015-03-06 18:30:45 UTC
=== 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
Comment 2 Brendan Zagaeski (Xamarin Team, assistant) 2015-03-06 19:01:31 UTC
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.
Comment 9 Joaquin Jares 2016-06-01 18:05:24 UTC
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.