WinUI 2.6.X/2.7.X cause the submission to MSStore failure with error code 1201 (Only in Windows Application Packaging Project with FullTrustProcess)

[zhuxb711]

Describe the bug
Failed to submit the package to Microsoft Store if an UWP App is Windows Application Packaging Project with fullTrustProcess.
Once you submit your package. Microsoft Store will report "Attention needed" after a few minutes. Error code is 1201

Someone report the same issue here

Steps to reproduce the bug

1. Create a Windows Application Packaging Project with UWP project and .Net Framework project
2. Install WinUI 2.6.X or WinUI 2.7.0preview
3. Publish and submit to MSStore

Expected behavior
Pass the certification and should not report 1201

Screenshots

Version Info
Encountered issue in:
[Microsoft.UI.Xaml 2.6.1]
[Microsoft.UI.Xaml 2.6.2]
[Microsoft.UI.Xaml 2.7.0-preview]

Disappear in:
[Microsoft.UI.Xaml 2.5.0]

Windows app type:

UWP	Win32
Yes

Windows version	Saw the problem?
Insider Build (xxxxx)
May 2021 Update (19043)	Yes
October 2020 Update (19042)	Yes
May 2020 Update (19041)
November 2019 Update (18363)
May 2019 Update (18362)
October 2018 Update (17763)
April 2018 Update (17134)
Fall Creators Update (16299)
Creators Update (15063)

Device form factor	Saw the problem?
Desktop	Yes
Xbox
Surface Hub
IoT

Additional context
None

[asklar]

@jevansaks @ranjeshj FYI

[zhuxb711]

I think it's a critical issue. I have to downgrade to 2.5 and give up all the effort I made for 2.6. Please investigate this issue ASAP. Thanks.

[yaira2]

We're having this same issue with Files and it's forced us to drop support for ARM in our upcoming major release v2.

[gus33000]

@yaichenbaum I wonder if this wouldn't be due to the fact Windows 10 on ARM does not have an ARM64 .NET framework available, only x86 (and for Windows 11 you do get x64 .NET framework instead). I wouldn't expect the .NET framework app to work here.

[zhuxb711]

@chingucoding @ranjeshj @michael-hawker Could help take a look at this issue? I have tested X64 only package and it fails again. @gus33000

[yaira2]

@dpaulino can you see if your having this issue with Nightingale?

[zhuxb711]

@yaichenbaum Have you test it in your project?

[yaira2]

@yaichenbaum Have you test it in your project?

Files was just approved (x64, x86)...

[zhuxb711]

@yaichenbaum Have you test it in your project?

Files was just approved (x64, x86)...

That is really wired

[zhuxb711]

I test it and here is the result:
WinUI 2.5 All -> Worked
WinUI 2.6.2 X64 only Version 1 Style -> Worked
WinUI 2.6.2 X64 only Version 2 Style -> Error 1201
WinUI 2.6.2 X64|ARM Version 1 Style -> Error 1201
WinUI 2.6.2 X64|ARM Version 2 Style -> Error 1201

[riverar]

@StephenLPeters @gabbybilka Can you help route this?

[myokeeh]

Why can't the Partner Center team ever stay ahead of these so it's never a problem?

[AathifMahir]

Noticing same issue on WinUI 2.6.2, without Arm64 binary, i can successfully publish to store.

The workaround for now is drop the support for Arm64 and include all other instructions sets X86, X64, Arm

[zhuxb711]

Noticing same issue on WinUI 2.6.2, without Arm64 binary, i can successfully publish to store.

The workaround for now is drop the support for Arm64 and include all other instructions sets X86, X64, Arm

It seems that I could not pass the validation even drop the support for Arm64

[crramirez]

Just a reminder. Windows 11 ships in about 3 weeks, and our applications are not ready to take advantage of the new styles. Users will see beautiful Settings and an ugly Raft WSL and Files (among others). Would you mind increasing the priority of this?

I don't have the luxury to skip the ARM64 version of my app.

[zhuxb711]

Issue still exists in 2.7.0

[zhuxb711]

From microsoft store support:

Please create .NET Native repro following steps here:
https://github.com/dotnet/core/blob/main/Documentation/ilcRepro.md#creating-and-sending-a-net-native-repro and please
send that repro to dotnetnative@microsoft.com. They can assist you with this issue.

I could not create the ilcRepro because VS will throw some exception when compiling if I added

<NetNativeReproPath>C:\myReproDirectory</NetNativeReproPath>

[StephenLPeters]

@zhuxb711 do you have a repro project handy that you can share with the team?

[crramirez]

I can confirm that I've been using the 2.7.1 preview in production in the Microsoft Store without issues for about one month. For me it is a good candidate for release.

[gus33000]

Is there any news about this issue? It will soon be 4 months this bug affects all stable versions of the WinUI 2 nuget package. Probably a few people are still running into this, lack information about the latest prerelease fixing this (or are not able to use prerelease bits due to policy) or are most likely throwing away potential new arm64 native apps because of this issue impacting the state of the ARM64 platform.

[crramirez]

We are still running into this but we could use the prerelease version with the store, it is behaving well, so we kept going. Looking forward for the stable version

[ghost]

🎉This issue was addressed in #6063, which has now been successfully released as Microsoft.UI.Xaml v2.7.1.:tada:

Handy links:

• Release Notes
• Official Nuget Release

[StephenLPeters]

@crramirez @gus33000 check out the new 2.7.1 stable release patch, which includes this fix (as well as a couple others).

[crramirez]

@crramirez @gus33000 check out the new 2.7.1 stable release patch, which includes this fix (as well as a couple others).

Hello @StephenLPeters ,

I have been working with the 2.7.1 prerelease without any problem. I'll test with the stable release and will back to you.

Thank you

[crramirez]

Hello @StephenLPeters,

Tested with 2.7.1 stable and everything is ok.

Regards,
Carlos

[gus33000]

@crramirez @gus33000 check out the new 2.7.1 stable release patch, which includes this fix (as well as a couple others).

Hello, can also confirm it's fully fixed on my side! Thanks a lot!

[ghost]

🎉This issue was addressed in #6063, which has now been successfully released as Microsoft.UI.Xaml v2.8.0-prerelease.220413001.:tada:

Handy links:

• Release Notes
• Official Nuget Release

[ghost]

🎉This issue was addressed in #6063, which has now been successfully released as Microsoft.UI.Xaml v2.8.0-prerelease.220712001.:tada:

Handy links:

• Release Notes
• Official Nuget Release

[ghost]

🎉This issue was addressed in #6063, which has now been successfully released as Microsoft.UI.Xaml v2.8.0.:tada:

Handy links:

• Release Notes
• Official Nuget Release