serviceInfoFile doesn't seem to work for custom flutter embedders

[knopp]

My flutter application writes a service info file, but when I specify it in the launcher configuration Dart-Code doesn't poll for it.

vmServiceUri with prompt works as expected, but it's not ideal to have to copy and paste the URI on every launch.

• Dart extension version: dart 3.22.0
• Dart/Flutter SDK version: current master

[knopp]

The application is not built through the flutter tool so I can't run it using flutter run. flutter attach works, but I need to specify vmServiceUri on every launch.

(down the line it would also be nice to have option for Dart-Code to launch a custom executable with --write-service-info), but for now at least serviceInfoFile working would be a big quality of life improvement.

[DanTup]

down the line it would also be nice to have option for Dart-Code to launch a custom executable with --write-service-info

You might be able to do this with a preLaunchTask (eg. cause the debug config to run a background task that spawns the app before it tries to debug) or a compound config (one that runs a Dart script that sets up the file and spawns your process) - I don't know how messy that would be though.

There is also some support for overriding the Flutter/Dart binaries, but it's aimed at some specific Bazel workspace setups so not something official supported for this, but may be another option to improve things until/unless something better is available:

Dart-Code/src/shared/utils/workspace.ts

Lines 57 to 69 in 195b1c6

	config.activateDevToolsEagerly = !!flutterConfig.devtoolsActivateScript;
	config.dartSdkHomeLinux = makeFullPath(flutterConfig.dartSdkHome?.linux);
	config.dartSdkHomeMac = makeFullPath(flutterConfig.dartSdkHome?.macos);
	// This one replaces the args "global activate devtools"
	config.devtoolsActivateScript = makeScript(flutterConfig.devtoolsActivateScript, 3);
	// This one replaces the args "global run devtools"
	config.devtoolsRunScript = makeScript(flutterConfig.devtoolsRunScript, 3);
	config.flutterDaemonScript = makeScript(flutterConfig.daemonScript);
	config.flutterDoctorScript = makeScript(flutterConfig.doctorScript);
	config.flutterRunScript = makeScript(flutterConfig.runScript);
	config.flutterSdkHome = makeFullPath(flutterConfig.sdkHome);
	config.flutterTestScript = makeScript(flutterConfig.testScript);
	config.flutterVersionFile = makeFullPath(flutterConfig.versionFile);

As for the original request - looking at FlutterDebugSession, attachRequest calls launchRequest which calls into DartDebugSession.launchRequest so I don't think it should be complicated to fix this - I suspect there are just some bad assumptions somewhere.

[DanTup]

Although this works in my testing with simple Flutter, it's not working for @knopp:

[1:28:22 PM] [FlutterRun] [Info] [Flutter: Attach to Process] Spawning flutter with args ["attach","--machine","-d","macos","--debug-uri","ws://127.0.0.1:60238/40DHMrlkLa0=/ws","--devtools-server-address","http://127.0.0.1:9100/","-v"]

[ +104 ms] Exception attempting to connect to the VM Service: WebSocketException: Connection to 'http://127.0.0.1:60238/40DHMrlkLa0=/ws/ws#' was not upgraded to websocket

The /ws/ws looks suspicious - though it's interesting I'm not seeing that (I did see the URL mangled in a different way though, it ended up with .,/ws on the end - but it still worked). Perhaps something changed in Flutter (I'm on master).