Skip to content
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

Problem with fovea validator #1550

Open
yiannis-spyridakis opened this issue Mar 22, 2024 · 0 comments
Open

Problem with fovea validator #1550

yiannis-spyridakis opened this issue Mar 22, 2024 · 0 comments

Comments

@yiannis-spyridakis
Copy link

yiannis-spyridakis commented Mar 22, 2024

Observed behavior

I am working on a project that uses the paid version of the fovea validator of the form:

https://validator.fovea.cc/v1/validate?appName=APP_NAME&apiKey=API_KEY

We are currently integrating v13.x of the plugin and I have tested Android/Google Playstore for the time being. The problem is that in case of successful validation the success payload is returned with an empty .collection (VerifiedPurchase[]).
This causes CdvPurchase.Product.owned to always return false (even for owned products) because CdvPurchase.Store.verifiedPurchases remains unpopulated.

A custom/dummy validator function that populates the collection with {id, purchaseDate, isExpired} fixes the issue.

Expected behavior

I don't know if it is an issue with the fovea validator or it is expected. In the later case should CdvPurchase.Product.owned use a different check? e.g. check for acknowledged transactions with the product?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant