-
-
Notifications
You must be signed in to change notification settings - Fork 155
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Purchasing UWP add-ons of type subscription not supported? #297
Comments
I am having the same challenge. Am I missing something? This is the code |
FYI - I have my subscription configured in the Microsoft store as "Available for purchase from within the parent product only.". Do I need to change the store connection type to InAppPurchase instead of Subscription? |
I tried switching both to InAppPurchase and still the purchase object comes back null. |
@gceaser I ended up not using this library for UWP purchases and made my own implementation. |
@sjorsmiltenburg assuming you got it all working, could you look at my stack overflow post about the native implementation and the problems I am having. Any suggestions you could offer would be appreciated.. https://stackoverflow.com/questions/63308359/subscription-add-ons-for-uwp-app-are-not-found |
Closing for #388 |
Bug Information
Version Number of Plugin: 3.0.0-beta
Device Tested On: windows
Simulator Tested On: -
Version of VS: 16.6.0
Version of Xamarin: 16.6.000.1055
Steps to reproduce the Behavior
When purchasing a published add-on of type subscription i keep getting
"Choose another item, This in-app purchase item is no longer available in {appname}"
When reading the docs (https://docs.microsoft.com/en-us/windows/uwp/monetize/in-app-purchases-and-trials) it says that add-ons of type subscription have the requirement to use the 'newer' Windows.Services.Store namespace.
Note To use subscription add-ons, your app must target Windows 10 Anniversary Edition (10.0; Build 14393) or a later release in Visual Studio, and it must use the Windows.Services.Store namespace instead of the Windows.ApplicationModel.Store namespace.
When browsing throuth the sources of this plugin I found that it still seems to use the 'old' Windows.ApplicationModel.Store namespace. Therefore I conclude that using this plugin for this type of add-on is not supported.
Is this correct?
Are there plans to move to the new namespace?
The text was updated successfully, but these errors were encountered: