search

microsoft / vscode-dotnettools

This is a feedback repository to capture issues logged for the C# Dev Kit and related extensions from Visual Studio Code
Other
234 stars 13 forks source link

[BUG] Publishing MAUI App to the Store - The newly created provisioning profile is not listed, but the old ones are, and the "Download manual profiles" process has been done from Xcode. #1595

Closed Raul-fc closed 1 week ago

Raul-fc commented 2 weeks ago

Describe the Issue

I am trying to publish my MAUI app, but the newly created provisioning profile is not showing up, although the old ones that are about to expire are listed. I have Xcode 16, Visual Studio 2022, and Visual Studio Code installed.

I followed the process of 'Request a certificate from a certificate authority' from Keychain Access, then created the distribution certificate, identifier, provisioning profile, and created the app in App Store Connect.

Then, from Xcode, I linked my account and performed the "download manual profiles" process.

I created a MAUI project in Visual Studio 2022 and another one in Visual Studio Code using the '.NET MAUI - Archive / Publish tool' extension, and added 'ApplicationTitle', 'ApplicationId', and 'ApplicationGuid' in the .csproj file.

Then, from Visual Studio 2022, in the properties under iOS, Bundle Signing, I tried adding the 'Signing Identity', but the created provisioning profile does not show up in the Provisioning Profile section. Image

In VSCode using the '.NET MAUI-Archive/Publish tool' extension, after running 'Maui Archive: Publish iOS', selecting the .csproj, and choosing a signing identity, the newly created provisioning profile is also not shown.

Image

Steps To Reproduce

No response

Expected Behavior

No response

Environment Information

No response

AllenD-MSFT commented 1 week ago

Publishing operations in Visual Studio aren't covered here in this issue list. Instead one should use the Feedback mechanism in Visual Studio to report issues there. This problem of downloading profiles is a known issue I believe and a fix should be made available as an update to Visual Studio soon I hope.