search

dotnet / maui

.NET MAUI is the .NET Multi-platform App UI, a framework for building native device applications spanning mobile, tablet, and desktop.
https://dot.net/maui
MIT License
22.27k stars 1.76k forks source link

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 #25741

Closed Raul-fc closed 2 weeks ago

Raul-fc commented 2 weeks ago

Description

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, 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

Link to public reproduction project repository

No response

Version with bug

9.0.0-rc.2.24503.2

Is this a regression from previous behavior?

Yes, this used to work in .NET MAUI

Last version that worked well

No response

Affected platforms

iOS

Affected platform versions

No response

Did you find any workaround?

No response

Relevant log output

No response

dotnet-policy-service[bot] commented 2 weeks ago

Thanks for the issue report @Raul-fc! 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.
jfversluis commented 2 weeks ago

This is a tooling issue and not something that originates in the .NET MAUI SDK. Unfortunately, there is not much we can do from our team about this. See the comment above for instructions on how to report this to the right team so it will be handled appropriately, thanks!

MarcoErlwein commented 2 weeks ago

I have the same problem, with old certificates and provision profiles there is no problem, it's just new ones. What other way is there now to generate the Bundled and send it to Testflight? thank you