forcedotcom / salesforcedx-vscode

Salesforce Extensions for VS Code
https://developer.salesforce.com/tools/vscode
BSD 3-Clause "New" or "Revised" License
954 stars 406 forks source link

V.62.0.0 APEX interactive Debugger not working #5896

Open gamatibrightcove opened 1 week ago

gamatibrightcove commented 1 week ago

Summary

I reported this multiple times, but all the newer versions seems not working. The APEX interactive debugger doesn't show anything. it looks completely broken. It doesn't show the variables, the call stack sections and even less the APEX statement with the breakpoint.

Steps To Reproduce:

  1. Create a Project with Manifest from one of your Salesforce Sandbox
  2. Create any trigger on any of the object, In my case a BEFORE_UPDATE trigger on CONTACT
  3. Set a breakpoint on your code and make sure you have assigned yourself the APEX Debug permission set in your sandbox
  4. Configure the LAUNCH.Json as per the following:

"version": "0.2.0", "configurations": [

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

] }

Then run start the debugging and do something on your record that triggers the APEX.

Expected result

The Variable, Watch and Call Stack panels on the left side of VSCode are totally empty

Actual result

I expect to see the list of Variables of the APEX code based on their scope visibility, and evaluated with the correct values.

Additional information

Screenshot 2024-10-14 at 16 02 50 Screenshot 2024-10-14 at 16 03 13

Salesforce Extension Version in VS Code: V.62.0.0 Apex Interactive Debugger V.62.0.0 Salesforce CLI Intergration V.62.0.0 Salesforce Extension Pack

Salesforce CLI Version: 2.61.8 darwin-arm64 node-v20.17.0

OS and version: Ventura 13.2.1 (22D68)

VS Code version: Version: 1.94.2 (Universal) Commit: 384ff7382de624fb94dbaf6da11977bba1ecd427 Date: 2024-10-09T16:08:44.566Z Electron: 30.5.1 ElectronBuildId: 10262041 Chromium: 124.0.6367.243 Node.js: 20.16.0 V8: 12.4.254.20-electron.0 OS: Darwin arm64 22.3.0

Most recent version of the extensions where this was working: I DON'T KNOW!

svc-idee-bot commented 1 week ago

Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.

svc-idee-bot commented 1 week ago

Hello @gamatibrightcove :wave: It looks like you didn't provide all the required basic info in your issue.

If you haven't already, please provide the following info: Salesforce Extension Version in VS Code: Salesforce CLI Version: OS and version: VS Code version: Most recent version of the extensions where this was working:

Here's an example of a set of required info that will pass the validation: Salesforce Extension Version in VS Code: 60.13.0 Salesforce CLI Version: @salesforce/cli/2.42.6 darwin-arm64 node-v18.18.2 OS and version: MacOS Sonoma 14.5 VS Code version: 1.89.1 Most recent version of the extensions where this was working: 60.11.0

A few more things to check:

Thank you!

gamatibrightcove commented 1 week ago

Please, this BOT is wrong I provided all the information required in the section!

AnanyaJha commented 6 days ago

Hi @gamatibrightcove- thanks for sharing this info. Based on the information you've provided, it looks like you're running into a known issue with the Interactive Debugger not working in Hyperforce. At this point, we don't have a workaround but we'll let you know as soon as we have any further information.

fyi - @rsensharma

gamatibrightcove commented 5 days ago

Hi @AnanyaJha @rsensharma Thank you for getting back to me. I am just curious now :) is it because SFDC sandbox and orgs are on Hyperforce (whatever that is) that the interactive debugger stopped working for all the versions? I'm really just curious here if anyone has a hint of what it could be.

Aren't all the Salesforce Extensions and Packages for VSCode developed by Salesforce too?

Thank you for the information. GC

github-actions[bot] commented 2 days ago

This issue has not received a response in 3 days. It will auto-close in 2 days unless a response is posted.

gamatibrightcove commented 22 hours ago

Hi, I replied back why is it closing down? GC