iOS Bundle Signing doesn't work for In-House teams and a profile with wildcard
I can't deploy my example app on a real iOS device, using the updated iOS signing workflow.
I'm trying to use a signing profile that already works on XCode. The profile is for In-House apps and has a wildcard to match bundle IDs. I can correctly choose my "Signing Identity", but it then gives me the message "Failed to refresh provisioning profiles combo." and I can't choose a "Provisioning Profile".
My user permissions don't allow me to create a profile, so I couldn't verify what the profile would be, but it seems to be a problem with the wildcard and fastlane. Maybe the fact that the team is In-House might have an influence too.
The old method works correctly.
Facing the similar issues. Tried to install provisioning certificates on my new Mac mini and now visual studio hangs for ever on selecting Project->Options->iOS bundle signing.
Thank you for your feedback! For us to investigate this further, could you please update to the latest stable release and advise whether the issue occurs there? We look forward to hearing from you!
Thank you for your feedback! Unfortunately, right now we don't have enough information to investigate this issue and find a solution. If this is still an issue for you, please update to our latest version. If you are still able to repro it, please provide the following:
- Minimized test case
- Zipped logs from Help > Open Log Directory
- Full version details from Visual Studio > About Visual Studio > Show Details > Copy Information [button]
Thank you for helping us build a better Visual Studio!
I am facing the similar problem. In-House app with a wild card identifier will not show the provisioning profiles. It will also not show the distribution certificate as a Signing Identity choice, only the one I have for development.
My setup:
=== Visual Studio Community 2017 for Mac === Version 7.1 (build 1297) Installation UUID: 2acdd559-8012-4329-9750-cf26dd98befc Runtime: Mono 5.2.0.215 (d15-3/da80840) (64-bit) GTK+ 2.24.23 (Raleigh theme) Package version: 502000215 === NuGet === Version: 4.3.0.2418 === .NET Core === Runtime: /usr/local/share/dotnet/dotnet Runtime Versions: 1.1.1 1.0.4 SDK: /usr/local/share/dotnet/sdk/1.0.3/Sdks SDK Version: 1.0.3 MSBuild SDKs: /Library/Frameworks/Mono.framework/Versions/5.2.0/lib/mono/msbuild/15.0/bin/Sdks === Xamarin.Profiler === Version: 1.5.5 Location: /Applications/Xamarin Profiler.app/Contents/MacOS/Xamarin Profiler === Apple Developer Tools === Xcode 8.3.3 (12175.1) Build 8E3004b === Xamarin.Android === Version: 7.4.0.21 (Visual Studio Community) Android SDK: /Users/kysterket/Library/Developer/Xamarin/android-sdk-macosx Supported Android versions: 6.0 (API level 23) SDK Tools Version: 25.2.5 SDK Platform Tools Version: 25.0.5 SDK Build Tools Version: 25.0.3 Java SDK: /usr java version "1.8.0_101" Java(TM) SE Runtime Environment (build 1.8.0_101-b13) Java HotSpot(TM) 64-Bit Server VM (build 25.101-b13, mixed mode) Android Designer EPL code available here: https://github.com/xamarin/AndroidDesigner.EPL === Xamarin.iOS === Version: 10.12.0.20 (Visual Studio Community) Hash: 80b8487d Branch: d15-3 Build date: 2017-08-18 16:07:26-0400 === Xamarin Inspector === Version: 1.2.2 Hash: b71b035 Branch: d15-1 Build date: Fri, 21 Apr 2017 17:57:12 GMT === Xamarin.Mac === Version: 3.6.0.19 (Visual Studio Community) === Build Information === Release ID: 701001297 Git revision: 9c5299666538b2f8baf501418a5c064d784d64da Build date: 2017-08-07 11:29:35-04 Xamarin addins: 3bb0c32a14f1b7e368bf5ac53a84c3581c019391 Build lane: monodevelop-lion-d15-3 === Operating System === Mac OS X 10.12.6 Darwin 16.7.0 Darwin Kernel Version 16.7.0 Thu Jun 15 17:36:27 PDT 2017 root:xnu-3789.70.16~2/RELEASE_X86_64 x86_64
No problem with XCode for provisioning profiles but in Visual Studio for Mac 7.1 similar problem for (Dev & Distribution).
Thank you for your feedback! We have fixed the problem in an upcoming release. Thank you for helping us build a better Visual Studio!
Thanks @Al Clark - any chance you can confirm if this would have been part of the most recent release? Or will it be part of a future release? Not sure if I should expect to see a difference yet.
Hi, when is the upcoming release please as this stops me from signing anything as I get the error: failed to refresh to provisioning profile combo.
Sorry to hear that. Could you copy your setup info Visual Studio -> About -> Show Details -> Copy Information create a gist with this text and post the link here?
You should be able to "roll back" to the previous version of signing controls by selecting "None" in team drop down.
To do it open:
1) iOS Bundle Signing panel in project options
2) Select "None" in team drop down to enable old signing controls
Old singing drop downs for certificates and provisioning profiles have no new fancy features but they should work just fine with whatever certificates and profiles you have installed on your machine.
Please let me know if it solved the problem for you.
45 People are following this
