android studio debug breakpoint not working

Check to see that you're debugging the right code.

Confirm that you're debugging the right process.

If your module isn't loaded, check the following to find the cause: Delete the file and run a clean build of the module to try to resolve the issue. Confirm you're working with a full PDB and not a stripped PDB. Stripped PDBs don't contain source file information.

It's possible to create stripped PDBs using the /PDBSTRIPPED linker option.

If your source files were recently added, confirm that an up-to-date version of the module is being loaded.

If symbols are loaded, the PDB doesn't contain information about your source files.

For more information about loading symbols, see Specify Symbol (.pdb) and Source Files. to see where the debugger looked to try and load symbols. From the context menu on a module in the Modules window, select Symbol Load Information.

If symbols aren't loaded, check the symbol status to diagnose the issue.

If your module is loaded, check the Symbol Status column to see whether symbols have been loaded. Go to the Modules window ( Debug > Windows > Modules) and check whether your module is loaded.

'No Symbols have been loaded for this document' The following two sections describe prominent warnings and how to fix them. To determine the difference, hover over the breakpoint and see if there's a warning.

A hollow (white filled) circle, either the breakpoint is disabled or warning occurred when trying to set the breakpoint.

A solid red circle, if the debugger successfully set a breakpoint in the target process.

When debugging, a breakpoint has two possible visual states: Applies to: Visual Studio Visual Studio for Mac Visual Studio Code Breakpoint Warnings

Android studio debug breakpoint not working