-
Notifications
You must be signed in to change notification settings - Fork 28.6k
Lost connection to device on save #26945
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
Comments
Perhaps https://github.com/flutter/flutter/wiki/Workarounds-for-common-issues#hot-reload-not-working Can you please try to get more information using these instructions #20998 (comment) |
@zoechi I was not able to get the logs from XCode but I got them from the Simulator itself (Debug > Open System Log...) I cleaned the log after startup and this is what's logged on save.
|
You are not by any chance use a proxy or self-signed certificates? |
Try manually uninstall from the phone/simulator and run |
I started seeing this about 3 weeks ago. Very often I get Lost Connection when hot reloading on iOS. I've tried flutter clean and uninstalling the app. |
I just see.
And the app is left frozen. |
You can raise priority with thumbs-up on the initial comment |
Bump. |
I no longer am seeing this issue as of around Flutter 1.5 |
I am on version 1.5.4 and having this issue. As soon as I run my app, it says I have tried to reboot Android Studio and my laptop but nothing seemed to work. |
Me too, It's my first time building flutter on MacOS and right after my app launched the log says |
Same behavior for me. MacOS and after launch, it loses the connection to the device. |
+1 Just did: i get the error: |
Same here as well. "Lost connection to device." immediately after launch. Hot reloading not working properly |
Same here as well. "Lost connection to device." immediately after launch. Debugging is not working. |
I too experienced this. Tried mostly everything I could find on the internet. Tried
Versions: Mac OS Mojave 10.14.5 I think, the error message is a tad misleading; I don't think flutter command runner could make connection to the observatory at all, however I don't have any evidence to this. After a few attempts, there are a number of What worked without hickup is running the same app on Android device. For now, just a wild idea is that docker virtual interfaces might be interfering? |
Update: after killing all docker related services and removed the networks created for docker, the error has changed from @YAPPDEF do you also use docker or do you have any other virtual machine on your computer that has it's own interfaces? |
Tried all of these, still can't debug on a physical device.
Solutions?? |
+1 |
Same problem. Every time I run
|
Same problem +1 MacOS Mojave 10.14.5 Flutter 1.5.4-hotfix.2 • channel stable • https://github.com/flutter/flutter.git |
+1 Flutter 1.5.4-hotfix.2 |
#35102 (comment) is a workaround for this. see that. |
This seem to have fixed both MacOS installs I knew of that had this problem. Single note: iproxy instances were stuck, computer restart was needed. |
This issue is fixed. Please close this. |
You can check stackoverflow answer. This may solve your problem |
I'm getting this in Android Studio, with usbmux updated. VSC works. So for me, with Android Studio, this is not closed. |
+1 Same here, still having this issue. macOS Mojave 10.14.6 Update: |
I still see this from time to time as well, using Android Studio.
|
I'm getting this as well after doing Flutter Upgrade. |
getting Lost connection to device after upgrading using flutter upgrade! |
I am getting the same behavior and it turns out it works if you disable automatic opening of dart devtools in chrome. (applies to lost connection to device in vscode) |
I am also got the same issue as below, huangweipeng@huangweipengs-MacBook-Pro colorful_classroom_app % flutter run └─Compiling, linking and signing... 9.6s |
There are a lot of unrelated issues posted in this thread, unfortunately that is making it impossible to tell what is tracking. Generally this could happen if the application crashes, but then we need a stack trace to figure out what is happening. Without a way to reproduce the issue on our end there is nothing for us to do here. I'm closing the issue for now, but feel free to re-open if you can provide a minimal reproducible-example |
Steps to reproduce:
I didn't update and have this issue since yesterday. Any ideas?
The text was updated successfully, but these errors were encountered: