Open baaaaif opened 11 months ago
Hi, have the same problem. The proposed workaround is not enough for me when I am controlling the ApplicationBuild version using msbuild property once for ios & android & windows during the azure devops build.
The last portion indeed needs to be 0 is you want to publish to the store: https://learn.microsoft.com/windows/apps/publish/publish-your-app/package-version-numbering?pivots=store-installer-msix#version-numbering-for-windows10-and-11-packages
Hi, have the same problem. The proposed workaround is not enough for me when I am controlling the ApplicationBuild version using msbuild property once for ios & android & windows during the azure devops build.
We are doing this via DevOps as well.
Description
When I try to upload our app to the MS Store i get the following message:
Package acceptance validation error: Apps are not allowed to have a Version with a revision number other than zero specified in the app manifest. The package xx.yy.zz_7.0.0.5089_x64_Release.msix specifies 7.0.0.5089.
this is caused by `
`
in combination with https://github.com/dotnet/maui/blob/main/src/SingleProject/Resizetizer/src/GeneratePackageAppxManifest.cs#L350 which always places the ApplicationVersion to the 4. position / revision number
Either I'm missing something, or it can't work that way at the moment
Steps to Reproduce
Link to public reproduction project repository
No response
Version with bug
7.0.100
Is this a regression from previous behavior?
Not sure, did not test other versions
Last version that worked well
Unknown/Other
Affected platforms
Windows
Affected platform versions
No response
Did you find any workaround?
manually set Version in Package.appxmanifest instead of 0.0.0.0
Relevant log output