Google Play: Billing Library 8
New apps and updates must use Play Billing Library 8 or later since 31 August 2026, with an extension to 1 November 2026.
What does Google Play require?
Since 31 August 2026, every new app and every update that uses Google Play Billing must carry Billing Library version 8 or later. Play Console shows a warning on apps still on an older version, and from its details page under Policy status you can request an extension until 1 November 2026. Apps that are not updated keep working: the rule applies to what you publish.
Where it comes from in a Flutter app
In a Flutter app the Billing Library comes from in_app_purchase_android, the Android side of in_app_purchase, or from an SDK such as RevenueCat. in_app_purchase_android moved to Billing 8 in version 0.5.0, and in_app_purchase took it up only in 3.3.0. An app on in_app_purchase 3.2.x stays on Billing 7 after flutter pub upgrade, because 3.2.x depends on in_app_purchase_android ^0.4.0, which does not include 0.5.0. Both new versions need Flutter 3.38 or newer. RevenueCat's purchases_flutter uses Billing 8 from version 9.0.0.
How to fix it
- Run the free build check on the .apk or .aab. It reads the Billing Library version the build actually carries.
- Upgrade Flutter to 3.38 or newer, then set
in_app_purchase: ^3.3.0in pubspec.yaml. - Replace any call to
queryPurchaseHistorywithqueryPurchases: Billing 8 removed it. - With RevenueCat, use
purchases_flutter9.0.0 or newer. - If you cannot ship in time, request the extension from the warning under Policy status in Play Console.
The free build check reads your .apk or .aab in the browser and shows whether this applies to your build, without uploading anything.
Or have the whole build checked: the store readiness audit is €190, 2 working days.