-
Notifications
You must be signed in to change notification settings - Fork 8
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
Crash reports #71
Comments
thanks @timeshift-ted for sharing the logs here. And also, will try to replicate the same issue in our example app and update it. |
Hi,
Can you please give me instructions on "add the test account of google play
store"?
Ted Johnson
Timeshift Media, Inc.
…On Fri, Sep 8, 2023 at 3:35 AM Amutha C ***@***.***> wrote:
thanks @timeshift-ted <https://github.com/timeshift-ted> for sharing the
logs here.
As per the crash analytics logs, we could see the issue is while fetching
the products from google store and unfortunately the app was unable to
connect with google play billing service.
Could you please add the test account of google play store and try again.
Thanks.
And also, will try to replicate the same issue in our example app and
update it.
—
Reply to this email directly, view it on GitHub
<#71 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANUMDSQ2TZOTEWSGQGNCGY3XZLYFJANCNFSM6AAAAAA4PEDMDM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Hi @cb-amutha , we have 120 reports of the same error since going live 1 month ago. Also through Crashlytics. What causes the failure to connect to Google Play services here? |
We also have this issue, but it's unclear why. I have a suspicion it's caused by the new default proguard rules in combination with a perhaps swallowed error, but I have no proof. |
Here are stacktraces: production via Crashlytics
Interestingly, the underlying error message is this:
in debug modeHere, I opened the app, then logged into the Play Store on the emulator (might have called some callback in your sdk) and then resurfaced the app.
This suggests missing proguard rules.
|
Issue is also reproducible in v0.3.0... this is affecting our production users who can't do purchases, please fix this asap. |
Here are reproduction steps:
Basically, closing the Play Store crashes the app if it's in the background. If it's in the foreground, nothing happens. |
Thanks for the steps to reproduce @ciriousjoker |
@cb-haripriyan Any news? |
We have identified the underlying case which was causing the multiple call backs. The Billing Library calls the listeners multiple times during disconnection/reconnection, which in turns causes multiple callbacks on Flutter. We are working on a method to avoid this. |
@cb-haripriyan Any eta for this? This is severely affecting our users. |
@ciriousjoker We are targeting this for early next week. |
@cb-haripriyan Do you have an update on this? This issue produces almost 300 crashes per week on Android |
@ciriousjoker We are expecting to release a fix by utmost tomorrow. |
@ciriousjoker @timeshift-ted |
Will try out asap, we'll probably have meaningful crash reporting statistics by the end of next week. |
@cb-haripriyan This doesn't seem to happen nearly as often anymore as this one, but apparently it still exists in Stacktrace
Perhaps this happens if a user signs into or out of the Play Store while the app is running? |
@ciriousjoker Missed updating it here. The version v1.0.0-beta.4 includes the fix for this. |
The fix solved the issue, this can probably be closed for now and reopened if it occurs again |
Crashlytics is reporting this crash is happening regularly:
Fatal Exception: java.lang.IllegalStateException
Reply already submitted
io.flutter.embedding.engine.dart.DartMessenger$Reply.reply (DartMessenger.java:435)
io.flutter.plugin.common.MethodChannel$IncomingMethodCallHandler$1.error (MethodChannel.java:268)
com.chargebee.flutter.sdk.ChargebeeFlutterSdkPlugin.error (ChargebeeFlutterSdkPlugin.kt:530)
com.chargebee.flutter.sdk.ChargebeeFlutterSdkPlugin.onError (ChargebeeFlutterSdkPlugin.kt:511)
com.chargebee.flutter.sdk.ChargebeeFlutterSdkPlugin.access$onError (ChargebeeFlutterSdkPlugin.kt:26)
com.chargebee.flutter.sdk.ChargebeeFlutterSdkPlugin$retrieveProducts$1.onError (ChargebeeFlutterSdkPlugin.kt:159)
com.chargebee.android.billingservice.BillingClientManager$retrieveProducts$2.invoke (BillingClientManager.kt:51)
com.chargebee.android.billingservice.BillingClientManager$retrieveProducts$2.invoke (BillingClientManager.kt:21)
com.chargebee.android.billingservice.BillingClientManager$retrieveProducts$3.invoke (BillingClientManager.kt:69)
com.chargebee.android.billingservice.BillingClientManager$retrieveProducts$3.invoke (BillingClientManager.kt:21)
com.chargebee.android.billingservice.BillingClientManager$createBillingClientStateListener$1.onBillingServiceDisconnected (BillingClientManager.kt:504)
com.android.billingclient.api.zzaf.onServiceDisconnected (com.android.billingclient:billing@@4.0.0:4)
android.app.LoadedApk$ServiceDispatcher.doDeath (LoadedApk.java:1967)
android.app.LoadedApk$ServiceDispatcher$RunConnection.run (LoadedApk.java:1982)
android.os.Handler.handleCallback (Handler.java:883)
android.os.Handler.dispatchMessage (Handler.java:100)
android.os.Looper.loop (Looper.java:214)
android.app.ActivityThread.main (ActivityThread.java:7356)
java.lang.reflect.Method.invoke (Method.java)
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:492)
com.android.internal.os.ZygoteInit.main (ZygoteInit.java:930)
The text was updated successfully, but these errors were encountered: