launch.json not automatically generating

[TMHarryJones]

1. Describe the bug When using the "AL: Go!" or "AL: Download Symbols" commands inside of Visual Studio Code I am presented with the usual 2 options "Your own server" and "Microsoft cloud sandbox", however when I select either option the launch.json is not automatically generated inside of the .vscode folder. Selecting either of the options does not cause any kind of error to be thrown either.

2. To Reproduce Steps to reproduce the behavior:

1. Run the "AL: Go!" or "AL: Download symbols" commands
2. When presented with the "Your own server" and "Microsoft cloud sandbox" options, select either option as it doesn't make a difference
3. Nothing happens

3. Expected behavior The launch.json should be automatically generated inside the .vscode folder and the "configurations" section of the json should contain details which are dependent on the option selected in step 3 of the repro steps

4. Actual behavior When using the "AL: Go!" command, nothing happens. When using the "AL: Download symbols" command, I am presented with the "Could not download symbols. Please see the Visual Studio Code output log for more details." error. The output log just says "Error: No server has been chosen"

5. Versions:

• AL Language: Latest release and pre-release, also tried on older release (14.3.1327807)
• Visual Studio Code: 1.99.3
• Operating System:
  • [X] Windows

[blrobl]

Hi, I cannot reproduce this behavior. Did this use to work before? What happens if you click here on the Run & Debug tab in VS Code? There might be some setting in your local setup preventing these files from being created or being created elsewhere.

[TMHarryJones]

Hi, apologies for the delay in response!

Definitely used to work, I only noticed it not working after updating Windows last week - updated it, noticed the issue, tried to resolve and then submitted the bug when I couldn't. I know it's not isolated to just me as a few colleagues are also experiencing this issue. I did try to find any settings which could be affecting this, but came up short.

Any suggestion/pointers, off the top of your head, as to which settings may be affecting this?

I can confirm the action you suggested works as well, thanks.

[blrobl]

Thanks for raising this issue and for your input. At the moment, we're focusing on other priorities, so we won't be addressing this directly, since we don't have a repro on our side and there is a workaround available that should help mitigate the problem in the meantime. Thanks again for your understanding!