No delegateCommandHandler for vscode.java.startDebugSession

[KrithikPatil]

My application is started, the extensions show a disable button, so I assume the extensions are also activated but I still the get "No delegateCommandHandler for vscode.java.startDebugSession" this error, why? Can anyone please solve this?

[github-actions]

Hi @KrithikPatil, I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.

Solution

• Make sure you’re running the latest Language Support for Java and Debugger for Java extensions (v0.49.0 or later). An important fix for this exact error was shipped in vscode-java 0.49.0.
  • Changelog: https://github.com/redhat-developer/vscode-java/blob/master/CHANGELOG.md#0490-september-18th-2019
• After updating, reload VS Code and restart the Java Language Server:
  1. Open the Command Palette (⇧⌘P / Ctrl+Shift+P).
  2. Run Java: Clean the Java language server workspace.
  3. Reload Window.
• If the problem persists, consult the official troubleshooting guide:
  • https://github.com/microsoft/vscode-java-debug/blob/master/Troubleshooting.md#no-delegatecommandhandler-for-vscodejavastartdebugsession-when-starting-debugger

Duplicate Issue

• No delegateCommandHandler for vscode.java.startDebugSession when starting Debugger #728

  “No delegateCommandHandler for vscode.java.startDebugSession when starting Debugger”

Other references with low confidence

• Get Error "No delegateCommandHandler for 'xxx'" eclipse-jdtls/eclipse.jdt.ls#1146 (comment)
  • Describes a caching issue in jdt.ls’s WorkspaceExecuteCommandHandler that can trigger “No delegateCommandHandler …”.

The team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!