Is your feature request related to a problem? Please describe.
When trying to launch Debug for any test method on Full sandbox org - I get "Debug test(s) failed to run message, no logs are saved in project folder.
The tests run normally. Happens for org refreshed last November, other old (2022) and new development orgs are fine, PROD is fine. Happens for other sf admins as well on the org. Happens for all test methods.
Apex Interactive Debugger: v60.13.0
Salesforce Extension Pack v59.9.0
VS Code: 1.89.1
The problem seems to be there for last two months. I do not recall performing any updates to extensions or vs code manually.
Describe the solution you'd like
Please help or at least let me know where I can go with the problem or where I can find any logs on VS debug functionality to debug by myself at least.
Describe alternatives you've considered
There are really no alternatives except from putting every variable in assert to find out what it is but this obviously no long-term solution.
Thank you for filing this feature request. We appreciate your feedback and will review the feature at our next grooming session. We prioritize feature requests with more upvotes and comments.
Is your feature request related to a problem? Please describe. When trying to launch Debug for any test method on Full sandbox org - I get "Debug test(s) failed to run message, no logs are saved in project folder. The tests run normally. Happens for org refreshed last November, other old (2022) and new development orgs are fine, PROD is fine. Happens for other sf admins as well on the org. Happens for all test methods. Apex Interactive Debugger: v60.13.0 Salesforce Extension Pack v59.9.0 VS Code: 1.89.1
The problem seems to be there for last two months. I do not recall performing any updates to extensions or vs code manually.
Describe the solution you'd like Please help or at least let me know where I can go with the problem or where I can find any logs on VS debug functionality to debug by myself at least.
Describe alternatives you've considered There are really no alternatives except from putting every variable in assert to find out what it is but this obviously no long-term solution.
Additional context