`userDataDir` has unexpected results

[Enteleform]

Environment:

• OS: Windows 10
• Extension: 1.3.1

Describe the bug:

Setting vscode-edge-devtools.userDataDir does not work as expected.

Repro steps:

// opens default temporary profile
"vscode-edge-devtools.userDataDir": false,
"vscode-edge-devtools.userDataDir": "C:/Users/Enteleform/AppData/Local/Microsoft/Edge/User Data/Profile 2",
"vscode-edge-devtools.userDataDir": "C:/Some/Invalid/Path",

// opens `Enteleform/Profile 2`
"vscode-edge-devtools.userDataDir": "C:/Users/Enteleform/AppData/Local/Microsoft/Edge/User Data",

Expected behavior:

// opens `Enteleform/Profile 1`
"vscode-edge-devtools.userDataDir": false,

// opens `Enteleform/Profile 2`
"vscode-edge-devtools.userDataDir": "C:/Users/Enteleform/AppData/Local/Microsoft/Edge/User Data/Profile 2",

// shows an error message informing user to use the path of a valid profile directory
"vscode-edge-devtools.userDataDir": "C:/Some/Invalid/Path",

// same as the previous example, unless one of the suggestions below is implemented
"vscode-edge-devtools.userDataDir": "C:/Users/Enteleform/AppData/Local/Microsoft/Edge/User Data",

Suggested behavior:

// - remove the `false` option
// - add the following options, which are more explicit and provide context as to their outcome

// opens `Enteleform/Profile 1`
"vscode-edge-devtools.userDataDir": "default",

// shows a dropdown to select one of the available user profiles @ `%LocalAppData%/Microsoft/Edge/User Data`
"vscode-edge-devtools.userDataDir": "select",

// shows a dropdown to select one of the available user profiles @ the defined path
"vscode-edge-devtools.userDataDir": "C:/CustomPath/Edge/User Data",

[burkeholland]

Hit this same issue today.

Works

"vscode-edge-devtools.userDataDir": "C:/Users/buhollan/AppData/Local/Microsoft/Edge/User Data"

Does not work

Launches with the temp profile

"vscode-edge-devtools.userDataDir": "C:/Users/buhollan/AppData/Local/Microsoft/Edge/User Data/Profile 2"

How can we launch a specific profile?

[captainbrosset]

Thank you both for your feedback, and apologies about the delay. @codepo8 this seems like a valid bug to track, want to add the tracked label so this can be planned?

[marr]

I am also interested in this. I would like to use my local chrome profile for the "Open link" functionality along with debugging. Setting a value for userDataDir does not appear to work as expected. If I use false for the value, the correct browser profile opens, but debugging does not appear to work.

[ardyhash]

Was about to create a new feature request before finding this, I too am interested in using existing profiles (on a Mac), this plugin could replace my actual browser if the profile aspect worked as expected

[JANA-itsaishvili]

damn. this issue is still outstanding. i wanted to open my Default profile, and i got into this rabbit hole. this is the most relevant thing i found, which implies the extension doesn't respect runtime args neither via the launch.json config nor the settings.json config:

edge://version formatted for legibility

  --user-data-dir=[...dir]ms-vscode.js-debug-companion.profile
  --disable-background-networking
  --disable-background-timer-throttling
  --disable-backgrounding-occluded-windows
  --disable-breakpad
  --disable-client-side-phishing-detection
  --disable-default-apps
  --disable-dev-shm-usage
  --disable-renderer-backgrounding
  --disable-sync
  --metrics-recording-only
  --no-first-run
  --no-default-browser-check
  --profile-directory=Default
  --remote-debugging-pipe
  --flag-switches-begin
  --flag-switches-end

i tried overriding these by setting some of them to false, but no go.

This could be a VS Code thing, because the launch.json config is independent of the extension.

PS, I'm running VS Code with WSL2 and the latest builds of VS Code, MS Edge, and WIndows 11.