Unable to launch Apex Debugger

[jhuizenga]

When trying to launch the Apex Debugger from vscode, is does not launch.

I have used the standard configuration as found in the documentation, but is does nothing. I dit create a permissionset en assign it. In our production org I cannot find any information about a session being started/used.

{
	"configurations": [
		{
			"name": "Launch Apex Debugger",
			"type": "apex",
			"request": "launch",
			"sfdxProject": "${workspaceRoot}"
		}
	]
}

I have used the debugger succesfully a number of times with vscode, but in the past months I have not been able to use it anymore.

Steps To Reproduce:

1. Push the ' Start debugging' button in VSCode

Expected result

Apex debugger should have been started.

Actual result

The little blue line underneath the button keeps running around:

Details

VS Code Version:
1.28.2 (user setup)

SFDX CLI Version:
sfdx-cli/6.38.0-0d66175ccf (windows-x64) node-v8.9.4

OS and version:
Windows 10 Enterprise

Internal Work Item:
W-5622038

[lcampos]

@jhuizenga thanks for reporting this. We are aware of it and currently working on a fix. I'll make sure to update this issue to let you know when the fix is going out.

[lcampos]

@jhuizenga could you confirm the following. You're able to deploy and run other commands that interact with the org. Do you get any error message in vscode's Output view or Debug Console view ? I want to make sure the fix we're working on is in fact the same as what you're experiencing. Thanks.

[nlrisbell]

The same issue is occurring for us in VSCode 1.29.0. Other commands seem to work fine in the scratch org and we have been using Interactive Debugger for a long time without errors. I upgraded VSCode and have re-installed the SF Extension Pack with the Interactive and Replay debuggers (v. 44.6.1) and no luck. I do get a popup on launch that has no info.

[lcampos]

Thanks for the info @nlrisbell, we were able to find a way to replicate the issue and we're working on getting a fix out. Apologies for the problems this has caused, we'll keep this thread up to date.

[lcampos]

@jhuizenga @nlrisbell we've release the fix for this as part of version 44.7.0 of the extensions. Thanks for being patient and let us know if you run into any other issues.

[nlrisbell]

That is delightful, @lcampos - thanks for your quick fix!! I am surprised there is not more discussion of this - isn't the Apex Debugger in high use? I see the 44.7.0 extension already - will test now. Fixed! :-)

[lcampos]

Awesome, thanks for confirming it's working for you now.

We see more people using the Apex Replay Debugger since Apex Debugger requires a license, so that could be it but please keep opening issues for bugs or feature requests.

[lflorezcyberark]

I am having a similar issue with version 44.7.0. I am connected to a Sandbox ORG and I am able to deploy from a project locally to the ORG, however when I am triggering the command SFDX: Turn on Apex debug log for Replay Debugger, I get the following error message:

`{"message":"Provided external ID field does not exist or is not accessible: null","status":1,"stack":"NOT_FOUND: Provided external ID field does not exist or is not accessible: null\n at HttpApi.getError (C:\Users\luis_\AppData\Local\sfdx\client\node_modules\jsforce\lib\http-api.js:250:13)\n at C:\Users\luis_\AppData\Local\sfdx\client\node_modules\jsforce\lib\http-api.js:95:22\n at tryCallOne (C:\Users\luis_\AppData\Local\sfdx\client\node_modules\promise\lib\core.js:37:12)\n at C:\Users\luis_\AppData\Local\sfdx\client\node_modules\promise\lib\core.js:123:15\n at flush (C:\Users\luis_\AppData\Local\sfdx\client\node_modules\asap\raw.js:50:29)\n at _combinedTickCallback (internal/process/next_tick.js:131:7)\n at process._tickCallback (internal/process/next_tick.js:180:9)","name":"NOT_FOUND","warnings":["All --json output, including on error, is moving to stdout. Use the SFDX_JSON_TO_STDOUT environment variable to move over to the new functionality. This will become the default in version 45."]}

SFDX: Turn On Apex Debug Log for Replay Debugger ended with exit code 1`

I am also able to download a debug log from VS Code but launching from the .log downloaded doesn't do anything.

This is my launch.json:

{ // Use IntelliSense to learn about possible attributes. // Hover to view descriptions of existing attributes. // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387 "version": "0.2.0", "configurations": [ { "name": "Launch Apex Replay Debugger", "type": "apex-replay", "request": "launch", "logFile": "07L3C000005c8RgUAI_20181119115110.log", "stopOnEntry": true, "trace": true } ] }

07L3C000005c8RgUAI_20181119115110.log is the downloaded log file.

[lcampos]

hi @lflorezcyberark please open a new issue for that since it's unrelated to this one; this was an issue with Apex Debugger and the issue you are experiencing is with Apex Replay Debugger.

As part of the new issue add the details you have here and include which version of vscode you are on and operative system you are working with. Thanks.

[jhuizenga]

@lcampos thnx for fixing this issue. I'm sorry for not replying on this issue earlier.. notifications went to my spam folder without me noticing it. I'll give it a try again today to see if my issue disappeared!

[jhuizenga]

I can confirm it is working again! 👍

[maimoona-shahid]

Same Launching error appearing in Version 1.54.1 , it keeps loading but nothing happens.

[SidTrailhead]

Awesome, thanks for confirming it's working for you now.

We see more people using the Apex Replay Debugger since Apex Debugger requires a license, so that could be it but please keep opening issues for bugs or feature requests.

Hi @lcampos ,
I am still facing the issue.

When I click on Launch Apex Replay debugger, nothing really happens.
Please suggest what to do.
I am using version v51.8.0