After using In-App- Billing extension

Discuss
1

App got crash please look into this issue.

2

I’ve also noticed the same bug, most of the in-app-billing extensions are crashing after the last update.

Captured logs:

2025-05-08 17:56:08.254 4434 4434 com.niotron.jewelshikderjony.BillingTest E AndroidRuntime : FATAL EXCEPTION: main
Process: com.niotron.jewelshikderjony.BillingTest, PID: 4434
java.lang.IndexOutOfBoundsException: Index 0 out of bounds for length 0
 at jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:64)
 at jdk.internal.util.Preconditions.outOfBoundsCheckIndex(Preconditions.java:70)
 at jdk.internal.util.Preconditions.checkIndex(Preconditions.java:266)
 at java.util.Objects.checkIndex(Objects.java:359)
 at java.util.ArrayList.get(ArrayList.java:434)
 at com.jewel.googleplaybilling.o0.run(SourceFile:217)
 at android.os.Handler.handleCallback(Unknown Source:2)
 at android.os.Handler.dispatchMessage(Unknown Source:4)
 at android.os.Looper.loopOnce(Unknown Source:185)
 at android.os.Looper.loop(Unknown Source:83)
 at android.app.ActivityThread.main(Unknown Source:107)
 at java.lang.reflect.Method.invoke(Native Method)
 at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(Unknown Source:11)
 at com.android.internal.os.ZygoteInit.main(Unknown Source:334)

It’s probably indicating that the issue is from this class: com.jewel.googleplaybilling.o0.run(SourceFile:217), but there is no such class in the extension.

However, I was able to resolve the issue.

3

is it happening in niotron only?

4

why not use billing from component noitron?

5

Now its working fine thankyou for fixing it

1 Like