!!! 活页夹交易失败！！！（包裹大小 = 624）。调用 .verifyPhoneNumber() 方法时 IGmsServiceBroker.getService 失败

Question

当我调用方法时，我收到此错误。verifyPhoneNumber()我的手机身份验证代码没有任何问题，因为在我更改捆绑 ID 并重新下载文件之前它工作得很好google-service.json。自从我更改了捆绑包 id 并更改了 google-service.json 以来，我的项目变得一团糟。我不知道该怎么做，因为我是编码新手，并且不知道这个堆栈跟踪在说什么。

在 ios 中，应用程序被杀死并且根本不留下任何堆栈跟踪。在android中，我得到了这个堆栈跟踪。

我尝试过的操作： flutter clean、flutter pub get、flutter pub cache Repair 删除了 build 文件夹、.gradle 文件夹、podfile.lock 和 pods 文件夹，然后运行 ​​flutter run -v 重新创建文件夹，但没有修复问题。

任何帮助将不胜感激。如果需要，我可以显示更多详细信息。

E/JavaBinder(12658): !!! FAILED BINDER TRANSACTION !!!  (parcel size = 624)
W/GmsClient(12658): IGmsServiceBroker.getService failed
W/GmsClient(12658): android.os.DeadObjectException: Transaction failed on small parcel; remote process probably died, but this could also be caused by running out of binder buffe
W/GmsClient(12658):     at android.os.BinderProxy.transactNative(Native Method)
W/GmsClient(12658):     at android.os.BinderProxy.transact(BinderProxy.java:584)
W/GmsClient(12658):     at com.google.android.gms.common.internal.zzac.getService(com.google.android.gms:play-services-basement@@18.1.0:8)
W/GmsClient(12658):     at com.google.android.gms.common.internal.BaseGmsClient.getRemoteService(com.google.android.gms:play-services-basement@@18.1.0:14)
W/GmsClient(12658):     at com.google.android.gms.common.api.internal.zabt.run(com.google.android.gms:play-services-base@@18.0.1:7)
W/GmsClient(12658):     at android.os.Handler.handleCallback(Handler.java:942)
W/GmsClient(12658):     at android.os.Handler.dispatchMessage(Handler.java:99)
W/GmsClient(12658):     at android.os.Looper.loopOnce(Looper.java:201)
W/GmsClient(12658):     at android.os.Looper.loop(Looper.java:288)
W/GmsClient(12658):     at android.os.HandlerThread.run(HandlerThread.java:67)
E/JavaBinder(12658): !!! FAILED BINDER TRANSACTION !!!  (parcel size = 624)
W/GmsClient(12658): IGmsServiceBroker.getService failed
W/GmsClient(12658): android.os.DeadObjectException: Transaction failed on small parcel; remote process probably died, but this could also be caused by running out of binder buffe
W/GmsClient(12658):     at android.os.BinderProxy.transactNative(Native Method)
W/GmsClient(12658):     at android.os.BinderProxy.transact(BinderProxy.java:584)
W/GmsClient(12658):     at com.google.android.gms.common.internal.zzac.getService(com.google.android.gms:play-services-basement@@18.1.0:8)
W/GmsClient(12658):     at com.google.android.gms.common.internal.BaseGmsClient.getRemoteService(com.google.android.gms:play-services-basement@@18.1.0:14)
W/GmsClient(12658):     at com.google.android.gms.common.api.internal.zabt.run(com.google.android.gms:play-services-base@@18.0.1:7)
W/GmsClient(12658):     at android.os.Handler.handleCallback(Handler.java:942)
W/GmsClient(12658):     at android.os.Handler.dispatchMessage(Handler.java:99)
W/GmsClient(12658):     at android.os.Looper.loopOnce(Looper.java:201)
W/GmsClient(12658):     at android.os.Looper.loop(Looper.java:288)
W/GmsClient(12658):     at android.os.HandlerThread.run(HandlerThread.java:67)
E/JavaBinder(12658): !!! FAILED BINDER TRANSACTION !!!  (parcel size = 624)
W/GmsClient(12658): IGmsServiceBroker.getService failed
W/GmsClient(12658): android.os.DeadObjectException: Transaction failed on small parcel; remote process probably died, but this could also be caused by running out of binder buffe
W/GmsClient(12658):     at android.os.BinderProxy.transactNative(Native Method)
W/GmsClient(12658):     at android.os.BinderProxy.transact(BinderProxy.java:584)

Answer 1

我发现问题 initState() 中的一个初始化函数太长，需要大量打印日志并多次更新状态变量。我减少了打印和状态更新......一切正常