# Changelog of Google Play Scraper - Rankings, Reviews & App Details (`haketa/google-play-scraper`) Actor

- **URL**: https://apify.com/haketa/google-play-scraper/changelog.md
- **Full Actor documentation**: https://apify.com/haketa/google-play-scraper.md

## Changelog

### 1.1.0 — 2026-11-01

- **Verified a fresh production run**: pulled the live **US Top Free** chart (`rankings` mode, `fullDetail: true`) and captured **200 ranked apps** — Google Play's full server-side ceiling for an overall chart — in **~141 s** with **0 duplicates** and **100% coverage** on every core field (`appId`, `title`, `url`, `rank`, `score`, `developer`, `installs`) plus the full enrichment set (`description`, `histogram`, `ratings`, `reviews`, `developerEmail`, `IAPRange`, `contentRating`, `version`, `released`, screenshots).
- **Verified uncapped review pagination**: a second run collected **400 reviews** for a single app across multiple cursor pages with **0 duplicate `reviewId`s** and 100% coverage on `score`, `text`, `date`, `thumbsUp`, and `userName` — confirming the "no artificial review cap" behavior.
- **Corrected the per-chart ranking ceiling in the docs**: Google Play's `list` RPC returns up to **~200 apps per chart** for the overall Top Free/Paid/Grossing charts (confirmed across two chart/category probes), so the README and input hints now state **~200** instead of the earlier **~660**. No behavior change — the actor already requests the maximum and returns exactly what Google serves.
- **Refreshed the README** to the gold standard: the Output example and field-reference table now mirror the exact fresh-run records, the Pagination & scale section reflects the real 200-app chart ceiling and uncapped reviews, and keyword density, FAQ, and related-scraper links were tightened.
- No changes to input fields, output field names, or scraping logic — a healthy actor kept accurate and current.
