Testing Panel Does Not Appear with v2.2.0

[rmecham]

Describe the bug
When opening certain Swift projects in VSCode with version 2.2.0 of the Swift plugin, the icon in the left for the testing panel does not appear. Attempting to run tests via the command palette also does not work. Upon downgrading to version 2.0.2 of the plugin, the testing panel becomes available again and tests can be run as expected.

This doesn't affect all projects. I haven't been able to pin down the exact trigger, but I strongly suspect it is related to dependencies. Projects with no dependencies reliably do not reproduce the bug.

To Reproduce
Steps to reproduce the behavior:

1. Open a Swift project in VS Code where the testing panel was previously available.
2. Allow plenty of time for the Swift plugin to initialize.
3. Observe that the testing panel does not appear in the left.
4. Attempt to run tests from the command palette; nothing happens.

Expected behavior
The testing panel should be available. It should be possible to launch tests from the panel or the command palette.

Environment

• OS: macOS 15.3.2
• Swift version: Swift version 6.0.3 (swift-6.0.3-RELEASE)
• Visual Studio Code version:

Version: 1.99.3 (Universal)
Commit: 17baf841131aa23349f217ca7c570c76ee87b957
Date: 2025-04-15T23:18:46.076Z
Electron: 34.3.2
ElectronBuildId: 11161073
Chromium: 132.0.6834.210
Node.js: 20.18.3
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.3.0

• vscode-swift version: 2.2.0

Additional context
I often use dev containers for development; this bug appeared in projects that do and do not use dev containers.

[plemarquand]

Do you have a project I could take a look at that reproduces this consistently? I haven't been able to find one that does yet.

[rmecham]

Do you have a project I could take a look at that reproduces this consistently? I haven't been able to find one that does yet.

I've been able to identify one project in particular that consistently reproduces this behavior for itself and anything that includes it as a dependency. Unfortunately, though, it is an internal project that I can't share. I will try to isolate what about that project is causing the problem so that I can reproduce it an an example project.

[rmecham]

It may be related to this error message:

workspace: Failed to load Package.swift: warning [...]

What follows is a long list of warnings from the compiler / package resolver. We're working on resolving those warnings, but they are only warnings. The project and its dependencies do still resolve and compile. Perhaps the new version of the plugin is treating these warnings as an error? The VS Code error box for these warnings does not appear when using v2.0.2 of the plugin.

[plemarquand]

@rmecham That is certainly suspicious. If the Package.swift is failing to load that would explain why the testing panel doesn't appear, as sourcekit-lsp needs a valid package manifest before it can discover test targets. Can you do a swift build in the VS Code terminal without issue? If you delete .build and re-open the package is it still an issue?

[rmecham]

Deleting .build and re-opening doesn't help. A successful compilation of this project from the command line does depend on passing some arguments to swift build. I've added those arguments to the swift.buildArguments and swift.additionalTestArguments sections in the project's .vscode/settings.json file but that doesn't seem to help.

[rmecham]

Also adding those arguments to swift.sourcekit-lsp.serverArguments doesn't seem to help, either.

[plemarquand]

Which arguments are you passing? You don't need to share the values if they're private information, just the flags passed to swift build.

[rmecham]

"swift.buildArguments": [
    "-Xswiftc",
    "-Xfrontend",
    "-Xswiftc",
    "-disable-round-trip-debug-types"
]

[matthewbastien]

@rmecham are you able to generate a diagnostics bundle for us using Swift: Capture VS Code Swift Diagnostic Bundle and upload it? You can review the information contained within it before sending it to us to make sure that it doesn't contain any sensitive information. There may be more information there like stack traces to go off of.

[rmecham]

@matthewbastien Here you go:

vscode-diagnostics-2025-05-07T15-51-18-06-00.zip

[plemarquand]

@rmecham thanks, this is helpful. It looks like one of swift package describe --type json or swift package show-dependencies --format json is failing with a non-zero exit code. Could you try running each of those from the root of your package an report if they produce any errors, or a non-zero exit code?