Repository navigation
|
How can a team catch Play Billing Library below version 8 automatically before a build goes to review? |
Replies: 1 comment
|
The quick check. Run this from the project root and read what it prints. grep -rnoE 'com\.android\.billingclient:billing(-ktx)?:[0-9]+' --include='*.gradle' --include='*.kts' . # major must be 8 or higher from 31 Aug 2026Read the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as What the hit means. A com.android.billingclient:billing dependency with a major version below 8. New apps and updates must use Play Billing Library 8 or later from 31 August 2026 (deprecation ladder), with a Play Console extension available until 1 November 2026. Already published v7 binaries keep transacting until the 2027 all-apps deadline. The fix. Upgrade to com.android.billingclient:billing 8.x, or request the Play Console extension before 1 November 2026. Reference https://developer.android.com/google/play/billing/deprecation-faq Recipe source. data/detection-recipes.json This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run |
The quick check. Run this from the project root and read what it prints.
Read the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as
GOOGLE-PLAY-BILLING-V8-REQUIREDwith a coverage line and a proper exit code.What the hit means. A com.android.billingclient:billing dependency with a major version below 8. New apps and updates must use Play Billing Library 8 or later from …