Play Billing 6.0.1 error on Console PlayStore

[SkilyFrance]

Hello,
After updated to purchases_flutter: ^9.9.1, Google PlayStore blocked my new .aab by saying
"Your app currently uses the AIDL version of the Play Billing library, but version 6.0.1 or later is required to take advantage of the latest monetization features on Google Play."

Do you have any idea about a way to fix it ?

EDIT : I have forced by passing implementation 'com.android.billingclient:billing:6.2.1' in build.gradle but still wait for another fix.

Thanks

[RCGitBot]

👀 We've just linked this issue to our internal tracker and notified the team. Thank you for reporting, we're checking this out!

[vegaro]

purchases_flutter 9.9.1 uses Google Play Billing v8, so you shouldn't need to add that to your build.gradle

implementation 'com.android.billingclient:billing:6.2.1'

Do you by any chance have other in app purchases plugin in your project that's using the old Play Billing library AIDL? Maybe an old version of in_app_purchase? If you're not sure, can you please share your dependencies with us so we can confirm what could be causing this?

Thank you

[SkilyFrance]

No, I also clean all caches to be sure. For sure, my dependencies here

  intl: ^0.20.2
  flutter_bloc: ^9.1.1
  firebase_auth: ^6.1.1
  cloud_firestore: ^6.0.3
  firebase_core: ^4.2.0
  firebase_storage: ^13.0.3
  firebase_ai: ^3.4.0
  firebase_analytics: ^12.0.3
  logger: ^2.6.2
  local_auth: ^3.0.0
  onesignal_flutter: ^5.3.4
  flutter_dotenv: ^6.0.0
  encrypt: ^5.0.3
  flutter_secure_storage: ^9.2.4
  camerawesome: ^2.5.0
  image: ^4.5.4
  share_plus: ^12.0.1
  path_provider: ^2.1.5
  package_info_plus: ^9.0.0
  mailto: ^2.0.0
  url_launcher: ^6.3.2
  image_gallery_saver_plus: ^4.0.1
  permission_handler: ^12.0.1
  in_app_review: ^2.0.11
  device_info_plus: ^12.2.0
  purchases_flutter: ^9.9.1
  audioplayers: ^6.5.1
  page_transition: ^2.2.1
  pressable_flutter: ^1.0.4
  flutter_animate: ^4.5.2
  app_settings: ^6.1.1
  native_dialog_plus: ^1.1.0
  flutter_native_splash: ^2.4.7
  phone_form_field: ^10.0.12
  pinput: ^5.0.2
  widget_zoom: ^0.0.4
  custom_refresh_indicator: ^4.0.1

[vegaro]

Thank you for sending that over. Yes, it doesn't look like any of those libraries brings the AIDL... Maybe this is a false positive by Google checks?

Do you by any chance have the following in the AndroidManifest.xml?:

<uses-permission android:name="com.android.vending.BILLING" />

I see some folks online getting their app blocked because of that, and the billing client version we use should add the correct permissions automatically.

[vegaro]

Apart from that, just to make sure this is not the case, if your project is an old project that was using AIDL before, make sure you don't have an IInAppBillingService.aidl in your project

app/src/main/aidl/com/android/vending/billing/IInAppBillingService.aidl

Again, I suspect this is not a real case of usage of AIDL, but Google incorrectly detecting it

[SkilyFrance]

Yes, I have added the following <uses-permission android:name="com.android.vending.BILLING" />.
But I had never been blocked before. I have to remove it when using last versionpurchases_flutter: ^9.9.1 ?

[vegaro]

Nothing in particular has changed in 9.9.1 that would require that to be removed. But in any case, you don't need that in your AndroidManifest.xml.

Can you try removing it and see if it passes Google checks?

Thank you

[vegaro]

@SkilyFrance did you try my suggestion?

Checking if we can close this issue

[SkilyFrance]

Hi @vegaro ,
Don't have app/src/main/aidl/com/android/vending/billing/IInAppBillingService.aidl

I have removed <uses-permission android:name="com.android.vending.BILLING" /> from my Manifest.

There is some proguard rules to provide in my project ?
Because now I get this issue this PlatformException(channel-error, Unable to establish connection on channel: "dev.flutter.pigeon.firebase_core_platform_interface.FirebaseCoreHostApi.initializeCore"., null, null).

After searching for 3 days, some packages may conflict with Firebase.

Do you have an explanation ?

[vegaro]

Proguard rules should be automatically included by our plugin. Did removing <uses-permission android:name="com.android.vending.BILLING" /> fix the issue that you reported in the original post? The issue you were getting of "Your app currently uses the AIDL version of the Play Billing library, but version 6.0.1 or later is required to take advantage of the latest monetization features on Google Play."

I don't understand if you are saying you started to get Unable to establish connection on channel after removing the BILLING permission. Can you please clarify?

Thank you