Guide · 8 min read
Google Play Billing Library 7 Enforcement: What Happens After the November 2026 Deadline
The November 1, 2026 extension deadline for Google Play Billing Library v7 enforcement has passed. If your Android app still depends on Billing Library versions 5, 6, or 7 without an active extension, you can't publish a new app or submit updates to the Play Store right now. Here is what that actually means for revenue, what the migration path looks like, and what the next enforcement cycle — Billing Library v8, August 2027 — requires you to do before the same problem repeats.
What enforcement means: a publishing gate, not a runtime shutdown
Google's Billing Library enforcement is a publishing restriction, not a kill switch on running apps. Apps already live on the Play Store using a deprecated Billing Library version continue running: existing users can still make purchases, subscriptions keep renewing, and revenue keeps flowing. What you've lost is the ability to publish a new app or submit any update to an existing app that includes the blocked library version.
For most developers, this distinction matters a lot. It means you're not in a user-visible emergency — nobody is seeing failed purchases right now. But every day you can't ship an update is a day you can't fix bugs, respond to crashes, or deploy security patches. The publishing gate is the emergency, even if it's invisible to users.
The block is applied per submitted binary. An old build with Billing Library v6 that was live before the enforcement date remains downloadable by users who already installed it. A new build attempting to include v6 will fail Play Console policy validation at upload time and cannot be submitted. This is consistent with how Android API level enforcement works — the same mechanism that required apps to target API 36 by August 31, 2026.
Google Play Billing Library v7 enforcement timeline: 3 dates that matter
Google's deprecation schedule for the Play Billing Library had three inflection points in 2026. The first enforcement date was August 31, 2026 — after that date, any new app submission or app update that declared Billing Library v5, v6, or any earlier unsupported version was rejected at upload. Version 7 was the minimum floor; v8 also satisfied the requirement.
Developers who couldn't complete migration by August 31 could request a time-limited extension through the Play Console's policy compliance section. The extension request window closed November 1, 2026. Extensions, where granted, were temporary — not a permanent exception. If your app received an extension and that window is now expiring, your deadline is whatever date appeared in your Play Console policy status, not a fixed date that applies to everyone.
The next version in the enforcement cycle is Billing Library v8, with a last-date-for-new-and-updated-apps deadline of August 31, 2027. If your migration plan ends at v7, you will be in the same position in nine months. The correct target now is v8 — migrating directly to v8.0.0 satisfies the current enforcement requirement and clears you through August 2027 without an intermediate step.
How to find which Billing Library version your app declares
In a Gradle-based Android project, search your app/build.gradle or app/build.gradle.kts for com.android.billingclient:billing. The dependency line looks like: implementation 'com.android.billingclient:billing:7.1.1'. If you're using the version catalog format (libs.versions.toml), look for the version key your billing dependency references — the value is the library version. Version 8.0.0 or any later 8.x release satisfies the current requirement.
Apps built with Unity or other cross-platform engines have a less obvious version footprint. The billing library version is embedded inside a third-party package, not your top-level Gradle file. In Unity, search the Assets/Plugins/Android folder for any .aar file with 'billing' in the filename. In React Native, the billing version lives inside the native module's android/build.gradle. In Godot, the Play Billing plugin bundles its own billing AAR. Play Console evaluates the actual version inside the submitted App Bundle, not what you declared at the top level.
If you're using RevenueCat, Adapty, or another subscription SDK, the SDK's own release notes will state which Billing Library version the current native module targets. RevenueCat's SDK 7.x and later wraps Billing Library 8; earlier versions may not. Cross-check the SDK version in your Gradle file against the SDK's changelog to confirm the billing version it bundles — the SDK is what you control, and it controls the billing version.
3-step migration from Billing Library v7 to v8
Step 1: update the dependency. In app/build.gradle, change the billing dependency to com.android.billingclient:billing:8.0.0 (or the latest 8.x version). If you use billing-ktx for Kotlin coroutine support, update that version line too. Run a Gradle sync immediately — the build will surface any removed APIs that require code changes before you get to testing.
Step 2: address the two most common breaking changes. The first is the PendingPurchasesParams requirement: enablePendingPurchases() on BillingClient.Builder now requires you to pass a PendingPurchasesParams object instead of calling it with no arguments. Update that initialization call. The second affects apps supporting API 21 or 22: Billing Library v8.1.0 raises the minSdkVersion to 23. If you haven't dropped support for those API levels, pin your dependency to exactly 8.0.0 until you're ready to bump minSdk.
Step 3: test the full billing flow end to end. Use Google Play's test environment via license testing or the billing sandbox, not production. Test initial subscription purchase, upgrade and downgrade between tiers, cancellation and re-subscribe, and pending purchase acknowledgment. The 3-day acknowledgment window still applies — purchases not acknowledged within 72 hours are automatically reversed, so confirm your acknowledgment call fires correctly in every purchase completion path.
If you missed the extension window: the only path forward
The extension request window closed November 1, 2026. No new extension applications are accepted. If your app is currently blocked, the only path to publishing again is completing the migration to Billing Library v8 and submitting a compliant build. There is no workaround, no appeal form for the extension, and no temporary pass available through Google Play support — enforcement means rejection at upload, not a delay.
For apps where the migration requires significant refactoring — custom billing implementations, homegrown subscription management, or deeply integrated billing flows — the fastest path to unblocking is usually a targeted update: replace only the Billing Library dependency and the initialization code that broke, ship a compliant build, and schedule the fuller refactor for the next sprint. A minimal-change update that satisfies the enforcement check is better than a comprehensive migration that takes another three weeks.
One parallel compliance issue worth auditing at the same time: if your app received a publisher account action related to billing policy, resolve that separately from the library version block. Policy actions and library enforcement are distinct systems in Play Console. A clean v8 migration can be submitted and approved for publishing while a separate policy issue is under review — they don't block each other unless Play Console specifically says so.
Billing Library v8 and the August 2027 enforcement cycle
Billing Library v8 is the current required version — but it also becomes the blocked version starting August 31, 2027. The deprecation cycle is now predictable enough to treat as a planning constant: Google typically announces the next version's requirement 12–18 months ahead of enforcement, releases a stable version at least six months before the deadline, and maintains the same two-tier structure (new apps → app updates → extension → hard cutoff). If Billing Library v9 follows the same schedule, watch for a stable release in early 2027.
Apps supporting API 21 or 22 devices face an additional constraint: Billing Library v8.1.0 raises the minSdkVersion to 23, so those apps must stay pinned to 8.0.0 for now. Dropping API 21/22 support is a separate product decision — check your Android Vitals dashboard in Play Console for your user base's Android version distribution before committing to a minSdk bump.
The Google Play billing commission changes from 2026 — reduced fees and third-party payment processing options — are separate from the library enforcement issue but affect the same billing infrastructure. If your app implemented external payment links or reduced-commission billing, verify that the payment integration layer is also compatible with the v8 billing client before shipping your compliance update.
Unity, React Native, and Flutter apps: the most common compliance failure point
Cross-platform framework apps generate the majority of Billing Library enforcement complaints, because the library version is controlled by a third-party package that the developer doesn't update directly. When Unity IAP or a subscription SDK is out of date, the billing version it bundles is the version that fails Play Console validation — even if your top-level Gradle file looks correct.
For Unity: Unity IAP 5.x is required for Billing Library 8 compatibility. IAP 4.x maxes out at Billing Library 7. When upgrading to IAP 5.x, add an explicit override in your Custom Main Gradle Template to prevent IAP from pulling in an older version transitively: configurations.all { resolutionStrategy { force 'com.android.billingclient:billing:8.0.0' } }. For React Native apps, check whether your in-app purchase library's current release targets Billing Library 8 — most major RN billing libraries released their v8-compatible builds in mid-2026.
For Flutter apps using the in_app_purchase package, the CHANGELOG lists which Billing Library version each release targets — verify before submitting. For Godot, the Play Billing plugin publishes a separate update when it vendors a new billing AAR; check the plugin's GitHub releases rather than relying on the Godot asset library to surface a newer version automatically. When your app is unblocked and can ship again, make sure your Play Store listing assets are ready for the update — the Play Store feature graphic and screenshots are the first thing users see when you push your compliance update.
The migration path is clear — the window to plan is not
Both the August 31 and November 1, 2026 enforcement dates have passed. If your app is blocked, the fastest fix is a targeted migration to Billing Library v8.0.0, addressing the PendingPurchasesParams breaking change, and testing the full purchase flow before submission. The August 2027 v8 enforcement date is already on the calendar — build in a quarterly dependency audit cycle now so the next version transition happens on your schedule, not Google's.
Once your compliance update is in production, review your Play Store listing while you have momentum — check your store listing against the latest screenshot size requirements, refresh release notes, and verify your feature graphic is ready for the traffic your update will bring.
Preview your Play Store assets in the editor →
Frequently asked questions
google play billing library deadline november 2026 — what does it mean?
November 1, 2026 was the deadline to request an extension for apps still using Billing Library v7 or older. After that date, no new extension requests are accepted. Apps that weren't migrated or granted an extension can't publish new apps or submit app updates to Google Play. Existing installs on users' devices keep running — the enforcement is a publishing gate, not a runtime shutdown.
which billing library versions does google play block after november 2026?
As of November 2026, Google Play blocks app submissions that include Billing Library v7 and all earlier versions (v5, v6, and older) for new apps and app updates. The current required version is v8.x. Billing Library v8 itself will become a blocked version for new app and update submissions on August 31, 2027.
my unity game uses unity iap — do i need to update for billing library enforcement?
Yes. Unity IAP 4.x bundles Billing Library 7, which is now blocked from Play Store submissions. Upgrade to Unity IAP 5.x (which targets Billing Library 8) and override the billing dependency version in your Custom Main Gradle Template to prevent IAP from pulling in an older version transitively.
can i still request a google play billing library extension after november 2026?
No. The extension request window closed November 1, 2026. No new extensions are available. The only path to publishing is completing the migration to Billing Library v8.0.0 and submitting a compliant build to Play Console.
what is the billing library v8 enforcement deadline?
Billing Library v8 becomes the blocked version for new app and update submissions on August 31, 2027. Apps already live on the Play Store using v8 continue running after that date, but no new app or app update submissions that include v8 or earlier will be accepted. The expected required version at that point is v9.