visual studio remote debugging error for local debugger

Give the permission set a name that you can remember, such as Debug Apex.In your browser, from Setup, enter Permission Sets in the Quick Find box, then select Permission Sets.In VS Code, run SFDX: Open Default Org.When your scratch org is ready, assign permissions for Apex Debugger to the org’s admin user.Choose a scratch org definition file that includes the DebugApex feature.In VS Code, run SFDX: Create a Default Scratch Org.Add the DebugApex feature to the scratch org definition files for all the types of scratch orgs that you plan to debug:.If you don’t have an Apex Debugger license, use the Replay Debugger. Note: You can use the default license provided to License Management orgs only with the ISV Customer Debugger to debug subscriber orgs. The first time that you use Apex Debugger in VS Code, complete these setup steps. To debug subscribers’ sandbox orgs, use ISV Customer Debugger, which is part of the Apex Interactive Debugger extension. Output your results to the Debug Console.Complete standard debugging actions, including step into, over, and out, and run to breakpoint.(When you inspect objects that have managed types that aren’t visible to you, only global variables are displayed in the variable inspection pane.)

Interact with global classes, exceptions, and triggers from your installed managed packages.

View the call stack, including triggers activated by Apex Data Manipulation Language (DML), method-to-method calls, and variables.

View variables, including sObject types, collections, and Apex System types.Set breakpoints in Apex classes and triggers.Apex Debugger allows customers to debug their Apex code in sandboxes and scratch orgs, in real time, using VS Code as the client.

Visual studio remote debugging error for local debugger