Installed vs for mac 2022 on a new machine but the bundle signing option is just black/empty? I've tried all the latest stable updates. I'd really like to avoid installing the old version of Xamarin. Stackoverflow wont let me post the full detailed installation description but hopefully these are the most interesting.
Visual Studio Community 2022 for Mac
Version 17.0.6 (build 4)
Runtime
.NET 6.0.5 (64-bit)
Architecture: Arm64
NuGet
Version: 6.0.0.262
.NET SDK (Arm64)
SDK: /usr/local/share/dotnet/sdk/6.0.302/Sdks
SDK Versions:
6.0.302
6.0.100
MSBuild SDKs: /Applications/Visual Studio.app/Contents/MonoBundle/MSBuild/Current/bin/Sdks
.NET Runtime (Arm64)
Runtime: /usr/local/share/dotnet/dotnet
Runtime Versions:
6.0.7
6.0.0
Xamarin Designer
Version: 17.1.5.90
Branch: remotes/origin/d17-0-vsmac
Build date: 2022-07-07 17:09:33 UTC
Apple Developer Tools
Xcode 13.4.1 (20504)
Build 13F100
Xamarin.Mac
Version: 8.10.0.5 (Visual Studio Community)
Branch: d17-2
Build date: 2022-05-18 07:32:06-0400
Xamarin.iOS
Version: 15.10.0.5 (Visual Studio Community)
Branch: d17-2
Build date: 2022-05-18 07:32:07-0400
Build Information
Release ID: 1700060004
Git revision: 056076d45137bf76b73f62f871524da8890deb05
Build date: 2022-07-07 17:06:59+00
Build branch: release-17.0
Build lane: release-17.0
Operating System
Mac OS X 12.4.0
Darwin 21.5.0 Darwin Kernel Version 21.5.0
Tue Apr 26 21:08:37 PDT 2022

Found another thread online that resolved the issue by commenting out the CodesignKey and CodesignProvision manually in the project file (for all configurations).
Worked for me! The bundle signing option view is displayed again and you can finish your setup.
E.g.
<!--<CodesignKey>iPhone Developer: Your value here </CodesignKey>-->
<!--<CodesignProvision> Your value here </CodesignProvision>-->
Just to extend answer from Cliffhanger. This is because your signing certificate for the selected debug or release profile isnt on this Mac. For example, if you had certificate in 1 mac and you changed to another Mac which doesn't have the certificate. Simple workaround without amending project file configuration is to select another debug or release configuration which doesnt have any signing yet For example, Debug|IphoneSimulator and select Sigining will show the Ui, there you can change release profile signing.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With