More information when provisioning goes wrong

[borrrden]

Description

As infuriating as Apple provisioning is in general, now that VS Code for mac is gone there is no replacement and the command line is extremely terse. All it says is "Could not find any available provisioning profiles for MauiApp1 on iOS."

Ok, could it say anything about why? I deleted all provisioning profiles from my machine except for one (com.couchbase.*). I have it on a newly generated certificate which has the private key (there are no other dev certs in my machine) and the app ID is com.couchbase.mauiapp1. All signs say that this should be fine, yet the dotnet CLI says otherwise.

In lieu of that, perhaps some documentation on the keys that are used in csproj since "automatic provisioning" is no longer a thing. All the docs seem to focus on Windows which is not an ideal experience for developing for iOS.

Public API Changes

Nothing

Intended Use-Case

To not waste hours of time trying to figure out why Apple is unsatisfied....

[borrrden]

I figured out that I need to add the filename of the provisioning profile (UUID) to the CodesignProvision key to make it force use a certain profile, and doing that helped me realize that the Info.plist bundle identifier was out of date. I don't think I ever would have found this out with the message I indicated above.

[dotnet-policy-service]

Thanks for the issue report @borrrden! This issue appears to be a problem with Visual Studio (Code), so we ask that you use the VS feedback tool to report the issue. That way it will get to the routed to the team that owns this experience in VS (Code).

If you encounter a problem with Visual Studio or the .NET MAUI VS Code Extension, we want to know about it so that we can diagnose and fix it. By using the Report a Problem tool, you can collect detailed information about the problem, and send it to Microsoft with just a few button clicks.

1. Go to the Visual Studio for Windows feedback tool or .NET MAUI VS Code Extension repository to report the issue
2. Close this bug, and consider adding a link to the VS Feedback issue so that others can follow its activity there.

[borrrden]

Neither Visual studio nor visual studio code was involved here. This was straight from the command line running dotnet 9 CLI.

[jfversluis]

That might be, this is still a tooling issue and the above places are the correct place to report this.