

Select and then click OK.Ī Debug pane appears at the bottom of Android Studio with a message that indicates that the debugger is attached to the target device or emulator.After the app runs on a device or emulator, click Attach Debugger to Android Process.Ī Choose Process dialog opens in which you can choose the process to which you want to attach the debugger.To attach the debugger to an app process, follow these steps: If your app is already running, you can attach the debugger to it. Once you're familiar with both ways, you can pick the one that you prefer or whichever one is required. Attach the debugger to an existing app process that runs on a device or emulator.īoth ways accomplish the same thing to a certain extent.There are two ways to run the debugger alongside your app: You can browse the code in the Github repository. Note: The starter code is on the main branch of the downloaded repository. $ cd basic-android-kotlin-compose-training-dice-roller

You can also skip the video and start the codelab instructions right away.Īlternatively, you can clone the Github repository for the code: $ git clone It's recommended to expand the video to full screen (with this icon in the lower right corner of the video) so you can see Android Studio and the code more clearly. If you'd like to watch one of the course instructors complete the codelab, play the below video.

It lets you specify points at which to suspend the execution of the code and manually interact with variables, methods, and other aspects of the code. The debugger is an essential tool that lets you inspect the execution of the code that powers your Android app so that you can fix any bugs in it. This codelab teaches you how to use the debugger in Android Studio to inspect what happens in the Dice Roller app at runtime.
