Can't use certificate by trusted source while publishing maui blazor app

[ParkerRedford]

Description

I'm trying to publish a maui blazor app using a certificate by a trusted source, but the manifest is giving me an error.

Steps to Reproduce

1. Created the pfx file using openssl
   
2. Installed the certificate on Windows
3. Modified the project file
   
4. Modified the Package.appxmanifest file
   
5. Selected the pfx file from the Packaging tab and provided my password, which gives me the error message
   

Version with bug

6.0 (current)

Last version that worked well

Unknown/Other

Affected platforms

Windows

Affected platform versions

net6.0-windows10.0.19041.0

Did you find any workaround?

No, .net maui non hybrid app gives me the same error.

Relevant log output

No response

[jfversluis]

What if you don't use the manifest designer and just follow the Docs for this, but now with an already existing certificate?

I don't see why the process for a trusted certificate should be different than a self-signed one. My gut feeling says this is something in the tooling that is not ready for this scenario that you're following yet.

[ParkerRedford]

I ran 'dotnet publish -f net6.0-windows10.0.19041.0 -c Release' by going through the docs, but I got a similar error but it's from the console

[ParkerRedford]

If I ran the same command in Package Manager Console, I got no error but no certificate was exported. I'm not sure using Package Manager Console makes any difference.

[mattleibow]

What happens if you use this certificate in a plain WinUI app? We are using the underlying tooling from WinUI for the final signing and packaging stage. I wonder if WinUI is needing some special format or encoding or password rules?

[ghost]

Hi @ParkerRedford. We have added the "s/needs-info" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

[ghost]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.