Windows App Runtime 1.2 store installation and side-loaded packages conflict

[BenJKuhn]

Describe the bug

The store and side-load packages of the Windows App Runtime 1.2 have different phone identities, causing installation of either to fail if the other is already installed. This was reported on Twitter here: https://twitter.com/dotMorten/status/1594737193666215937

I was also able to confirm the issue & repro.

Steps to reproduce the bug

Install an app from the store that uses Windows App Runtime 1.2 package (e.g. WinUI 3 Gallery), then try to install Windows App SDK using the standalone installer.

Expected behavior

Installs cleanly in either case, or does nothing if already installed.

Screenshots

No response

NuGet package version

Windows App SDK 1.2.1: 1.2.221116.1

Packaging type

Packaged (MSIX), Unpackaged

Windows version

Windows 11 version 22H2 (22621, 2022 Update)

IDE

No response

Additional context

No response

[roxk]

This had happened before: #1953 (comment)

Anyway to setup a test to catch this before rolling out a release? The test would install the stored-signed package and then install using installer.exe. Rollout should be blocked unless test succeeds.

[MikeHillberg]

Internal tracking http://task.ms/42339525

[MikeHillberg]

@dotMorten, how are you installing when you see this? Using the Store? Using the WindowsAppRuntimeInstall.exe from the download center?

[dotMorten]

@MikeHillberg Installing? I'm just pressing F5 in Visual Studio.
I do think the WinUI 3 Gallery was installed via the store which is likely what it was conflicting with.

[bpulliam]

🎉Microsoft.WindowsAppSDK.1.2.221209.1 has been released which fixes this issue.

Handy links:

Release Notes
Official Nuget Release