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
FAILED BINDER TRANSACTION #113427
Comments
Hi @AnukirtiYadav, please provide a completed and minimal reproducible code sample so that we may verify this. Also, please provide the output of |
Hi @AnukirtiYadav, I've faced this issue before. It's mainly causing on my mac m1 by the android emulator. Can be resolved by quitting the emulator and run again. |
I have the same on m1 but tried this option and nothing has changed, how do you quit the emulator. |
after
Try to use |
I get the same error on a MacBook Pro but with intel, is it a mac error? I tried restarting the emulator, closing it and reopening it but the error remains. |
I get the same error. i'm trying to add google ad banner on my app. currently just using the test AdMob app and ad units. ad is not showing. |
In my case, I reverted to Pixel 2 API 30 emulator on my mac and it works fine compared to latest version (33) |
I've the same problem in the emulator, BUT not in physical phone. |
I've the same problem in the google play api 33 emulator. |
I encounter the same error, when trying to use the Google One Tap button with Jetpack Compose. Restarting the Emulator seems to help most of the time. Emulator: |
I've the same issue on Pixel XL API 33 emulator |
Hi everyone facing this issue, I tried running the default Flutter project (counter app) on Pixel 4 API 33 emulator but can not reproduce this issue. It would be nice if you can provide a completed and minimal reproducible code sample so that we may verify this, and along with the output of |
In my case, after wiping data of emulator works. |
It's the issue with emulators on m1. For now the only way out from this issue is cold booting your emulator. |
I had the same issue with a Nexus 5X API 33 Google Play x86_64 emulated device. I did multiple things at once so I'm not sure which one did the trick but I'm leaving my steps here in case it will help someone out:
But I still get this log error:
which makes me concerned if it is "stable" to use. I'm currently testing android api 33 and I'm on the master channel of flutter as it has a critical not released fix regarding tree-shaking which caused non related issues on iOS devices. flutter doctor -v
APP: build.gradle Android: build.gradle EDIT: Maybe another important side-note, I do not have this issue with API versions 30 and 31. Also the log message does not appear on those API versions. |
Have faced this issue only when working with API 33 emulator on M1 Mac. The issue gets resolved temporarily after a cold boot of the emulator but it comes back every now and then. |
Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. |
this also worked on my windows machine |
FYI
Simulator reboot made no difference. |
anyone know how to cool boot on intellij since my emulator doesn't show and i have tried cool boot from android studio still cannot since the emulator still running |
Noticed this during a navigation transition while testing on a Windows Android Emulator earlier today. Didn't cause any noticeable issues but though it's worth adding that it wasn't just M1 Macs for me. |
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of |
Steps to Reproduce
flutter run --flavor development --target lib/main_development.dart
Expected results:
App should run.
Actual results:
Code sample
Logs
The text was updated successfully, but these errors were encountered: