Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Too many bind requests(999+) for service Intent #641

Open
thevinhhuynh opened this issue Sep 30, 2023 · 10 comments
Open

Too many bind requests(999+) for service Intent #641

thevinhhuynh opened this issue Sep 30, 2023 · 10 comments

Comments

@thevinhhuynh
Copy link

thevinhhuynh commented Sep 30, 2023

I'm using BILLING: 6.0.0, I encountered the above error. The devices are mainly Samsung

Exception java.lang.IllegalStateException: Too many bind requests(999+) for service Intent { act=com.android.vending.billing.InAppBillingService.BIND pkg=com.android.vending cmp=com.android.vending/com.google.android.finsky.billing.iab.InAppBillingService (has extras) }
at android.app.ContextImpl.bindServiceCommon (ContextImpl.java:2115)
at android.app.ContextImpl.bindService (ContextImpl.java:2024)
at android.content.ContextWrapper.bindService (ContextWrapper.java:870)
at com.android.billingclient.api.BillingClientImpl.startConnection (com.android.billingclient:billing@@6.0.0:64)
at sdk.platform.android.inapppurchase.InAppPurchaseUtils.connectToGooglePlayBilling (InAppPurchaseUtils.java:83)
at sdk.platform.android.inapppurchase.InAppPurchaseUtils$2.onBillingServiceDisconnected (InAppPurchaseUtils.java:87)
at com.android.billingclient.api.zzaf.onServiceDisconnected (com.android.billingclient:billing@@6.0.0:5)
at android.app.LoadedApk$ServiceDispatcher.doDeath (LoadedApk.java:2368)
at android.app.LoadedApk$ServiceDispatcher$RunConnection.run (LoadedApk.java:2383)
at android.os.Handler.handleCallback (Handler.java:942)
at android.os.Handler.dispatchMessage (Handler.java:99)
at android.os.Looper.loopOnce (Looper.java:226)
at android.os.Looper.loop (Looper.java:313)
at android.app.ActivityThread.main (ActivityThread.java:8757)
at java.lang.reflect.Method.invoke
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:571)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1067)

Help me!

@leCandas
Copy link

leCandas commented Oct 2, 2023

Exactly same issue with some Samsung devices with billing 6.0.1

Fatal Exception: java.lang.IllegalStateException: Too many bind requests(999+) for service Intent { act=com.android.vending.billing.InAppBillingService.BIND pkg=com.android.vending cmp=com.android.vending/com.google.android.finsky.billing.iab.InAppBillingService (has extras) }
at android.app.ContextImpl.bindServiceCommon(ContextImpl.java:2115)
at android.app.ContextImpl.bindService(ContextImpl.java:2024)
at android.content.ContextWrapper.bindService(ContextWrapper.java:870)
at com.android.billingclient.api.BillingClientImpl.startConnection(com.android.billingclient:billing@@6.0.1:64)

@Zachary625
Copy link

same here with PBL 5.0.0 this seems to be Samsung Android 13 bug but still hope we can get some insights

@JRWilding
Copy link

100% Samsung on Android 13 (from an app with 10m+ installs)

@leCandas
Copy link

I had the same issue, only coming from Samsung devices.

Since I want to address this quickly.
I have surrounded the billingClient.startConnection(this); with a try catch block.
When I get an exception I just end the connection billingClient.endConnection(); billingClient = null;
And posting a delayed call to a handler to re-initilize the billingClient.

This approach will at least address the crash.

@kolagit
Copy link

kolagit commented Oct 25, 2023

Same issue using PBL 5.0!
Any updates???

@congdanh1608
Copy link

congdanh1608 commented Nov 14, 2023

Any updates?
I don't know why I got many crashes from one app, but others did not.
I tried to downgrade the in-app billing SDK version, but it is not working.

@npkhung92
Copy link

I am also using billingclient version 6.0.1 and faced the same issue. Is there any updates on this?

@ErickSorto
Copy link

I am having the same issue.

@igorwojda
Copy link

Workaround - make sure that billingClient.startConnection() is called only when app is in foreground

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants