Bug 55193 - iOS app cannot be signed when a non-automatic provisioning profile is selected
Summary: iOS app cannot be signed when a non-automatic provisioning profile is selected
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: 4.5.0 (15.2)
Hardware: PC Windows
: Normal normal
Target Milestone: 15.3
Assignee: Emanuel
: 53155 ()
Depends on:
Reported: 2017-04-13 19:49 UTC by Dimitar Dobrev
Modified: 2017-07-13 09:12 UTC (History)
6 users (show)

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:

Description Dimitar Dobrev 2017-04-13 19:49:45 UTC
The problem is that when the provisioning profile is selected, VS writes a GUID instead of the name to the .csproj. This later causes compilation of the IPA to fail with "No iOS signing identities match the specified provisioning profile". Xamarin Studio works properly as fixed at https://bugzilla.xamarin.com/show_bug.cgi?id=25499 .
Comment 1 xamarin-release-manager 2017-05-19 15:59:04 UTC
Fixed in version (master)

Author: Emanuel
Commit: 78298d5d525fd818e17877e6baeb4bd0e7f603ee (xamarin/XamarinVS)
Comment 2 Emanuel 2017-05-22 17:26:44 UTC
*** Bug 53155 has been marked as a duplicate of this bug. ***