Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extension shows the "need to update some CodeLLDB settings" alert extremely frequently #991

Open
NSExceptional opened this issue Aug 6, 2024 · 8 comments
Assignees
Labels
bug Something isn't working

Comments

@NSExceptional
Copy link

I'm seeing this message several times a week, if not every day:

Screenshot 2024-07-25 at 5 25 03 PM

I hope this is not intended. I always click "global"

Environment

  • OS: macOS Sonoma 14.5
  • Swift version: 1.90.11.1 Apple Swift version 5.10
  • Visual Studio Code version: 1.86.1
  • vscode-swift version: latest at this time
@NSExceptional NSExceptional added the bug Something isn't working label Aug 6, 2024
@adam-fowler
Copy link
Contributor

Every time you change swift version it needs to update those settings

@plemarquand
Copy link
Contributor

@NSExceptional Is there anything you're doing just before this dialog appears? Updating Swift toolchains?

@adam-fowler I'm not sure but I think this dialog might also come up when a new version of the vscode-swift extension is released?

@NSExceptional
Copy link
Author

That must be it, I am changing between the beta and the release versions of Xcode.

There has to be a way to do this automatically without prompting the user every time though, right?

@adam-fowler
Copy link
Contributor

Well there's the decision to make the change globally or on the workspace that needs to be made. I guess we could add a setting that has the options always set it globally, always set it for the workspace, show dialog

@NSExceptional
Copy link
Author

Why not just use global if no workspace CodeLLDB settings were ever set, and use workspace if there are some set? Is that possible?

If not, what you suggested sounds fine too

@adam-fowler
Copy link
Contributor

Why not just use global if no workspace CodeLLDB settings were ever set

This could be annoying if you have two projects open that use different versions of swift

@NSExceptional
Copy link
Author

I see, okay. The setting is probably the way to go then

@plemarquand
Copy link
Contributor

#1024 should help with this if you're on Swift 6. It will use lldb-dap by default, which is in the Swift 6 toolchain, and removes the need for CodeLLDB.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants