You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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):
Note
I have fix ready, need approval for my branch and Pull Request
The text was updated successfully, but these errors were encountered: