`flutter attach` doesn't work on physical iOS device in larger apps
I have a problem with `flutter attach` not working in larger apps. Of course, "larger apps" is subjective. I tried to reproduce this issue in 3 apps: 1. the default app (`flutter create example --platforms ios,android`) (1 dependency, not reproduced) 2. [example app](https://github.com/leancodepl/patrol/tree/master/packages/patrol/example) from [the Patrol project](https://patrol.leancode.co) (7 dependencies, reproduced) 3. [my private, closed-source app](https://play.google.com/store/apps/details?id=pl.baftek.discoverrudy) (50 dependencies, reproduced) ## Steps to Reproduce 1. Connect the physical iOS device 2. Clone [the Patrol repository](https://github.com/leancodepl/patrol/tree/master/packages/patrol/example) and `cd packages/patrol/example` 4. `flutter run`, and then `d` (to detach after the app starts) 5. If the "Local network" permission dialog shows up on the device, accept it 6. `flutter attach --app-id com.example.example` (PS This could be another bug report: `--app-id` is always required when using `flutter attach` on iOS – otherwise it fails). **Expected results:** After a short wait, `flutter attach` connects to the Dart VM running inside the application and I can debug my app. **Actual results:** The message `Waiting for a connection from Flutter on Barteks-iPhone...` shows up and nothing happens, even after a few minutes. Also, sometimes (again, sorry for these "sometimes", but I just cannot deterministically reproduce these issues) the command crashe
Posted by bartekpacia on Mar 15, 2023, 2:44 PM
Tags
Related issues
- 2026 - Microsoft Office 365
- [Ubuntu] `ubuntu-latest` label will use Ubuntu 26.04 in November 2026
- Gamut mapping
- [Codex Desktop] Editing and resending a queued message triggers "App-server queued follow-up no longer exists"
- [Windows] ChatGPT 26.820.60940 fails with "invalid transport in mcp_servers.codex_app"; Beta 26.727.40816 works
- [BUG]: infinite loading of videos
Raise real-world problems, find people facing the same issue, and discuss solutions.2,500 issues0 comments
github (SaaS)
2026 - Microsoft Office 365
[Ubuntu] `ubuntu-latest` label will use Ubuntu 26.04 in November 2026
Gamut mapping
[Codex Desktop] Editing and resending a queued message triggers "App-server queued follow-up no longer exists"
[Windows] ChatGPT 26.820.60940 fails with "invalid transport in mcp_servers.codex_app"; Beta 26.727.40816 works
[BUG]: infinite loading of videos
Restore GPT-5.6 Sol’s 372k Codex context window, or provide an opt-in setting
Codex Desktop for macOS repeatedly triggers `syspolicyd` / `trustd` CPU and memory runaway
`flutter attach` doesn't work on physical iOS device in larger apps
I have a problem with `flutter attach` not working in larger apps. Of course, "larger apps" is subjective. I tried to reproduce this issue in 3 apps: 1. the default app (`flutter create example --platforms ios,android`) (1 dependency, not reproduced) 2. [example app](https://github.com/leancodepl/patrol/tree/master/packages/patrol/example) from [the Patrol project](https://patrol.leancode.co) (7 dependencies, reproduced) 3. [my private, closed-source app](https://play.google.com/store/apps/details?id=pl.baftek.discoverrudy) (50 dependencies, reproduced) ## Steps to Reproduce 1. Connect the physical iOS device 2. Clone [the Patrol repository](https://github.com/leancodepl/patrol/tree/master/packages/patrol/example) and `cd packages/patrol/example` 4. `flutter run`, and then `d` (to detach after the app starts) 5. If the "Local network" permission dialog shows up on the device, accept it 6. `flutter attach --app-id com.example.example` (PS This could be another bug report: `--app-id` is always required when using `flutter attach` on iOS – otherwise it fails). **Expected results:** After a short wait, `flutter attach` connects to the Dart VM running inside the application and I can debug my app. **Actual results:** The message `Waiting for a connection from Flutter on Barteks-iPhone...` shows up and nothing happens, even after a few minutes. Also, sometimes (again, sorry for these "sometimes", but I just cannot deterministically reproduce these issues) the command crashe
Comments (0)
No comments yet. Start the discussion.