Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Google Play In-app Billing API version is less than 3

I just started beta testing the 2.0 update to the billing library for the Play Store and a lot of my users are getting this error Google Play In-app Billing API version is less than 3.

Is this just a matter of time before they update or are some devices stuck on older versions or what?

like image 287
casolorz Avatar asked Jun 06 '19 14:06

casolorz


People also ask

What does it mean Google Play In-App Billing API version is less than 3?

Usually the BILLING_UNAVAILABLE error means that your Android device is running an unsupported version of Android or Play services. Other things to check when you get this error: Are you logged in to the correct Google Account on the device/emulator? Try logging out and logging back in.

What is in-app billing API?

The In-app Billing Version 3 API makes it easier for you to integrate In-app Billing into your applications. The features in this version include improved synchronous purchase flow, APIs to let you easily track ownership of consumable goods, and local caching of in-app purchase data.

What is Google Play in-app billing?

Google Play's billing system is a service that enables you to sell digital products and content in your Android app. You can use Google Play's billing system to sell a one-time product or subscriptions on a recurring basis.


3 Answers

I started seeing this error when using the Emulator without logging into Google Play.
Once I logged into Google Play with my account the error went away.

like image 137
ElegyD Avatar answered Oct 21 '22 19:10

ElegyD


In-app Billing API version goes with the Google Play Store and v3 is actually quite old (at least 3 years old)

PBL will check user's client version and will return this error message if their devices have a very old Play Store installed on their devices. If you're migrating from AIDL to PBL and you didn't check client's billing API version before, you could end up with seeing users reporting this issue.

You shouldn't expect this error message if you're upgrading from PBL 1.x to 2.0 because PBL 1.x is newer than v3 and it will also do this check. You may want to file a bug to the Google team in this case.

like image 39
DrPower Avatar answered Oct 21 '22 19:10

DrPower


It was normal, because at that moment it is not connected to any Google account.

So make sure you have an emulator with Google Play services.

-> Go to Google Play and enter your account credentials. After you close and reopen the app.

like image 43
AlexPad Avatar answered Oct 21 '22 18:10

AlexPad