StoreProduct.RequestPurchaseAsync fail to purchase when Run as Administrator

[oden3d]

Describe the bug

Call StoreProduct.RequestPurchaseAsync to purchase Addons just always return NotPurchased when WinUI3 app run as Administrator.

So user can not purchase any Addon in WinUI3 app when run as Administrator.
Any workaround on this critical block issue?

Steps to reproduce the bug

1. Create WinUI3 project to use StoreProduct.RequestPurchaseAsync
2. Run as Administrator and try to purchase.
3. Store popup will blink for a second then return NotPurchased status.

Expected behavior

User able to purchase Addons when WinUI3 app run as Administrator.

Screenshots

No response

NuGet package version

Windows App SDK 1.6.3: 1.6.250108002

Packaging type

Packaged (MSIX)

Windows version

Windows 11 version 24H2 (22621, October 2024 Update)

IDE

Visual Studio 2022

Additional context

No response

[bogdan-patraucean]

I have the same issue. Other APIs from the StoreContext suffer from the same limitation. When our apps are based on elevated operations, we basically can't monitize as intended. That's really stupid. From my understanding this is how the store API is designed.

[mominshaikhdevs]

Can you run this API as Admin in an unpackaged app? (can you even call this API in MediumIL, as you currently can in packaged app, in an unpackaged app!)

If no, then this class of APIs issues: "works only in "MSIX + Medium IL + LowIL/partialTrust/AppContainer/win32-app-isolation repo)"" ultimately boils down to "APIs being closedly tightened with MSIX Vertualizations". So, once again, this would be a MSIX Issue.(or, how other runtimes like .NET handle MSIX).

related:

1. AppContainer for Win32 apps #219.

2. Touch events stop working in a WPF packaged app after using ApplicationData.Current #5167.

3. Trying to use a FileOpenPicker while running the app as Administrator will crash the app #2504.

4. Improved StorageFile APIs #8.

5. [MSIX] Provide Public API for launching App Execution Aliases over both WinRM and SSH. #5258.

[ssparach]

Thanks for the question! The API is external to the WindowsAppSDK. For any issues related to it, please file a report via Feedback Hub.

[bogdan-patraucean]

It might get fixed in a future Windows update. A team works on the issue as I reported it to them directly. No updates yet, but it's confirmed they are working on it internally.