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.
Created attachment 13925 [details]
Detailed version info
[XVS.iOS 4.0] Certain distribution provisioning profiles do not appear in the iOS project settings
(This is an intentional duplicate of non-public Bug 35615 for public tracking and to document a possible temporary workaround.)
## Possible temporary workaround
This problem is limited to _browsing_ the provisioning profiles. If you set the desired "CodesignProvision" and "CodesignKey" using Xamarin Studio on Mac, the values will be preserved in the project file, and the app will be signed correctly when _building_ in Visual Studio on Windows. Similarly, if you set the desired provisioning profile on Mac, save the project, and then open the `.csproj` file in a text editor, you can find the `<CodesignProvision>` and `<CodesignKey>` elements, and then copy them into the corresponding location in the `.csproj` file on Windows. (Be sure to place these properties under the matching `<PropertyGroup Condition=" '$(Configuration)|$(Platform)'` section of the file that corresponds to the configuration you wish to use`.)
## Regression status: regression in XamarinVS 4.0
BAD: XamarinVS 184.108.40.2069 (f860fe4) + Xamarin.iOS 220.127.116.11 (3c0ec35)
GOOD: XamarinVS 3.11.1594.0 (a06d6d5) + Xamarin.iOS 18.104.22.168 (1f068b4)
## Steps I followed to reproduce
1. Create a new iOS application or open an existing iOS application.
2. Set the configuration to "Release|iPhone".
3. Open the project properties, and navigate to "iOS Bundle Signing".
4. Ensure the "Identity" is set to a valid Distribution identity (or "Distribution (Automatic)").
5. Click the "Provisioning profile" drop-down.
## Actual Results
I have 2 non-expired distribution profiles present in "$HOME/Library/MobileDevice", but _only_ the "AdHoc Distribution, Wildcard" provisioning profile is displayed in the "Provisioning profile" drop-down at step 5.
> <string>Xcode iOS Wildcard App ID</string>
> <string>AppStore distribution wildcard</string>
> <string>Xcode iOS Wildcard App ID</string>
> <string>AdHoc Distribution, Wildcard</string>
## Expected Results
In XamarinVS 3.11, the "AppStore distribution wildcard" provisioning profile appears as expected in the iOS project properties.
A candidate patch has been committed to fix this issue. It is currently targeted for inclusion in an Alpha Channel Service Release during the week of November 23.
I will post any relevant additional updates on this bug report as they become available.
*** Bug 36193 has been marked as a duplicate of this bug. ***
The patch for this issue has not yet been merged into the initial version of "Cycle 6 – Service Release 0" that is planned for release to the Alpha Channel this week.
It might be included in a later build of Service Release 0, but for the moment the most direct way to address the problem is to continue using the "temporary workaround" from comment 0.
I will continue to post any further updates on this bug report as they become available.
I will tentatively mark this as "reopened" based on my preliminary testing with development builds that included the candidate patch for this issue. In those preliminary tests, my distribution profiles did not appear as expected.
I will test again with the Cycle 6 – Service Release 1 Alpha builds and update accordingly.
## Verification status: not yet fixed in Cycle 6 – Service Release 1 Alpha 1
BAD: XamarinVS 22.214.171.124 (944b6bd) + Xamarin.iOS 126.96.36.199 (97af501)
Now both of my distribution provisioning profiles [1, 2] are absent from the menu. Maybe this is an interesting clue?
 "AppStore distribution wildcard"
 "AdHoc Distribution, Wildcard"
*** Bug 35615 has been marked as a duplicate of this bug. ***
Fixed in version 188.8.131.527 (xcode7.1)
Commit: b3abd4d93a494fe278f1b71d313bf2c5c58dff53 (xamarin/XamarinVS)
I have xcode7.2. Does it work there?
## Status clarification for any users CC'd on the bug
The candidate fix for this issue is included in the latest Alpha version of "Cycle 6 - Service Release 1" .
### Side note: Xcode version should not affect this bug
The Mac build host's Xcode version should not affect this bug. To clarify about the automated text in Comment 14, "(xcode7.1)" is just a branch name for the XamarinVS source code where a candidate fix for this bug was initially committed. That fix has now been merged into "Service Release 1". The fix is present in XamarinVS itself, so the Mac build host's Xcode version is not too important.
## Verification status: fixed with the latest Alpha versions
GOOD: XamarinVS 184.108.40.206 (7082690) + Xamarin.iOS 220.127.116.11 (78c6cd3)
I was able to find both of my distribution profiles (as well as all of my development profiles) using the latest Alpha versions. I was also able to select and save either of the profiles correctly, and I was build and sign successfully.
## Status update for any users watching this bug
There is at least one additional case where provisioning profiles are not displayed as expected in the Visual Studio project properties in the current Stable version. That remaining issue is now being tracked in its own bug report:
Bug 38585 - Enterprise "In House" provisioning profiles do not appear in the drop-down menu in the iOS project settings editor
Fixed in version 18.104.22.168 (cycle6)
Commit: f2e586517abe2c0558a04a729d45f7f08336aa91 (xamarin/XamarinVS)