![]() I see somebody else solved the issue after adding the following line to their gradle.properties file. Unfortunately, sometimes these steps are not enough, or simply donât work, the debugger wonât hit your breakpoints. Now, click on the Debug icon in the Toolbar (having selected the previously created AnnotationProcessorDebugger configuration) and the debugger will hit your breakpoints! Additional info You will see the process will start and suddenly stop on > Starting Daemon waiting for you to do something. A Devices page similar to the following opens. Replace APP_MODULE_NAME with the name of the module having annotations which you want to debug. In your Google Chrome browser, enter chrome://inspect/devices in the URL field. ![]() gradlew -no-daemon =true :APP_MODULE_NAME:clean :APP_MODULE_NAME:compileDebugJavaWithJavac Run adb connect :5555 If you run adb devices again, you should see your device.Go to the Settings -> About phone -> Status to view the IP address of your phone. Run adb tcpip 5555 Disconnect your device (remove the USB cable). Setup your breakpoints wherever you need them and then run this command from the terminal. You can check if it shows up when running adb devices. ![]() Check if the device notification bar displays the message USB debugging. Then click View > Command Palette menu item. Open visual studio code, then click File > Open and select the above folder. Create a folder named VisualStudioCodeWorkSpace.
0 Comments
Leave a Reply. |