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

In-App Range inconsistencies #80

Open
michalRajcan opened this issue Jan 13, 2021 · 0 comments
Open

In-App Range inconsistencies #80

michalRajcan opened this issue Jan 13, 2021 · 0 comments
Labels

Comments

@michalRajcan
Copy link

Describe the bug
Some apps contain only one value in In-App Purchase section (e.g. com.codium.bmicalculator).
Current functionality does not correctly parse (and store) the iap_range tuple while requesting app details.

At the same time, if Interactive Elements contains element with dash ("-") in name, iap_range returns the Interactive Elements list as well.

To Reproduce
incorrectly shown iap_range tuple: play_scraper.details('com.codium.bmicalculator')
or any other app with single In-App Purchase

Interactive Elemnts list in iap_range: play_scraper.details('com.LightBeam.Demolish')

Expected behavior
Function should return tuple containing the single In-App Purchase value in both places.

Desktop (please complete the following information):

  • OS: macOS (does not matter though, happens also on another OSs)
  • Python Version 3.7.7
  • play_scraper Version 0.6.0

Note
I have fix ready, need approval for my branch and Pull Request

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

No branches or pull requests

1 participant