Windows.ApplicationModel.Store.CurrentAppSimulator.RequestProductPurchaseAsync() no longer works

Hong 1,046

The following code used to work:

Windows.ApplicationModel.Store.PurchaseResults pr = await Windows.ApplicationModel.Store.CurrentAppSimulator.RequestProductPurchaseAsync(_ud.sInAppTokenName);

It no longer shows a window. Instead, it returns immediately with
pr.Status == Windows.ApplicationModel.Store.ProductPurchaseStatus.NotPurchased

Both the targe and min versions of the UWP app are 18362. Could anyone shed some light on this?

Roy Li - MSFT 31,551 Reputation points Microsoft Vendor

2019-12-23T03:08:40.627+00:00

According to the document: CurrentAppSimulator.RequestProductPurchaseAsync Method, the method should show the UI for purchasing. Is the product ID that you want to purchase valid? Does the WindowsStoreProxy.xml that is used by CurrentAppSimulator contain the requested product? Could you please confirm this first?
Hong 1,046 Reputation points

2019-12-24T02:51:15.97+00:00

Thank you for trying to help.
This is not a new app. The app including its IAP has been working for quite a few years. I had not tested the simulator for a while.
Yes, WindowsStoreProxy.xml modified from the sample has the requested product.
This is the case for two apps that I have tested.
Roy Li - MSFT 31,551 Reputation points Microsoft Vendor

2019-12-24T07:16:29.17+00:00

Not sure why the API shows such behavior if you had double-checked the requested product in the WindowsStoreProxy.xml. Your app is running a device with build 18362, right? If you change the min version to lower and run your app in a lower version. Will this happen again?

Another thing I have to say is that APIs from Windows.ApplicationModel.Store Namespace is no longer updated. And it is recommended to use APIs from Windows.Services.Store Namespace if your app targets Windows 10 Anniversary Edition (10.0; Build 14393) or a later release.
Hong 1,046 Reputation points

2019-12-24T13:31:13.623+00:00

I looked into the newer API, but could not find any equivalent of the CurrentAppSimulator. How can test IAP functions without bothering the store?
I will try to find an earlier Windows 10 build to test if possible.
Roy Li - MSFT 31,551 Reputation points Microsoft Vendor

2019-12-25T01:46:15.3+00:00

Different from Windows.ApplicationModel.Store Namespace, the new APIs don't have a simulator mechanism to test. If you are using the new API and you want to test about it, you will need to add the test add-ons in the dev center first. Then you could directly purchase this add-on in your app. It means you will go through the real purchase process but the add-on is just a test add-on.
Hong 1,046 Reputation points

2019-12-25T06:00:42.577+00:00

I have checked all the PCs that I can put my hand on, and all of them run 18362. I will have to give up on this. Thank you again for all the help.
Roy Li - MSFT 31,551 Reputation points Microsoft Vendor

2019-12-25T06:55:47.06+00:00

If you have other questions about In-app purchase, please feel free to contact us.