All packsPlay Billing MachinerySolve
google play billing library 8 skudetails removed migration
The APIs v8 deleted are the ones training data has seen the most
SkuDetails, querySkuDetailsAsync, SkuType and the no-argument enablePendingPurchases() were all removed in Billing Library 8 -- and are heavily represented in training data precisely because they were correct for years (decision 12).
This is one of the things Play Billing Machinery already handles. Sell subscriptions in your Android app on the Billing Library version Google requires from 31 August 2026.
Is this you?
Code written against SkuDetails, SkuDetailsParams, querySkuDetailsAsync, BillingClient.SkuType, queryPurchaseHistoryAsync, or the no-argument enablePendingPurchases() doesn't compile against Billing Library 8+ at all -- every one of these was removed, not deprecated-but-working, and each has a direct replacement (ProductDetails, QueryProductDetailsParams, queryProductDetailsAsync, BillingClient.ProductType, and a PendingPurchasesParams-typed call).
Why this one is easy to get wrong
These APIs were correct and current for years before v8 removed them, which means they're heavily represented in any model's training data relative to the newer replacements -- an agent writing "idiomatic" Play Billing code from memory reaches for exactly the surface Google deleted, with total confidence, because that's what most of the indexed examples still show.
What you get instead
The pack pins the current Billing Library 9 shape throughout and greps the built repo for the removed names as a build-time check, so a v6/v7 ghost fails fast rather than shipping. It also documents the inverse trap: acknowledgePurchase, consumeAsync, and the singular getOneTimePurchaseOfferDetails() are commonly mis-reported as removed when they're not -- and ProductDetailsResponseListener.onProductDetailsResponse now receives a QueryProductDetailsResult object, not a bare List, which is a compile error rather than a silent bug.
Source: ARCHITECTURE.md decision 12 — checkable in the pack you receive
How you actually use this
You don’t install a library or wire up an SDK. Your own coding agent builds the code in your project, and you keep it — no runtime dependency on us.
Step 1
Download and unzip
You get a folder: the docs that tell an agent what to build, a starting skeleton, and the test suite that decides when it's done.
Step 2
Open it in Claude Code or Cursor
Point your coding agent at the folder. Nothing to install, no account with us, no API key.
Step 3
Paste one prompt
The pack contains the exact prompt. Paste it as your first message and leave it alone — it works through the build itself, choosing a cheaper or stronger model per task.
Step 4
Run ./verify.sh
One command. It prints a pass or fail for every check. Green means the build is done — the same script we ran to produce the receipt on this page.
Typical build: about 33 minutes of your agent working, mostly unattended. Then you integrate the working module into your app the way you would any code you’d written yourself.
Why you can believe this
3 of 3 runs passedWe ran this pack from an empty folder 3 times and published exactly what happened — every check, the model, the token cost, the wall time. Not a testimonial, and not our opinion: the same verify.sh you run yourself. Read the full receipt →