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
flutter run --machine outputs "event sent after app closed" #61361
Comments
Also seeing this in Android Studio |
I also saw it on Android Studio. I think updating dart and flutter fixed it, but not sure |
Yes, we're seeing this in IntelliJ as well: I believe some refactoring of the logging meant that we can no longer send progress events from the flutter tool early in the app's lifecycle. I have a local change which largely addresses this (but am not certain where the best place is to put a test). I'll follow up with a PR. |
fixed by #65508 |
I got this error too. Need to kill the dart.exe and then close the editor and reopen it |
internet connection make me received that error |
I use a Mac and I found that the problem was linked to the location I had the flutter SDK installed. I had it installed in Applications and usr/local/bin which seemed to require authentication/sudo to modify. So, I created a new folder in the home directory called ~/Developer/Resources and unzipped the file there, updated the path in the terminal profile and when I ran it again from android studio / vscode / terminal it downloaded the iOS tools, and worked. Here are the updated steps for you:
Then open project and run. |
Why can't it be installed through Homebrew, automatically setting PATH variables correctly etc like normal software does. |
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 |
When running flutter
run --machine
, initial progress messages (ifpub get
runs) are output with an error:Because this isn't valid JSON, in VS Code we assume this is a message for the user and show it in the debug console (rather than showing a progress indicator).
(@jonahwilliams sorry! 😬)
The text was updated successfully, but these errors were encountered: