salesforcedx-vscode
salesforcedx-vscode copied to clipboard
Running Interactive debugger doesn't show Variables
Hi Team,
I have an issue with Apex interactive debugger. This is my configuration
Version 60.10.0 VSCode version: Version: 1.88.1 (Universal) Commit: e170252f762678dec6ca2cc69aba1570769a5d39 Date: 2024-04-10T17:42:52.765Z Electron: 28.2.8 ElectronBuildId: 27744544 Chromium: 120.0.6099.291 Node.js: 18.18.2 V8: 12.0.267.19-electron.0 OS: Darwin arm64 23.4.0
Salesforce CLI version: @salesforce/cli/2.38.7 darwin-arm64 node-v20.12.2
The Launch.json is as follows: { // 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 Debugger", "type": "apex", "request": "launch", "salesforceProject": "${workspaceRoot}" } ] }
My problem is that when I enable the Integrative debugging VSCode connects to the Salesforce sandbox, but Visual Studio won't show the three sections 'Variables' 'Watch', and so on. Occasionally, however, it does show the sections but when I do a step-by-step debugging the variables of my APEX classes will not show up. The 'Variable' section is empty.
Thank you for any suggestion you might have. Giancarlo
Summary
Short summary of what is going on or to provide context.
Steps To Reproduce:
- This is step 1.
- This is step 2. All steps should start with '1.'
Expected result
Describe what should have happened.
Actual result
Describe what actually happened instead.
Additional information
Feel free to attach a screenshot.
Salesforce Extension Version in VS Code:
SFDX CLI Version:
OS and version:
VS Code version:
Hi @gamatibrightcove, Can you provide us with the org ID for your org? And if it's a sandbox or scratch org, can we also have the org ID of the production org that created it?
Hi I am currently working in this sandbox: 00D750000000MaC
created from this prod: 00D8c000002JFrH
Thank you. GC
@gamatibrightcove Our team has faced this issue while testing, and we are aware of the inconsistencies in the product. We are investigating it and will let you know when we have more updates.
@daphne-sfdc Thank you very much. If I can say, the whole Salesforce Extention package looks a lot slower from the version 60.10 . If I have the 'detect conflicts' enabled when saving the Apex classes, it slows down so much that I had to disable it. Also, in order to be able to work a bit faster, I had to recreate another workspace brand new. Altought that mitigated the issue, (but it hasn't fixed the debugger), VSCode with the Salesforce Extention Pack and Salesforce CLI Integration is still rather slow. Thank you for working on this. GC
Hi @gamatibrightcove -
Thanks for reporting your experience. We are making effort to optimize the extensions. The extension pack will be reduced from 173 MB to 114 MB in the next week's release and there are other ongoing optimization to be released in the next couple of weeks. We value your experience and look forward to your feedback soon.
Error while creating work item!