You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I have been working with a few checkpoints, then remove them in VS Code, they're not automatically removed in the org during the easy debugging flow (Debug Test / Launch Apex Replay Debugger with the Current File)
Steps To Reproduce:
Toggle a few checkpoints and either run the Update Checkpoints command to update them in the org, debug a test, or use Launch Apex Replay Debugger with the Current File.
Remove all checkpoints in VS Code (Toggle Checkpoint, or delete by clicking them directly)
Debug at Test or Launch Apex Replay Debugger with the Current File
Notice that Update Checkpoints didn't run; code will still stop at the checkpoints with the replay debugger even though they don't exist in the UI anymore. If you open the Checkpoint Viewer in the Dev Console, you'll see they're still there as well.
Expected result
When running through Debug Test or Launch Apex Replay Debugger with Current File, checkpoints are removed.
Actual result
Checkpoints are not removed because VS Code thinks it doesn't have any checkpoints to work with.
Additional information
Salesforce Extension Version in VS Code: 54.8.0 OS and version: Mac 11.6.5
The text was updated successfully, but these errors were encountered:
Summary
When I have been working with a few checkpoints, then remove them in VS Code, they're not automatically removed in the org during the easy debugging flow (Debug Test / Launch Apex Replay Debugger with the Current File)
Steps To Reproduce:
Expected result
When running through Debug Test or Launch Apex Replay Debugger with Current File, checkpoints are removed.
Actual result
Checkpoints are not removed because VS Code thinks it doesn't have any checkpoints to work with.
Additional information
Salesforce Extension Version in VS Code: 54.8.0
OS and version: Mac 11.6.5
The text was updated successfully, but these errors were encountered: