Partner Center reporting a bug for latest version of BuildTools #4480

DRAirey1 · 2024-06-07T12:14:50Z

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

myokeeh · 2024-06-13T05:42:54Z

Seeing this too

myokeeh · 2024-06-13T05:59:22Z

To clarify, the app I tried submitted is a UWP app. I think the Partner Center isn't ready for 10.0.26100 yet.

shyamshr93 · 2024-06-14T18:26:58Z

facing the same issue. any update on this ?

gagansuie · 2024-06-17T04:43:32Z

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" />

Armorost · 2024-06-19T13:35:34Z

uninstall "Microsoft.Windows.SDK.BuildTools" from the app Packages seems to remove the pb to me

ritesh3103 · 2024-06-27T06:08:55Z

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.

jbe2277 · 2024-07-12T07:15:56Z

Any updates regarding this issue?

microsoft/WindowsAppSDK#4480

Rarisma · 2024-07-12T19:38:55Z

I am experiencing this too.

zhuxb711 · 2024-07-24T08:26:54Z

Same here. Only way to solve this is downgrade the BuildTools.

MartinZikmund · 2024-08-04T16:16:19Z

Also just hit this problem, but have no workaround, as some of my dependencies already bumped to latest stable as well

matthewacme · 2024-08-14T13:10:14Z

Aug 14th and I'm still seeing this

IsmailHassani · 2024-08-15T08:06:18Z

Same here

Sevael · 2024-09-04T07:26:29Z

:( Same here

SolidRockProgrammer · 2024-09-17T08:28:07Z

Same here, we can't deploy our latest version UNO app, and we can't down grade.

MartinZikmund · 2024-09-17T12:03:09Z

@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

PIN0L33KZ · 2024-09-17T22:47:35Z

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.

MartinZikmund · 2024-09-19T19:25:27Z

CC @Sergio0694 @dpaulino - do you have a point of contact for this at Partner Center team that could help please?

Sergio0694 · 2024-09-19T19:29:42Z

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).

under3415 · 2024-09-19T22:15:58Z

myokeeh has pinged ankur06 in microsoft-store Discord channel 👍

KevinLaMS · 2024-09-20T00:17:00Z

Hey, @DRAirey1 I am newly joining the team and will take a look at this? Thanks!

BrianDT · 2024-09-20T15:33:25Z

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.

DCorrBECare · 2024-09-25T14:06:36Z

Is there any news regarding this problem?

myokeeh · 2024-09-25T15:40:30Z

@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?

IsmailHassani · 2024-09-25T21:42:18Z

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.

matthewacme · 2024-09-25T21:56:16Z

@IsmailHassani

unfortunately we are not using Azure Devops (we are using GitHub tools) so that's not an option for us

under3415 · 2024-09-26T08:02:27Z

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.

IsmailHassani · 2024-09-26T08:27:48Z

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.

under3415 · 2024-09-26T08:47:48Z

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;

marwalsch · 2024-09-26T15:18:02Z

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.

DRAirey1 · 2024-09-27T16:38:18Z

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.

matthewacme · 2024-09-27T16:45:31Z

@DRAirey1
Hey David,

I'm successfully submitting a WinUI app with

<TargetFramework>net8.0-windows10.0.22621.0</TargetFramework>
<TargetPlatformMinVersion>10.0.19044.0</TargetPlatformMinVersion>

and

<PackageReference Include="Microsoft.WindowsAppSDK" Version="1.5.240802000" />
<PackageReference Include="Microsoft.Windows.SDK.BuildTools" Version="10.0.22621.3233" />

in all the packages.

Any upgrade from those libraries however and I get the "not supported" error.

I'm using 1.5.240802000 for the WAS and you are 1.5.240428000 for your WAS

I don't know if that is any help to you.

myokeeh · 2024-10-01T19:37:08Z

@KevinLaMS I made another attempt to submit for version 26100 thinking this would be fixed now that 24H2 is GA. No luck.

IsmailHassani · 2024-10-02T10:07:22Z

@KevinLaMS I made another attempt to submit for version 26100 thinking this would be fixed now that 24H2 is GA. No luck.

I'm wondering what the issue could be. Any chance you can share your csproj file and the pipeline yaml file?

under3415 · 2024-10-02T10:21:34Z

The issue seems quite simple. When store validates the package, it does not recognize the new SDK. Probably just needs a config update, but this is very low on Microsoft backlog. Get Outlook for Android<https://aka.ms/AAb9ysg>

…

________________________________ From: Ismail Hassani ***@***.***> Sent: Wednesday, October 2, 2024 11:07:46 PM To: microsoft/WindowsAppSDK ***@***.***> Cc: under3415 ***@***.***>; Mention ***@***.***> Subject: Re: [microsoft/WindowsAppSDK] Partner Center reporting a bug for latest version of BuildTools (Issue #4480) @KevinLaMS<https://github.com/KevinLaMS> I made another attempt to submit for version 26100 thinking this would be fixed now that 24H2 is GA. No luck. I'm wondering what the issue could be. Any chance you can share your csproj file and the pipeline yaml file? — Reply to this email directly, view it on GitHub<#4480 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AA5N3HWYVMWREBKWPMYOMPLZZPAXFAVCNFSM6AAAAABI6RUFFOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBYGIZTANRYHA>. You are receiving this because you were mentioned.Message ID: ***@***.***>

myokeeh · 2024-10-02T16:53:57Z

I agree with @under3415. It's on the Partner Center side. What's frustrating is this is not the first time this happened. I don't know why the lesson hasn't been learned. Almost every time there's a new SDK version, they fumble here.

under3415 · 2024-10-04T23:31:18Z

Someone needs to tell them this is affecting AI and it will get fixed in 10 minutes :-D

microsoft-github-policy-service bot added the needs-triage label Jun 7, 2024

codendone added area-DeveloperTools Issues related to authoring (source and IDL), debugging, HotReload, LiveVisualTree, VS integration and removed needs-triage labels Jun 27, 2024

jbe2277 added a commit to jbe2277/musicmanager that referenced this issue Jul 12, 2024

Downgrade SDK.BuildTools because of MS Partner Center issue

9275497

microsoft/WindowsAppSDK#4480

Rarisma mentioned this issue Jul 12, 2024

downgrade buildtools storybuilder-org/StoryCAD#763

Merged

MartinZikmund mentioned this issue Aug 26, 2024

[Epic] Opened Microsoft issues tracking unoplatform/uno#982

Open

Lamparter mentioned this issue Aug 29, 2024

General Updates 20 0x5bfa/FluentHub#486

Draft

Partner Center reporting a bug for latest version of BuildTools #4480

Partner Center reporting a bug for latest version of BuildTools #4480

Comments

DRAirey1 commented Jun 7, 2024

Describe the bug

Steps to reproduce the bug

Expected behavior

Screenshots

NuGet package version

Packaging type

Windows version

IDE

Additional context

myokeeh commented Jun 13, 2024

myokeeh commented Jun 13, 2024

shyamshr93 commented Jun 14, 2024

gagansuie commented Jun 17, 2024

Armorost commented Jun 19, 2024

ritesh3103 commented Jun 27, 2024

jbe2277 commented Jul 12, 2024

Rarisma commented Jul 12, 2024

zhuxb711 commented Jul 24, 2024

MartinZikmund commented Aug 4, 2024

matthewacme commented Aug 14, 2024

IsmailHassani commented Aug 15, 2024

Sevael commented Sep 4, 2024

SolidRockProgrammer commented Sep 17, 2024

MartinZikmund commented Sep 17, 2024

PIN0L33KZ commented Sep 17, 2024

MartinZikmund commented Sep 19, 2024

Sergio0694 commented Sep 19, 2024 • edited Loading

under3415 commented Sep 19, 2024

KevinLaMS commented Sep 20, 2024

BrianDT commented Sep 20, 2024

DCorrBECare commented Sep 25, 2024

myokeeh commented Sep 25, 2024

IsmailHassani commented Sep 25, 2024

matthewacme commented Sep 25, 2024

under3415 commented Sep 26, 2024

IsmailHassani commented Sep 26, 2024 • edited Loading

under3415 commented Sep 26, 2024 • edited Loading

marwalsch commented Sep 26, 2024 • edited Loading

DRAirey1 commented Sep 27, 2024 • edited Loading

matthewacme commented Sep 27, 2024

myokeeh commented Oct 1, 2024

IsmailHassani commented Oct 2, 2024

under3415 commented Oct 2, 2024 via email

myokeeh commented Oct 2, 2024

under3415 commented Oct 4, 2024

Sergio0694 commented Sep 19, 2024 •

edited

Loading

IsmailHassani commented Sep 26, 2024 •

edited

Loading

under3415 commented Sep 26, 2024 •

edited

Loading

marwalsch commented Sep 26, 2024 •

edited

Loading

DRAirey1 commented Sep 27, 2024 •

edited

Loading