Solved

Flutter: Reply already submitted

  • 23 September 2021
  • 2 replies
  • 118 views

Badge +3

Anyone had this crash?

 

Fatal Exception: java.lang.IllegalStateException: Reply already submitted
       at io.flutter.embedding.engine.dart.DartMessenger$Reply.reply(DartMessenger.java:164)
       at io.flutter.plugin.common.MethodChannel$IncomingMethodCallHandler$1.success(MethodChannel.java:238)
       at com.revenuecat.purchases_flutter.PurchasesFlutterPlugin$5.onReceived(PurchasesFlutterPlugin.java:584)
       at com.revenuecat.purchases.hybridcommon.CommonKt$restoreTransactions$2.invoke(common.kt:187)
       at com.revenuecat.purchases.hybridcommon.CommonKt$restoreTransactions$2.invoke(common.kt)
       at com.revenuecat.purchases.ListenerConversionsKt$receivePurchaserInfoListener$1.onReceived(listenerConversions.kt:127)
       at com.revenuecat.purchases.Purchases$retrievePurchaseInfo$1.invoke(Purchases.kt:846)
       at com.revenuecat.purchases.Purchases$retrievePurchaseInfo$1.invoke(Purchases.kt:98)
       at com.revenuecat.purchases.PurchasesKt$sam$java_lang_Runnable$0.run(Purchases.kt)
       at android.os.Handler.handleCallback(Handler.java:739)
       at android.os.Handler.dispatchMessage(Handler.java:95)
       at android.os.Looper.loop(Looper.java:148)
       at android.app.ActivityThread.main(ActivityThread.java:7325)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1230)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1120)

icon

Best answer by Maddie 1 October 2021, 20:08

View original

2 replies

Userlevel 3
Badge +8

Thanks for the crash report! Did you open this related GitHub issue for this crash? Our mobile engineers are looking into it and it would be helpful to know if you opened that issue. Mentioning @Maddie to keep her in the loop.

Hey @Meu Cronograma Capilar, we have some updates on the GitHub issue if you’re interested! 

TLDR -- there is a bug in Google’s BillingClient that results in the listener being called twice. We’ve filed an issue with them and are working on a patch in the meantime. Feel free to follow the GitHub issue for further updates! 

Reply