Support for debugging add-to-app flutter app

I’ve switched my app to be the add-to-app setup in order to better support app extensions on the iOS platform. While this is working great, and it’s nice to have full control over the Xcode Project generation, the drawback is that I can no longer start/debug the app from VS Code.

Would it be possible to add a new debug configuration for starting a custom app and connecting to that one?

I imagine it would look something like this:

{
  "name": "Flutter",
  "request": "launch-custom",
  "type": "dart",
  "xcworkspace": "ios/MyApp.xcworkspace",
  "xcscheme": "MyApp"
}

[DanTup]

Hmm, maybe not. I’ve opened a folder with a flutter and ios folder. The flutter root thus is in {workspace_root}/flutter, should that work? 🤔

Sort-of 😃

The problem here is that because you’re attaching (and not launching), we don’t know what part of your workspace is the project. I think if you create a launch.json and set the cwd to point at the flutter folder, probably that will fix it (since then we’d spot that it contained a pubspec that references the Flutter SDK).

To avoid confusion, if that doesn’t work - open a new issue with the details, and include a log (run Dart: Capture Logs, then run the attach command, then when it asks for Observatory URI, cancel it and click Stop Logging).

The other issue does look like a Flutter bug. I think the method for finding the Observatory URI is being changed to use mDNS (which should mean doing things in a specific order will not be required), but seems there’s something wrong with it. If you’re on master, you might be able to avoid it by switching to something like beta temporarily.

I don’t think there’s anything else for this issue so I’ll close it but feel free to post back on it if you have any questions about the above (for ex. if you can’t get the tasks/launch.json stuff working) and I’ll try to help out.

Thanks!

[DanTup]

You shouldn’t have needed to restart VS Code, though glad it’s working now 😃