Open nkskaare opened 5 days 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.
Hello @nkskaare :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:
Developer: Toggle Developer Tools
in the command palette.Thank you!
Developer tools logs no error when trying to set the breakpoint, but the following error message is displayed when debugging session is finished.
Summary
Unable to stop at breakpoints with Apex Replay Debugger in a repo with multiple packages defined in sfdx-project.json.
Steps To Reproduce:
Update: Tried reproducing the issue with a simpler project structure than I have in the repo where it is failing, I am currently unable to reproduce, even though I am running in the same devcontainer environment. Any insight into how to further debug this is appreciated.
Expected result
Regular breakpoint, which debugger can be stopped at.
Actual result
Breakpoint is greyed out, saying unverified breakpoint.
Additional information
Salesforce Extension Version in VS Code: v62.5.1
Salesforce CLI Version: @salesforce/cli/2.46.6 linux-x64 node-v18.20.4
OS and version: Ubuntu 22.04.5 LTS (Docker devcontainer)
VS Code version: 1.95.3
Most recent version of the extensions where this was working: v62.5.1 (Unsure. Tried reproducing the issue in the same type of container with a simpler project structure and it worked.)