sourcekit-lsp client crashes after any run command in Neovim

[gmtborges]

Swift version

Apple Swift version 6.0 (swiftlang-6.0.0.9.10 clang-1600.0.26.2)

Platform

macOS 14.7

Editor

Neovim

Description

When I open a xcworkspace or xcodeproj project in Neovim, sourcekit-lsp loads normally, but if I execute anything like (:Telescope, open explorer, :XcodebuildPicker, ...) it quit with this message:

Client sourcekit quit with exit code 0 and signal 5. Check log for errors: /Users/gustavo/.local/state/nvim/lsp.log

And nothing was logged in the lsp.log. But in Console App there is a sourcekit-lsp crash report.

Steps to Reproduce

1. Init a project with tuist mkdir MyDemo && cd MyDemo && tuist init --name MyDemo
2. Generate the xcworkspace tuist generate
3. Open in Neovim
4. Await sourcekit-lsp loads (Verify with :LspInfo)
5. Run any other command (:Telescope, :Ntree)

Logging

log.txt

[ahoppen]

Oh, that’s interesting. We’re crashing in

sourcekit-lsp/Sources/LanguageServerProtocol/SupportTypes/DocumentURI.swift

Lines 59 to 61 in dd95a3d

	return storage.withUnsafeFileSystemRepresentation {
	String(cString: $0!)
	}

.

I’m wondering what kind of URI is producing this. Would you be able to enable extended logging as described here, reproduce the issue and attache the log file produced by that?

[gmtborges]

The logs with extented logging enabled
log.txt

BTW this is the project I'm playing with
https://github.com/gmtborges/MyDemo

[ahoppen]

Did you install the profile mentioned in the macOS section of the document I linked and then reproduce the issue? Your new log still shows <private>, which indicates to me that extended logging isn’t enabled.

[gmtborges]

Oh sorry, I setup the wrong step (.sourcekit-lsp/config.json). Now with the profile activated.
log.txt

[ahoppen]

Thanks for the log. It looks like your editor is sending the a textDocument/documentColor request with the following payload (last couple of lines in the log)

{
  "textDocument" : {
    "uri" : "file://"
  }
}

While SourceKit-LSP shouldn’t crash on this, this indicates that something in neovim or the plugins you have installed in neovim is wrong because it should probably include the file path in the request.

[gmtborges]

Thank you so much man! I found the plugin that was causing the issue. brenoprata10/nvim-highlight-colors

[ahoppen]

Let’s keep the issue open to make sure SourceKit-LSP doesn’t crash in this case but returns an error.

[ahoppen]

Synced to Apple’s issue tracker as rdar://137886470