[Solved] No output in VScode debug console

Development VSCode Swift extension
,
1

After updating VScode, the Debug Console stopped showing my app's log output (worked fine previously).

Any ideas for fixes / workarounds?

Here's my setup:

  • VScode Version: 1.120.0 (user setup)
    Commit: 0958016b2af9f09bb4257e0df4a95e2f90590f9f
    Date: 2026-05-12T20:17:22Z
    Electron: 39.8.8
    ElectronBuildId: 13870025
    Chromium: 142.0.7444.265
    Node.js: 22.22.1
    V8: 14.2.231.22-electron.0
    OS: Windows_NT arm64 10.0.26200
  • swiftlang.swift-vscode Version 2.17.20260513
  • Swift Toolchain: TBC swift-6.3.0-20260513.3
  • OS: Windows 11 ARM
2

Hey @ktraunmueller, mind raising an issue at Issues · swiftlang/vscode-swift · GitHub and someone can try to reproduce

3

I'm also curious if you install the previous version of the extension if the issue reproduces. I don't think there have been any changes in the area of the Debug Console recently

4

When switching VScode extension to the released version 2.16.4, the problem persists.

Note that, as mentioned, the problem popped up after updating VScode, not the extension.

5

Hard to tell without more info, but it's possible that this is related to issue #309 which was recently fixed in the toolchain. Are you able to try out a nightly-main toolchain to see if that resolves the issue?

If not then can you run the Swift: Capture Diagnostics Bundle and send it to me? In this case we would need to capture full diagnostics so that the lldb-dap logs are included.

6

Thanks for the issue link. I will try a main toolchain if I can't find another workaround. Strange that it worked just fine before, as mentioned.

Here's the diagnostics bundle (Google Drive link, can't upload a zip here).

7

Yeah, that is strange that it appears to be tied to the VS Code version. There's another issue we discovered in 6.3 where lldb-dap on Windows is incorrectly reporting stdout/stderr under the general console message type in the debug adapter protocol (this is also fixed in nighty-main). Perhaps the latest version of VS Code hides console messages by default now in the Debug Console? Nothing interesting in the logs, unfortunately.

8

I finally got around to trying a main toolchain (latest BrowserCompany build), and I am happy to report that the Debug console output is back (without upgrading VScode).

1 Like