-
Notifications
You must be signed in to change notification settings - Fork 28.6k
Stopping a debug session does not terminate the app on iOS #52232
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
I thought we had another issue for this but I can't find it at the moment. |
I think we have an issue for physical iOS devices filled in 2016, but not one for simulators - possibly a similar issue though |
FWIW I don't have a physical iOS device to test, so when I put "iOS Simulator" in the subject it was mostly because it doesn't happen for Android Simulators (so it may be the same issue as for a physical device). |
Confirm this issue still exists unfortunately |
I just tried this on Flutter master in Android Studio and the stop button quit the app. Am I missing repro steps, @DanTup?
|
Same for me in VS Code - so as far as I can see, it's no longer an issue. I tested with iOS Simulator, current Flutter master (today) and latest VS Code + extensions. @mikeRozen if you're still seeing this, can you confirm Flutter version/device and how you're testing? |
Sorry for the late response yes I still see it on IOS simulator. (android studio) |
@jmagman I see the same with Flutter 2.5.0 in both VS Code and Android Studio now (using a new project created using
|
did you solve this issue? |
Same here. It used to work on my previous Intel Mac with Flutter 2.5. But on my M1 Max MacBook Pro with Flutter 2.8.1 on macOS 12.1, here's what happens if I stop the runner in IntelliJ IntelliJ IDEA 2021.3.1 (Ultimate Edition; Build #IU-213.6461.79):
|
I have the exact same issue on M1 MacBook Air:
|
I am seeing this just with "flutter run" on an M1 mac mini, without the "--start-paused" and without using an IDE to launch. |
Still an issue. Simulator and physical device. Doctor summary (to see all details, run flutter doctor -v): |
I can reproduce this issue in the current stable and master
|
I have the same issue as @PaulRudin above. M1MAX Macbook Pro, iOS Simulator, running flutter doctor -v
|
I'm seeing the same issue from terminal and Android Studio. When I run from IntelliJ it works. MacBook Pro M1 Max running Flutter Beta 3.3.0-0.2.pre on macOS 12.5 flutter doctor -v
|
Has continued to happen for me with all Flutter versions since at least January when I made my initial comments - M1 Max MacBook Pro, latest Flutter stable version (currently at 3.0.5), latest macOS version (currently at Monterey 12.5): When I start Flutter on an iOS simulator from IntelliJ and stop it in IntelliJ, it always goes on running in the simulator. And at least right now, the same is true when launching my app from the terminal. |
As of #113581 |
I can confirm that this issue is fixed in the latest master. Closing this issue as fixed |
Still happening with 3.3.5 for me. |
@jmagman Thanks for the clarification. Reopening this issue until the fix lands :) |
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 |
Uh oh!
There was an error while loading. Please reload this page.
When running an app on the iOS Simulator in debug mode (eg.
flutter run --start-paused
), the app is not terminated on the device when you stop (send anapp.stop
request). This happens even if the app is not paused at the time.To repro:
Looking at the logs in VS Code, the
--start-paused
flag is the only thing I can see that's difference in these cases, so I think something it's doing is changing the behaviour whenapp.stop
is sent.(moved from Dart-Code/Dart-Code#2291)
The text was updated successfully, but these errors were encountered: