Open scottkuhl opened 1 month ago
This applies to this article as well: Mac Catalyst entitlements
Hi @scottkuhl
Agreed about the docs update, but as a quick answer it's literally a case of having to add an XML file to the project and hand edit it.
I think this is a separate issue, but these pages also need updating:
Automatic provisioning for iOS apps Manual provisioning for iOS apps
These are probably more important, because the IDEs hide some "magic" that handles some very complicated stuff.
@davidbritch would you like me to open a separate issue for those?
Hi @scottkuhl
Please go ahead. It's all known issues that anything with VSMac content needs VSCode versions, but you creating issues will save me doing so.
There's no good story about a lot of this stuff in VSCode though. It's the whole VSCode being an editor versus VSMac being an IDE. So in VSCode provisioning is a case of using Xcode to pull down provisioning profiles, and then using command line to set certificates/profiles.
There's no good story about a lot of this stuff in VSCode though. It's the whole VSCode being an editor versus VSMac being an IDE. So in VSCode provisioning is a case of using Xcode to pull down provisioning profiles, and then using command line to set certificates/profiles.
Even documenting that process would help. I'll open another story. Thanks.
Type of issue
Outdated article
Description
With the retirement of Visual Studio for Mac there are currently no instructions on how to get entitlements working for iOS or MacCatalyst while developing on a Mac. The sections for Visual Studio for Mac should be updated to instructions for VS Code.
Page URL
https://learn.microsoft.com/en-us/dotnet/maui/ios/entitlements?view=net-maui-8.0&tabs=vs
Content source URL
https://github.com/dotnet/docs-maui/blob/main/docs/ios/entitlements.md
Document Version Independent Id
3305d4a0-d05c-84db-0388-2dc01fbbcfc3
Article author
@davidbritch
Metadata