I’ve tried to add subscriptions to my App and wanted to get the Purchases but it just doesn’t work. There is no error, the billing is connected and the app is in internal testing on Google Play Console. Even trying to get a subscription detail just does nothing.
Are you using the Error event blocks to see if you are getting any error messages?
Yes I used every error block in the AppBilling into a Message Notifier but nothing.
I’ve uploaded the App to Google Play as Closed-Test (Alpha), created the subscription vip.boost and added all Error Block avaible. Nothing happens. The Loading-Label changes, so I know that the producure is running.
Used the Free Extension from Sumit before, that worked until Niotron added the Component and I get a compiling error for two colliding libaries.
Can you send me the apk or the aia for testing.
Still no updates on this. I used an extension for InGame Billing before, but that throws me an Error. Using the inbuilt component, just does nothing.
As I needed to update my games, all of them are now unable to access Google Subscription Services.
Loosing a lot of money.
can you show us proper example how it work ? I try other extension also dont support Niotron.
4 month of silence. I lost so much money, if this isn’t fixed soon, I need to find a alternative to this Builder.
Can’t you not just roll back, so we can use the extensions again? Or at least give us a Tutorial on how to use the Niotron InAppComponent.
1 Like
For a quick fix, I’d suggest this extension:
What is the difference between this and any other InApp Billing Extension? I’ve tried every single one and it throw an error. Does yours still work on Niotron?
Currently, 10+ users are using this extension in Niotron without any issues.
If it dont work, is there money back guaranty ? And what is niotron doing, why we are paying them , to buy extra extension, ?? @abhijith
I try to build extension of inapp billing but , niotron dont support as ( may be java above 7 dont support by niotron ) and sdk above 4 dont support, 
Why Billing v8 cannot run in Niotron?
| Billing Version | Status in Niotron |
|---|---|
| v2 / v3 / v4 | Fully Supported |
| v5 |  NOT supported (requires Java 8) |
| v6 | NOT supported |
| v7 | NOT supported |
| v8 | NOT supported |
Niotron is built on Android API 29, Java 7, Gradle 4.x, so it cannot load Billing v8 classes.
ProductDetails)
NOT supported in Niotron
Requires Java 8
Requires AAR bundling
You already saw errors:
-
QueryProductDetailsParamsmissing -
getProducts()missing
So cannot work in Niotron, 3.0 billing works.
Current Java Version in 2025
Java™ SE Development Kit 24, 24.0.2 Release Notes
As of 2025, Java 25 is the latest long-term support (LTS) release, scheduled for September 2025. It introduces numerous enhancements across the language, APIs, and runtime, making it a significant update for developers. However, Java 24 (version 24.0.2) is also actively maintained, with its latest update released in July 2025.
Niotron Stuck In Java 7
Niotron supports Java 8, I think the Niotron IDE doesn’t support Java 8 yet. We’re hopeful that Niotron will update it soon.
You might try the new FAST-CLI to develop your extensions. I’ve built my in-app-billing extension with it and it’s working perfectly.
I have create 1 extension I will launch it soon , it is working.
But service connection disconnected issue
Issue is in my code or in play consol, or may be i have to make my app live in playstore to test, cant understand .
2 Likes
there is some thing that i dint understand ?? Or some thing that is not clear?
Elaborate your issues.
I did two test : 1 ) with my extension in Niotron , 2 ) Kodular with kodula in app billing ,
test1 with my extension :
error I receive when try to buy subscription, Connection was success , inappbilling connected with my extension.
Test 2 with kodular:
to understand the issue more deeply, i try with kodular, i here also no connection issue, when i try to call sub id :
I receive data but I receive this issue,
The extension i use for kodular :
For more information, In google play consol, i create Subscription id / base plan also, and upload aab file in ( same project ) in internal testing. So i cant understand what i miss.