Debugger cannot attach when using chrome profiles

Question

I am using multiple chrome profiles for various scenarios. I have a launch.json as follows: { "type": "pwa-chrome", "request": "launch", "name": "Custom Profile", "url": "http://localhost:4000/index.html?scale=.5&play=HIMSS2022&tb=1&offline=true", "breakOnLoad": true, "sourceMaps": true, "userDataDir": false, "runtimeArgs": [ "--profile-directory=CustomProfile", "http://localhost:4000/index.html" ], "webRoot": "${workspaceFolder}", "sourceMapPathOverrides": { "webpack:/": "${webRoot}/", "/./": "${webRoot}/", "/src/": "${webRoot}/", "/": "", "/./~/": "${webRoot}/node_modules/" } }, If I launch with no other chrome windows open the debugger attaches. If I open Chrome (with a different profile or default) then the debugger fails to attach, yielding an alert "Unable to attach to browser" with Open 'launch.json' and Cancel buttons

Is there some attribute I need to add to the config, or is this just not possible?