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

Comments Location Regressed #682

Closed
jonathansampson opened this issue Aug 8, 2024 · 0 comments · Fixed by #683
Closed

Comments Location Regressed #682

jonathansampson opened this issue Aug 8, 2024 · 0 comments · Fixed by #683

Comments

@jonathansampson
Copy link
Contributor

jonathansampson commented Aug 8, 2024

This issue has regressed. @jbigman, comments are now in ds:9 again. Perhaps the extractor should check both ds:8 and ds:9 (one being a fallback if the other doesn't contain comments). Thoughts?

Originally posted by @jonathansampson in #603 (comment)

jonathansampson added a commit to jonathansampson/google-play-scraper that referenced this issue Aug 8, 2024
jonathansampson added a commit to jonathansampson/google-play-scraper that referenced this issue Aug 8, 2024
fixes facundoolano#682

Revert "dynamically resolves comments path"

This reverts commit 5f0546b.

Improves comment extraction

Comments may be found in either ds:8 or ds:9 paths. This approach will check for expected fields in both paths before determine which path houses the comments themselves.
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

Successfully merging a pull request may close this issue.

1 participant