Error while fetching list of available targets No available targets to attach.

[johntony366]

Environment (please complete the following information):

• OS (e.g., Windows 10): WSL2 (Ubuntu 20.04.4 LTS) on Windows 11 Pro
• Extension version (e.g., 1.2.3): 2.1.0

Describe the bug:

On clicking Open with Edge -> Open browser, an error pops up with the message "Error while fetching list of available targets No available targets to attach."

Repro steps:

1. Open a workspace in visual studio code (WSL).
2. Right click the index.html file and click Open with Edge -> Open browser.

https://user-images.githubusercontent.com/88877609/180636806-226dbf51-6257-40b8-b1db-d62d693487f5.mp4

Expected behavior:

1. A browser tab is opened within visual studio code that displays the expected content.

Additional context:

[codepo8]

Thank you so much for this detailed issue. I added it to the backlog

[RadioactivePlays]

Exact same issue here😐

[johntony366]

The extension works as expected on Windows. Hope the issue on WSL can be fixed soon.

[captainbrosset]

Marking as tracked, since this is on the backlog for the team to look at.

[Agrover112]

Lol same issue , I thought I was dumb for a second or what lol

[gzmorell]

I have the same issue on Windows 10.

[Josephisi]

I currently have this same issue on my mac

[nwaweru]

Having the same issue. I am on Windows 11 and WSL2.

[piesikot]

Guyz I'm using pop os and had this issue, desperately was trying many things and it started working when I've uinstalled Edge and installed version from official site.

[anson999]

Having the same issue. It's unable to triggered installed edge browser in macOS 12.6 but works well with Chrome/Safari.

[ScopeRay]

same issue :(

[d-pletikapa]

Error while fetching list of available targets No available targets to attach.

Same here on win10

[codepo8]

Can someone verify that this happens on the first launch? I sometimes get this issue when I had a session open before and didn't close it, so I am suspecting that there might be some caching happening here.

[enviouscodefellow]

I'm experiencing this issue after upgrading to Ubuntu 22.04. Previously, no issues with 20.04 on windows 10 (Live server also no longer working)

[d-pletikapa]

Can someone verify that this happens on the first launch? I sometimes get this issue when I had a session open before and didn't close it, so I am suspecting that there might be some caching happening here.

I installed Vscode on new fresh machine and decided to synchronize my settings with the help of the plugin called 'Sync' , so after a few conflict merges in settings i got the same problem with MS Dev Tools plugin witch i got on my previous machine, so it leads me to a conclusion that some settings in Vscode or in DEVtools plugin must be messed. But i dont know how to fix them.

i`m getting it on win 10 (fetching error like in header of this topic) i tried to re-adjust port numbers on the same in devtools and liveserver plugins at the same time but it doesnt help at all

[enviouscodefellow]

I'm experiencing this issue after upgrading to Ubuntu 22.04. Previously, no issues with 20.04 on windows 10 (Live server also no longer working)

Interestingly, using the live preview extension from Microsoft will work and open in browser just fine...quick workaround for now...

[Domine29]

same issue trying to open DevTools by right-clicking on the .html file. On Windows 11, WSL

[JonrGull]

Also still have this issue. Can't get it to work with CRA at all.

[stevecu]

This is still an issue in WSL on Win11.

[abhijitmjj]

facing the same issue

[tunztunztunz]

Still seeing this issue when using WSL on Win 11 as well.

[Loongphy]

Works well on Win11, same issude using WSL2 on Win11.

[indexfull]

same issue window 10

[AJSN1988]

Having a same issue on mac.

[luke-pritch]

Exact same issue, on an M1 Pro Macbook 13.2.1 (22D68),

VSCode info:

Version: 1.76.1 Commit: 5e805b79fcb6ba4c2d23712967df89a089da575b Date: 2023-03-08T16:48:08.231Z (1 wk ago) Electron: 19.1.11 Chromium: 102.0.5005.196 Node.js: 16.14.2 V8: 10.2.154.26-electron.0 OS: Darwin arm64 22.3.0 Sandboxed: Yes

[RDhar]

This remains an issues on the latest Win 11 via WSL2 on Edge Dev browser with the following launch.json for a basic, static HTML page.

{
  "version": "0.2.0",
  "configurations": [
    {
      "type": "msedge",
      "request": "launch",
      "name": "Open index.html",
      "file": "/home/username/code/basics/index.html"
    }
  ]
}

Version: 1.78.0-insider (user setup) Commit: 3e0b354932b8ddeb099c68ed3b7dfac25350dde2 Date: 2023-04-06T05:20:25.265Z Electron: 22.4.3 Chromium: 108.0.5359.215 Node.js: 16.17.1 V8: 10.8.168.25-electron.0 OS: Windows_NT x64 10.0.22621 Sandboxed: Yes

[Fefedu973]

Same issue here but on windows 11 pro no wsl maybe time to fix it:

Nom de l'appareil SUPERPC Processeur 12th Gen Intel(R) Core(TM) i7-12700KF 3.60 GHz Mémoire RAM installée 32,0 Go (31,8 Go utilisable) ID de périphérique E1726DA7-78B4-4C21-A0AC-A93B7574792D ID de produit 00331-20090-00000-AA912 Type du système Système d’exploitation 64 bits, processeur x64 Stylet et fonction tactile Prise en charge de la fonction tactile avec 4 points de contact Édition Windows 11 Professionnel Insider Preview Version 22H2 Installé le ‎09/‎04/‎2023 Build du système d’exploitation 25336.1010 Expérience Windows Feature Experience Pack 1000.25336.1010.0 Version: 1.77.3 (user setup) Commit: 704ed70d4fd1c6bd6342c436f1ede30d1cff4710 Date: 2023-04-12T09:16:02.548Z Electron: 19.1.11 Chromium: 102.0.5005.196 Node.js: 16.14.2 V8: 10.2.154.26-electron.0 OS: Windows_NT x64 10.0.25336 Sandboxed: No

[wildiego]

Same issue here:

Processor 12th Gen Intel(R) Core(TM) i7-1260P 2.10 GHz Installed RAM 16.0 GB (15.7 GB usable) Device ID 49BA0CFC-6A57-440D-8560-21260FB03D55 Product ID 00342-22036-37056-AAOEM System type 64-bit operating system, x64-based processor

Edition Windows 11 Home Version 22H2 Installed on ‎4/‎12/‎2023 OS build 22621.1555 Serial number PF40AC4J Experience Windows Feature Experience Pack 1000.22640.1000.0

[b4ruch]

Hopefully this will be resolved at some point. It's been 9 months since it was first reported. When right-clicking the .html file (which resides in WSL) to open DevTools, Edge receives an unreachable directory path (.html's WSL dir path). Thus, it is unable to interpret that path and therefore, unable to render the file.

[Fefedu973]

I don't have wsl and my file is in a Normal folder but it still doesn't work. I tried with several versions of vscode and all of them have the same problem and I tried in several directory but nothing changes