search

vknabel / vscode-swift-development-environment

New home of Swift Development Environment for VS Code
https://marketplace.visualstudio.com/items?itemName=vknabel.vscode-swift-development-environment
Apache License 2.0
175 stars 14 forks source link

SDE not activated; uncaught error "Cannot read property 'map' of null" #111

Closed fphartnc closed 3 years ago

fphartnc commented 3 years ago

Sorry to bother you so soon after my sourcekite issue, but I just noticed that the SDE does not get activated. [And no, the two are not related as this was the first time I attempted to use the SDE -- or at least the first where I was paying attention.] I am seeing the following in Runtime Status: Not yet activated. And below that, there is a list of "Uncaught Errors (1)" with the detail "Request initialize failed with message: Cannot read property 'map' of null" ...

fphartnc commented 3 years ago

Bump... Herr K., do you expect to have time to look into this in the near future? I ask because I am also having nothing but trouble getting the separate extension to use Apple's sourcekit-lsp built. That is not your problem, but I had expected to be easily able to use Apple-supported tools until you could look into the issue above, but this apparently is not the case as Apple's GitHub documentation does not correctly guide builds of the extension. I will probably have to deal with that on a forum at Swift.org...

vknabel commented 3 years ago

Hi @fphartnc, sorry for the late response - sometimes I just don't have enough time and energy. This weekend I will probably have enough time. 👍

When the error occurs, is there a stack trace in the logs? Could you provide that? Also: can you provide your vscode settings? This would really help me debugging.

You don't need to call me Herr K., simply @vknabel or Valentin is just fine 😊

fphartnc commented 3 years ago

@vknabel, Okay, no more Herr K... Attached are log files from the most recent run of VSCodium (I installed VSCodium, not VSCode) that appeared in the ~/.config/VSCodium/logs directory. Also attached is ~/.config/VSCodium/User/settings.json. I disabled sourcekit-LSP and Code-LLDB before this run so that their presence wouldn't pollute the log entries. Let me know if there's more I can do or provide on my end. I am new to using VSCode (though not Linux), but all of my Swift work until now has been in Xcode on a Mac.

On the log files, I could not upload "2-Swift-Build.log" and "5-Swift.log" because both were empty. I have supplied the others. The file "settings.json" had to be renamed "settings_json.txt" for upload through Firefox on the Mac. I am not certain I have captured the trace info you seek, so please provide further guidance on that if necessary.

One bit of good news: I finally did get sourcekit-LSP working, though I will probably post a documentation suggestion for the Apple developers that I hope will help others avoid the same rat hole. 1-Swift - Build.log 3-Git.log 4-Swift.log exthost.log settings_json.txt ..

vknabel commented 3 years ago

Thanks for all the attachments, they really helped me! I just released a fix in 2.12.2: the extension didn't work properly for non-workspaces / standalone files. Does it solve all your issues?

fphartnc commented 3 years ago

Hey, @vknabel, looks like SDE 2.12.2 has no issues with starting up and running, so the bug appears to be fixed! I am seeing a problem with hover help getting stuck (at "Loading...") with SDE whereas they work with the plain sourcekit-LSP and extension, but that may well be an operator error (configuration problem). Unless you want to track that here, I suggest closing and I'll continue working on that separately...

vknabel commented 3 years ago

Thanks for the feedback, I added a new issue and linked it here. Thanks!