[FREE] 💰 In App Billing V8.3.0 - Integrate In App Purchases In Your Apps

Extensions
,
43

New Update

  • Billing SDK Upgraded to v8.3.0
  • Minor bug fixes

Download: In App Billing - AD Extensions

2 Likes
44

Vous pensez que celle que j’ai ne fonctionne pas ??

45

bonjour , j’ai tĂ©lĂ©chargĂ© la version 8.3.0 mise Ă  jour et j’ai toujours le mĂȘme problĂšme : quand je clique sur mon bouton “premium” ça ne fait rien, alors que je voudrais que l’utilisateur soit dirigĂ© vers google play pour s’abonner.

voici mes blocs

Capture d’écran 2
Capture d’écran 2989×514 73.6 KB

Capture d’écran 3
Capture d’écran 3910×478 43.1 KB

Capture d’écran 4
Capture d’écran 4522×284 26.6 KB

Pouvez m’aider ? merci

46
  1. Put your app into closed/internal testing on PlayStore
  2. Upload your .aab file on PlayStore
  3. Download the app from the link of closed/internal testing
  4. This would make it work.
47

oui c’est ce que j’ai fais : j’ai tĂ©lĂ©chargĂ© le fichier .aab sur play store, j’ai envoyĂ© le lien par mail (celui qui se trouve dans le test interne) et j’ai tĂ©lĂ©chargĂ© l’application.

48

use this
image
in place of this

image
image736×199 57.7 KB

also correct way of launching the subscription purchase

image
image1127×196 22.6 KB

49

J’ai simplifiĂ© et corrigĂ© mes blocs

Capture d’écran 5
Capture d’écran 5953×480 60.4 KB

et quand je clique sur le buttonPremium ça n’ouvre toujours pas la fenĂȘtre googlePlay, savez vous quel est le problĂšme ?

50

Je crois que j’ai un curieux problĂšme, je vous montre quand mĂȘme qu’au niveau googlePlayStore mon abonnement est configurĂ© comme actif. Et mon “buttonPremium” ne veut pas ouvrir la fenĂȘtre GooglePlay pour que l’utilisateur puisse s’abonner !

J’ai testĂ© le butonPremium autrement (c’est Ă  dire juste en ouvrant un arrangementVertical et ça fonctionne), donc ce n’ai pas un problĂšme au niveau du bouton.

j’avais joint mes blocs plus haut

Capture d’écran 6
Capture d’écran 61326×255 28.1 KB

J’ai bien tĂ©tĂ©chargĂ© .aab pour le test interne

Capture d’écran 7
Capture d’écran 71048×199 12.9 KB

Est ce que quelqu’un a dĂ©jĂ  eu ce problĂšme ? Merci pour votre aide

51

j’ai oubliĂ© de dire que j’ai essayĂ© ça aussi et ça ne fonctionne pas !

Capture d’écran 8
Capture d’écran 8860×394 26.5 KB

52

I love this extension but it only works for those in playstore. i was thinking of creating extension that works with local transaction like (MPESA). If anyone has done STK PUSH contact we try together, i have daraja ready

53

Rebonjour, ça y est j’ai trouvĂ© mon problĂšme. C’était un soucis avec Google play store, les blocs Ă©taient corrects. DĂ©solĂ© de vous avoir dĂ©rangĂ© mais je dĂ©sespĂšrais , Merci

54

InAppBilling "Product list is empty" — appears after adding any additional extension, unrelated to which one

App: PhotoLog (published, real subscriptions active and confirmed live in Play Console) Extension in question: in.akshatdeveloper.InAppBilling v1 Symptom: GoogleInAppBilling.Error fires with message "Product list is empty" when querying real, live subscription products (photolog_monthly, photolog_annual_subscription) that are confirmed Active in Play Console → Monetize → Subscriptions.

What triggers it

The original, unmodified app has run this exact billing flow (sign in → PhotoCaptureScreen.Initialize → StartConnection() → GetSubscription()) with no issue at all. After adding new extensions to the project for an unrelated feature, the same flow now fails every time, on every compiled build, on the same device, same account.

What I've ruled out through testing (compiled APK, not Companion)

  1. Not a specific-extension conflict. Tested single extensions in isolation, added one at a time to the real app package: RYimagepicker alone, TaifunExif alone — both independently reproduce the error. Two completely unrelated extensions, from different developers, each sufficient on their own. This rules out a conflict between two specific libraries.

  2. Not about GPS/location permission timing, despite the error consistently appearing right after the GPS permission dialog. Confirmed by: (a) denying location instead of granting it — same error either way; (b) sitting on the screen for 2 minutes without responding to the permission dialog at all — no error appears until the dialog is dismissed one way or the other, suggesting the Notifier alert is simply queued behind the system dialog and not actually caused by it.

  3. Not a dropped/interrupted billing connection. Added a guarded one-time reconnect (StartConnection() called again after first location fix) — no change in behavior, and confirmed the reconnect itself succeeds (visible from a doubling of error dialogs when the original connection also completes cleanly).

  4. Not extra permissions from specific extensions — tested TaifunFile+TaifunExif (file/EXIF, minimal permissions) vs RYimagepicker+SAF (image/storage access) as separate pairs; both reproduce identically.

  5. Not missing/misconfigured products. Confirmed directly in Play Console: both subscription products exist, are Active, with the exact product IDs the code queries.

  6. Not extra diagnostic info hiding elsewhere. Wired up dialogs for ConnectionFailed, FailedToGetSubscription, QueryPurchasesFailed, and SubscriptionPurchaseFailedToLaunch (previously unhandled/silent events) — none of them ever fire. Only the generic Error event fires, always with the same message, no additional response code surfaces anywhere.

  7. Removed 3 confirmed-unused legacy extensions (present in the project but referenced by zero components/blocks anywhere) to reduce total extension count — did not resolve it.

Current extension list (15 total after removing the 3 unused ones)

TaifunExif, TaifunFile, TaifunImage, TaifunScreenshot, TaifunZip, RYimagepicker, SAF, FileTools, ImageConvertor, Base64Convertor, KIO4_TransportNet, minSdk21, InAppBilling, LogWatcher — plus the app's own components.

Leading theory

Given the symptom appears with any single additional extension regardless of vendor/type, and disappears with none of the four new ones present, I suspect this may be related to crossing some kind of build threshold (possibly multidex) that changes how the compiled app resolves/loads Play Billing's library at runtime — rather than a conflict between specific extension code. I don't have visibility into the actual compiled manifest or dex layout to confirm this.

What I'm hoping to learn

  • Is this a known interaction between InAppBilling and multidex builds (or some other build-time threshold)?

  • Is there a way to check whether a locally-compiled .apk from App Inventor's build server went multidex, without decompiling it myself?

  • Has anyone else seen InAppBilling queries return genuinely empty despite confirmed-live Play Console products, tied to overall app/extension size rather than a specific extension?

Happy to share the .aia or specific block screenshots if useful.

55

Possibly the extension is out of date, other current extensions are targeting 9.1.* requirements...

We have not heard from @AkshatRana since May 2026

:red_question_mark:

You have your own AppInventor built from sources ?

56

While using any Play Billing extension make sure app's package name is exactly the same which is published on Google Play. If you're testing the apk built directly without being published the app on internal testing and installing from Google Play then you can query the products and it will show you live active in-app products and subscriptions but if using method Purchase it will give an error.

If apk build is failing due to class conflicts then make sure you're not using another extension which has similar classes.

57

v.8.** will work till Aug 2027, v.9.** till Aug 2028 [As per 2 year (from the date library released) deprecation rule].