This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(201.6, 96%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EU%3C/text%3E%3C/svg%3E)
I cannot get Visual Studio to publish my .net maui application correctly.
When I look at the WindowsApp.Manifest the information appears to match the information that the partner center is expecting to see, however, when I upload the app to the partner center I get a slew of errors. IDK how to fix this...
Here is the PackageApp,Manifest --- NOTE that the Publisher and the Package Family name are correct.
And here are the reported errors
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(22.400000000000002, 3%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EWZ%3C/text%3E%3C/svg%3E)
however, when I upload the app to the partner center I get a slew of errors.
There are several steps to publish a .NET MAUI app for Windows with Visual Studio, you packaged your project without error following the doc above, right? And you got the errors when you publish your app in the Microsoft Store, right? Did you upload the msix file? Do you add any capabilities for your app? What's the detailed VS version? Is your project based on .NET7?
Glad you solved the problem. As a solution, I convert the comment to an answer.
In addition, images of text (including source or errors) are not accessible and are hard to work with. It's better to edit the error messages into the post as text. In this way, it will make thread searching in the forum easier and be beneficial to other community members as well. Thanks for your understanding.
I finally found the problem. I have to create a temporary certificate using my publisher ID instead of publisher Name. Then it was happy...