WindowsAppSDK
WindowsAppSDK copied to clipboard
microsoft
Partner Center reporting a bug for latest version of BuildTools
Describe the bug
I have an application that builds, runs and passes all validation tests locally, but when I submit it to the store, I get:
Package acceptance validation error: The package Desktop (Package)_1.35.14.0_x86_Production.msix uses an unsupported version of file makepri.exe (10.0.26100.1). The following versions are allowed: < 10.0.10500.0; >= 10.0.10586.0 & < 10.0.11000.0; >= 10.0.14383.0 & < 10.0.14800.0; >= 10.0.15053.0 & < 10.0.15100.0; >= 10.0.16299.0 & < 10.0.16350.0; >= 10.0.17134.0 & < 10.0.17500.0; >= 10.0.17763.0 & < 10.0.18199.0; >= 10.0.18362.0 & < 10.0.18799.0; >= 10.0.19041.0 & < 10.0.19399.0; >= 10.0.20348.0 & < 10.0.21242.0; >= 10.0.22000.194 & < 10.0.22350.0; >= 10.0.22621.0 & < 10.0.25054.0. Please update your Visual Studio build tools and try again. Package acceptance validation error: The package Desktop (Package)_1.35.14.0_x64_Production.msix uses an unsupported version of file makepri.exe (10.0.26100.1). The following versions are allowed: < 10.0.10500.0; >= 10.0.10586.0 & < 10.0.11000.0; >= 10.0.14383.0 & < 10.0.14800.0; >= 10.0.15053.0 & < 10.0.15100.0; >= 10.0.16299.0 & < 10.0.16350.0; >= 10.0.17134.0 & < 10.0.17500.0; >= 10.0.17763.0 & < 10.0.18199.0; >= 10.0.18362.0 & < 10.0.18799.0; >= 10.0.19041.0 & < 10.0.19399.0; >= 10.0.20348.0 & < 10.0.21242.0; >= 10.0.22000.194 & < 10.0.22350.0; >= 10.0.22621.0 & < 10.0.25054.0. Please update your Visual Studio build tools and try again. Package acceptance validation error: The package Desktop (Package)_1.35.14.0_ARM64_Production.msix uses an unsupported version of file makepri.exe (10.0.26100.1). The following versions are allowed: < 10.0.10500.0; >= 10.0.10586.0 & < 10.0.11000.0; >= 10.0.14383.0 & < 10.0.14800.0; >= 10.0.15053.0 & < 10.0.15100.0; >= 10.0.16299.0 & < 10.0.16350.0; >= 10.0.17134.0 & < 10.0.17500.0; >= 10.0.17763.0 & < 10.0.18199.0; >= 10.0.18362.0 & < 10.0.18799.0; >= 10.0.19041.0 & < 10.0.19399.0; >= 10.0.20348.0 & < 10.0.21242.0; >= 10.0.22000.194 & < 10.0.22350.0; >= 10.0.22621.0 & < 10.0.25054.0. Please update your Visual Studio build tools and try again.
Steps to reproduce the bug
-
Install the latest version of SDK BuildTools in your WinUI project. <PackageReference Include="Microsoft.Windows.SDK.BuildTools" Version="10.0.26100.1" />
-
Update to the latest version of Visual Studio.
-
Build your application.
-
Submit it to the Windows Store.
Expected behavior
I expect the application to pass the validation tests.
Screenshots
NuGet package version
None
Packaging type
Packaged (MSIX)
Windows version
No response
IDE
Visual Studio 2022
Additional context
No response
To clarify, the app I tried submitted is a UWP app. I think the Partner Center isn't ready for 10.0.26100 yet.
Same issue here as well. Reverting back to this version in the mean time.
<PackageReference Include="Microsoft.Windows.SDK.BuildTools" Version="10.0.22621.3233" />
uninstall "Microsoft.Windows.SDK.BuildTools" from the app Packages seems to remove the pb to me
The version 10.0.26100.1 was updated on May 22, 2024 and after a month or more, Microsoft Partner Center is not ready for it. Reverting back to the version 10.0.22621.3233 solved the issue.
Also just hit this problem, but have no workaround, as some of my dependencies already bumped to latest stable as well
Same here, we can't deploy our latest version UNO app, and we can't down grade.
@SolidRockProgrammer if you don't mind using older version of Uno.Extensions, you can use the following in Directory.Build.Props:
<!-- Temporary workaround for https://github.com/microsoft/WindowsAppSDK/issues/4480 -->
<WinAppSdkBuildToolsVersion Condition="$(TargetFramework.Contains('windows10'))">10.0.22621.3233</WinAppSdkBuildToolsVersion>
<UnoExtensionsVersion Condition="$(TargetFramework.Contains('windows10'))">4.2.2</UnoExtensionsVersion>
This is, of course, just a workaround, and the issue itself needs to be resolved
Is that really STILL a thing??
Got the following error: Package acceptance validation error: The package Packaging Project_2.2.1.0_x86.appx uses an unsupported version of file makepri.exe (10.0.26100.1). The following versions are allowed: < 10.0.10500.0; >= 10.0.10586.0 & < 10.0.11000.0; >= 10.0.14383.0 & < 10.0.14800.0; >= 10.0.15053.0 & < 10.0.15100.0; >= 10.0.16299.0 & < 10.0.16350.0; >= 10.0.17134.0 & < 10.0.17500.0; >= 10.0.17763.0 & < 10.0.18199.0; >= 10.0.18362.0 & < 10.0.18799.0; >= 10.0.19041.0 & < 10.0.19399.0; >= 10.0.20348.0 & < 10.0.21242.0; >= 10.0.22000.194 & < 10.0.22350.0; >= 10.0.22621.0 & < 10.0.25054.0. Please update your Visual Studio build tools and try again.
CC @Sergio0694 @dpaulino - do you have a point of contact for this at Partner Center team that could help please?
I'd suggest pinging ankur06 in the microsoft-store channel on Discord (https://aka.ms/microsoftstorediscord).
He's the PM for Partner Center working on the submission pipeline, he might be able to help.
As far as I know though this is just a matter of the pipeline not having been updated yet, so it likely just needs time.
Keep in mind that 26100 isn't even out yet (the SDK is stable, but Windows 26100 isn't available yet in GA).
Hey, @DRAirey1 I am newly joining the team and will take a look at this? Thanks!
Microsoft have requested an update to one of my apps and will delist the app at the end of the September if a new version has not been published by then. This issue is a major inconvenience.
@KevinLaMS, slightly off topic: I have some devices that are already on 10.0.26100 and I'm noticing a pattern that those devices are not getting automatic updates for UWP apps that I have in the Store with new updates. TargetPlatformVersion is 10.0.22621.0 and TargetPlatformMinVersion is 10.0.19041.0 for those apps. They are LOB apps.
I assumed insider builds would get apps automatically updated since they're always going to be higher than the TargetPlatformVersion. What's preventing automatic updates?
Same here The thing that worked for me is to remove the reference of the build tools. Azure Devops build seems to figure it out itself.
@IsmailHassani
unfortunately we are not using Azure Devops (we are using GitHub tools) so that's not an option for us
People saying that removing "the reference to the build tools" fixed the problem, do you mean that you were able to use the old SDK to build you app, or that you managed to use the latest SDK?
I removed the SDK and built my UWP using the old SDK, would not call that a fix though.
People saying that removing "the reference to the build tools" fixed the problem, do you mean that you were able to use the old SDK to build you app, or that you managed to use the latest SDK?
I removed the SDK and built my UWP using the old SDK, would not call that a fix though.
This depends totally on which version of the buildtools is installed on de build server. Azure Devops hosted build server uses an older version hence the error. If you have your own build server, there is probably an older version installed. Either update this one or downgrade the sdk buildtools to the same version. I'm using Azure Devops and noticed, that i didn't need the strong refrence in my csproj file (WinUI). Last week finished updates and publication of 5 apps to the Microsoft store.
Frankly i don't know why i would need this reference in my project if the build server already has this sdk. ;)
A thing to consider is of course the fact that some people mention UWP which has a different project structure and afaik only buildable with msbuild. WinUI can be build with dotnet publish.
I've tried the new SDK which is now available, version is 10.0.21600.1742
Still the same issue:
Package acceptance validation error: The package uses an unsupported version of file MakePri.exe (10.0.26100.1742). The following versions are allowed: < 10.0.10500.0; >= 10.0.10586.0 & < 10.0.11000.0; >= 10.0.14383.0 & < 10.0.14800.0; >= 10.0.15053.0 & < 10.0.15100.0; >= 10.0.16299.0 & < 10.0.16350.0; >= 10.0.17134.0 & < 10.0.17500.0; >= 10.0.17763.0 & < 10.0.18199.0; >= 10.0.18362.0 & < 10.0.18799.0; >= 10.0.19041.0 & < 10.0.19399.0; >= 10.0.20348.0 & < 10.0.21242.0; >= 10.0.22000.194 & < 10.0.22350.0; >= 10.0.22621.0 & < 10.0.25054.0. Please update your Visual Studio build tools and try again.
Package acceptance validation error: The package uses an unsupported version of file MakePri.exe (10.0.26100.1742). The following versions are allowed: < 10.0.10500.0; >= 10.0.10586.0 & < 10.0.11000.0; >= 10.0.14383.0 & < 10.0.14800.0; >= 10.0.15053.0 & < 10.0.15100.0; >= 10.0.16299.0 & < 10.0.16350.0; >= 10.0.17134.0 & < 10.0.17500.0; >= 10.0.17763.0 & < 10.0.18199.0; >= 10.0.18362.0 & < 10.0.18799.0; >= 10.0.19041.0 & < 10.0.19399.0; >= 10.0.20348.0 & < 10.0.21242.0; >= 10.0.22000.194 & < 10.0.22350.0; >= 10.0.22621.0 & < 10.0.25054.0. Please update your Visual Studio build tools and try again.
Package acceptance validation error: The package uses an unsupported version of file MakePri.exe (10.0.26100.1742). The following versions are allowed: < 10.0.10500.0; >= 10.0.10586.0 & < 10.0.11000.0; >= 10.0.14383.0 & < 10.0.14800.0; >= 10.0.15053.0 & < 10.0.15100.0; >= 10.0.16299.0 & < 10.0.16350.0; >= 10.0.17134.0 & < 10.0.17500.0; >= 10.0.17763.0 & < 10.0.18199.0; >= 10.0.18362.0 & < 10.0.18799.0; >= 10.0.19041.0 & < 10.0.19399.0; >= 10.0.20348.0 & < 10.0.21242.0; >= 10.0.22000.194 & < 10.0.22350.0; >= 10.0.22621.0 & < 10.0.25054.0. Please update your Visual Studio build tools and try again.
I bet you that someone just needs to add this to the store validation config >=10.0.26100.1 & < 10.0.27000.0;
Has someone already tried contacting Partner Center support about this? I feel like this might be nothing than a configuration issue on their end like @under3415 suggested.
This being an ongoing issue for almost 4 months with barely any feedback is becoming a bit of a nuisance.
I think I finally fixed this. I got rid of all the package references to Microsoft.WindowsAppSDK and Microsoft.Windows.SDK.BuildTools in all my .csproj files. That is, I deleted this line wherever I found it:
<PackageReference Include="Microsoft.Windows.SDK.BuildTools" Version="10.0.22621.3233" />
IMPORTANT NOTE: You need to do this to all the packages you consume as well. I had a package of WinUI resources (controls, formatters, etc.), that was still referencing the SDK.BuildTools. It wasn't until I removed the ALL the references in every package that I imported that I was able to successfully upload to the Microsoft Partner Center with the latest version of everything.
