{"id":89,"date":"2026-10-09T11:43:00","date_gmt":"2026-10-09T11:43:00","guid":{"rendered":"https:\/\/moiks.com\/blog\/?p=89"},"modified":"2026-11-06T08:48:44","modified_gmt":"2026-11-06T08:48:44","slug":"android-logcat-debugging-explained-complete-beginner-guide","status":"publish","type":"post","link":"https:\/\/moiks.com\/blog\/android-logcat-debugging-explained-complete-beginner-guide\/","title":{"rendered":"Android Logcat &#038; Debugging Explained: Complete Beginner Guide"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">When developing Android applications with <strong>Kotlin and Jetpack Compose<\/strong>, errors are a normal part of the development process.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Sometimes your application may crash unexpectedly. A button might not respond, a screen might display incorrect data, or an API request might fail.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">How do Android developers identify these problems?<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The answer is <strong>Android Studio Logcat and debugging tools<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Android Studio provides powerful tools to inspect application behavior, monitor logs, analyze exceptions, and debug Kotlin code.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In this tutorial, we&#8217;ll learn how to use Android Logcat, understand logging levels, investigate crashes, and debug applications using breakpoints.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">What You&#8217;ll Learn<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">By the end of this tutorial, you&#8217;ll understand:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>What Android Logcat is<\/li>\n\n\n\n<li>Why logging is important<\/li>\n\n\n\n<li>How to open Logcat in Android Studio<\/li>\n\n\n\n<li>Android logging levels<\/li>\n\n\n\n<li><code>Log.v()<\/code>, <code>Log.d()<\/code>, <code>Log.i()<\/code>, <code>Log.w()<\/code>, and <code>Log.e()<\/code><\/li>\n\n\n\n<li>How to filter Logcat messages<\/li>\n\n\n\n<li>How to identify Android application crashes<\/li>\n\n\n\n<li>How to read exception stack traces<\/li>\n\n\n\n<li>How to use breakpoints<\/li>\n\n\n\n<li>How to inspect variables<\/li>\n\n\n\n<li>How to debug Kotlin and Jetpack Compose applications<\/li>\n\n\n\n<li>Debug vs Release builds<\/li>\n\n\n\n<li>Common debugging mistakes<\/li>\n\n\n\n<li>Android debugging best practices<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Let&#8217;s begin.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">1. What is Android Logcat?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Logcat is a debugging tool that displays system and application log messages from an Android device or emulator.<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It helps developers understand what is happening while an application is running.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, Logcat can display:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Application startup messages<\/li>\n\n\n\n<li>Debug information<\/li>\n\n\n\n<li>Warning messages<\/li>\n\n\n\n<li>Exceptions<\/li>\n\n\n\n<li>Application crashes<\/li>\n\n\n\n<li>Android framework messages<\/li>\n\n\n\n<li>Custom logs written by developers<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Simple explanation<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Think of Logcat as a window into your application&#8217;s behavior.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Android Application\n        |\n        v\nApplication Events\n        |\n        v\nLog Messages\n        |\n        v\nAndroid Studio Logcat\n        |\n        v\nDeveloper Investigates<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">When something goes wrong, Logcat is often one of the first tools Android developers use.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">2. Why is Logcat Important?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Imagine you&#8217;re developing a Jetpack Compose application.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The application launches successfully, but clicking a button doesn&#8217;t produce the expected result.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Without debugging tools, you might not know what went wrong.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Using Logcat, you can inspect whether the button click is being triggered.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Log.d(\"MainScreen\", \"Button clicked\")<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">When the user taps the button, the message appears in Logcat.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This helps confirm that the click handler executed.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Logging is especially useful for:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Tracking application behavior<\/li>\n\n\n\n<li>Investigating errors<\/li>\n\n\n\n<li>Understanding lifecycle events<\/li>\n\n\n\n<li>Debugging user interactions<\/li>\n\n\n\n<li>Monitoring development-time operations<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">3. How to Open Logcat in Android Studio<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Follow these steps:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Step 1:<\/strong> Open your Android project in Android Studio.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Step 2:<\/strong> Run the application on an Android emulator or physical device.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Step 3:<\/strong> Open the Logcat tool window.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Navigate to:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>View \u2192 Tool Windows \u2192 Logcat<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Step 4:<\/strong> Select the correct device.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Step 5:<\/strong> Select your application&#8217;s process or apply an appropriate Logcat filter.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">You should now see log messages from the connected Android device.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Important<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Logcat may contain thousands of messages from Android system components and other applications.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Filtering helps you focus on relevant messages.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">4. Android Logging Levels Explained<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Android provides several logging levels.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Each level represents the importance or severity of a message.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><th>Level<\/th><th>Kotlin Method<\/th><th>Purpose<\/th><\/tr><tr><td>Verbose<\/td><td><code>Log.v()<\/code><\/td><td>Detailed diagnostic information<\/td><\/tr><tr><td>Debug<\/td><td><code>Log.d()<\/code><\/td><td>Development and debugging<\/td><\/tr><tr><td>Info<\/td><td><code>Log.i()<\/code><\/td><td>General informational messages<\/td><\/tr><tr><td>Warn<\/td><td><code>Log.w()<\/code><\/td><td>Potential problems<\/td><\/tr><tr><td>Error<\/td><td><code>Log.e()<\/code><\/td><td>Errors and failures<\/td><\/tr><tr><td>Assert<\/td><td><code>Log.wtf()<\/code><\/td><td>Conditions that should never occur<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Let&#8217;s understand each level.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">5. Log.v() \u2014 Verbose Logging<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Verbose logging is used for highly detailed diagnostic messages.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Log.v(\n    \"MainActivity\",\n    \"Verbose log message\"\n)<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Verbose messages can help investigate detailed application behavior.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, excessive logging can make debugging difficult.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Use verbose logging selectively.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">6. Log.d() \u2014 Debug Logging<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Debug logging is one of the most commonly used logging methods during development.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Log.d(\n    \"MainActivity\",\n    \"Application started\"\n)<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">You can also log variable values.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>val username = \"Alex\"\n\nLog.d(\n    \"UserScreen\",\n    \"Username: $username\"\n)<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Expected output:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>D\/UserScreen: Username: Alex<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">When should you use Log.d()?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Use debug logs when investigating:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Button clicks<\/li>\n\n\n\n<li>Screen navigation<\/li>\n\n\n\n<li>Function execution<\/li>\n\n\n\n<li>State changes<\/li>\n\n\n\n<li>Development-time behavior<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Avoid logging passwords, access tokens, or sensitive personal information.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">7. Log.i() \u2014 Information Logging<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Information logging is useful for recording meaningful application events.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Log.i(\n    \"AppLifecycle\",\n    \"MainActivity started\"\n)<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Expected output:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>I\/AppLifecycle: MainActivity started<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">This can help track significant application events during development.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">8. Log.w() \u2014 Warning Logging<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Warning logs indicate potential problems that may not immediately cause the application to crash.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>val username = \"\"\n\nif (username.isEmpty()) {\n\n    Log.w(\n        \"Validation\",\n        \"Username is empty\"\n    )\n}<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Expected output:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>W\/Validation: Username is empty<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Warnings can help identify unexpected situations before they become serious problems.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">9. Log.e() \u2014 Error Logging<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Error logs are used when an operation fails.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Log.e(\n    \"Network\",\n    \"Failed to load data\"\n)<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Expected output:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>E\/Network: Failed to load data<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">You can also log exceptions.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>try {\n\n    val result = 10 \/ 0\n\n    Log.d(\"Calculation\", \"Result: $result\")\n\n} catch (exception: ArithmeticException) {\n\n    Log.e(\n        \"Calculation\",\n        \"Calculation failed\",\n        exception\n    )\n}<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Here, the exception is passed as the third argument.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This allows Logcat to display the exception details and stack trace.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">10. Complete Android Logging Example<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Let&#8217;s create a simple Activity that demonstrates multiple logging levels.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>class MainActivity : ComponentActivity() {\n\n    private val tag = \"MoiksDebug\"\n\n    override fun onCreate(\n        savedInstanceState: Bundle?\n    ) {\n        super.onCreate(savedInstanceState)\n\n        Log.v(tag, \"Verbose message\")\n\n        Log.d(tag, \"Debug message\")\n\n        Log.i(tag, \"Information message\")\n\n        Log.w(tag, \"Warning message\")\n\n        Log.e(tag, \"Error message\")\n\n        setContent {\n            MyFirstAppTheme {\n                DebugExampleScreen()\n            }\n        }\n    }\n}<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Required import<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>import android.util.Log<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Replace <code>MyFirstAppTheme<\/code> with your project&#8217;s theme function.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Expected Logcat output<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>V\/MoiksDebug: Verbose message\nD\/MoiksDebug: Debug message\nI\/MoiksDebug: Information message\nW\/MoiksDebug: Warning message\nE\/MoiksDebug: Error message<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The exact formatting depends on your Android Studio version and Logcat settings.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">11. How to Filter Logcat Messages<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Android Logcat displays messages from many processes.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Filtering allows you to focus on relevant information.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Suppose you use:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Log.d(\n    \"MoiksDebug\",\n    \"Button clicked\"\n)<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">In the modern Logcat query field, you can filter by tag:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>tag:MoiksDebug<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">You can also filter by your application package:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>package:mine<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Or filter by minimum log level:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>level:ERROR<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">These filters make it easier to find useful messages.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Example<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>tag:MoiksDebug level:DEBUG<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">This filters messages using the specified tag and a minimum debug level.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">12. What is an Android Application Crash?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">An application crash occurs when an unhandled error or another fatal condition causes the application process to terminate.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>val number = \"Hello\".toInt()<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">This code attempts to convert non-numeric text into an integer.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It throws a <code>NumberFormatException<\/code>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If the exception is not handled, the application may crash.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Typical crash output<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>FATAL EXCEPTION: main\n\njava.lang.NumberFormatException:\nFor input string: \"Hello\"<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The complete stack trace normally contains additional information about where the exception occurred.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">13. How to Read Android Stack Traces<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A stack trace shows the chain of function calls associated with an exception.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>FATAL EXCEPTION: main\n\njava.lang.NumberFormatException:\nFor input string: \"Hello\"\n\nat java.lang.Integer.parseInt(...)\nat com.example.myapp.MainActivity.onCreate(MainActivity.kt:25)<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">This tells us:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Exception type<\/strong><\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>NumberFormatException<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Problem<\/strong><\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>For input string: \"Hello\"<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Relevant application location<\/strong><\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>MainActivity.kt:25<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The file and line number can help identify the code responsible for the error.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Debugging tip<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">When investigating a stack trace, look for relevant frames from your application&#8217;s package.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Framework and library frames may also matter, but your application&#8217;s code is often a useful starting point.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">14. Fixing a NumberFormatException<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Consider this unsafe code:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>val age = \"Hello\".toInt()<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If the string isn&#8217;t a valid integer, it throws an exception.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A safer approach is:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>val age = \"Hello\".toIntOrNull()<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The result is:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>null<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">instead of throwing a <code>NumberFormatException<\/code> for invalid input.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>val age = \"25\".toIntOrNull()\n\nif (age != null) {\n\n    Log.d(\n        \"Validation\",\n        \"Valid age: $age\"\n    )\n\n} else {\n\n    Log.w(\n        \"Validation\",\n        \"Invalid age entered\"\n    )\n}<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">This is a simple example of how understanding an exception can help you write safer Kotlin code.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">15. What is Debugging in Android Studio?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Debugging is the process of investigating application behavior to identify and fix problems.<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Android Studio includes an integrated debugger that allows you to:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Pause application execution<\/li>\n\n\n\n<li>Set breakpoints<\/li>\n\n\n\n<li>Inspect variable values<\/li>\n\n\n\n<li>Step through code<\/li>\n\n\n\n<li>Examine function calls<\/li>\n\n\n\n<li>Evaluate expressions<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Instead of relying only on log messages, you can inspect the application&#8217;s state while the code is executing.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">16. What is a Breakpoint?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A breakpoint tells the debugger to pause execution when a particular line of code is reached.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>fun calculateTotal(\n    price: Int,\n    quantity: Int\n): Int {\n\n    val total = price * quantity\n\n    return total\n}<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Suppose you place a breakpoint on:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>val total = price * quantity<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">When the debugger reaches that line, execution pauses.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">You can inspect:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>price = 100\n\nquantity = 3<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Then step over the calculation and inspect:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>total = 300<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Breakpoints help you understand exactly what your application is doing.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">17. How to Add a Breakpoint in Android Studio<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Follow these steps:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Step 1:<\/strong> Open a Kotlin source file.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Step 2:<\/strong> Find the line you want to inspect.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Step 3:<\/strong> Click the gutter next to the line number.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A breakpoint marker appears.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Step 4:<\/strong> Start the application using the Debug action.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Step 5:<\/strong> Perform the action that triggers the breakpoint.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Android Studio pauses execution when the breakpoint is reached.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">You can now inspect variables and step through the code.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">18. Debugger Controls Explained<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Android Studio provides several debugger controls.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><th>Control<\/th><th>Purpose<\/th><\/tr><tr><td>Resume Program<\/td><td>Continue execution<\/td><\/tr><tr><td>Step Over<\/td><td>Execute the current line without stepping into called functions<\/td><\/tr><tr><td>Step Into<\/td><td>Enter a function call<\/td><\/tr><tr><td>Step Out<\/td><td>Finish the current function and return to its caller<\/td><\/tr><tr><td>Evaluate Expression<\/td><td>Evaluate an expression in the paused context<\/td><\/tr><tr><td>Stop<\/td><td>Stop the debugging session<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">These controls help you investigate how your application executes.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">19. Debugging Jetpack Compose Button Clicks<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Let&#8217;s create a simple Compose screen.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>@Composable\nfun DebugExampleScreen() {\n\n    var counter by remember {\n        mutableIntStateOf(0)\n    }\n\n    Column(\n        modifier = Modifier\n            .fillMaxSize()\n            .padding(24.dp),\n        verticalArrangement = Arrangement.Center,\n        horizontalAlignment = Alignment.CenterHorizontally\n    ) {\n\n        Text(\n            text = \"Counter: $counter\",\n            style = MaterialTheme.typography.headlineMedium\n        )\n\n        Spacer(\n            modifier = Modifier.height(20.dp)\n        )\n\n        Button(\n            onClick = {\n\n                counter++\n\n                Log.d(\n                    \"ComposeDebug\",\n                    \"Counter updated: $counter\"\n                )\n            }\n        ) {\n\n            Text(\"Increase Counter\")\n        }\n    }\n}<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Required imports<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>import android.util.Log\nimport androidx.compose.foundation.layout.Arrangement\nimport androidx.compose.foundation.layout.Column\nimport androidx.compose.foundation.layout.Spacer\nimport androidx.compose.foundation.layout.fillMaxSize\nimport androidx.compose.foundation.layout.height\nimport androidx.compose.foundation.layout.padding\nimport androidx.compose.material3.Button\nimport androidx.compose.material3.MaterialTheme\nimport androidx.compose.material3.Text\nimport androidx.compose.runtime.Composable\nimport androidx.compose.runtime.getValue\nimport androidx.compose.runtime.mutableIntStateOf\nimport androidx.compose.runtime.remember\nimport androidx.compose.runtime.setValue\nimport androidx.compose.ui.Alignment\nimport androidx.compose.ui.Modifier\nimport androidx.compose.ui.unit.dp<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Expected UI<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>+--------------------------------+\n|                                |\n|           Counter: 0           |\n|                                |\n|      &#91; Increase Counter ]      |\n|                                |\n+--------------------------------+<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">When you click the button, the counter increases.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Logcat displays:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>D\/ComposeDebug: Counter updated: 1\nD\/ComposeDebug: Counter updated: 2\nD\/ComposeDebug: Counter updated: 3<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Debugging exercise<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Place a breakpoint on:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>counter++<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Run the application in Debug mode.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Click the button and inspect the value of <code>counter<\/code>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is a simple way to practice debugging Compose state.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">20. Debugging Jetpack Compose State<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Jetpack Compose uses state to update the UI.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>var username by remember {\n    mutableStateOf(\"\")\n}<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">When the state changes, Compose may recompose the affected UI.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">While debugging Compose applications, pay attention to:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>State values<\/li>\n\n\n\n<li>State updates<\/li>\n\n\n\n<li>Button click handlers<\/li>\n\n\n\n<li>ViewModel state<\/li>\n\n\n\n<li>Recomposition behavior<\/li>\n\n\n\n<li>Navigation events<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Important<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A composable function can execute multiple times due to recomposition.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Avoid assuming that every composable execution represents a new screen launch or user interaction.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, logging directly in a composable body can produce repeated messages:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>@Composable\nfun ExampleScreen() {\n\n    Log.d(\n        \"ComposeDebug\",\n        \"Composable executed\"\n    )\n\n    Text(\"Hello Compose\")\n}<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">This can be useful temporarily while investigating recomposition, but it should not be treated as a reliable screen-view event.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">21. Debug vs Release Builds<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Android projects commonly have Debug and Release build types.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Debug build<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A Debug build is designed for development and testing.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It commonly supports:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Debugger attachment<\/li>\n\n\n\n<li>Development logging<\/li>\n\n\n\n<li>Breakpoints<\/li>\n\n\n\n<li>Debug-specific configuration<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Release build<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A Release build is intended for distribution.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It may include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Code shrinking<\/li>\n\n\n\n<li>Optimization<\/li>\n\n\n\n<li>Obfuscation<\/li>\n\n\n\n<li>Release signing<\/li>\n\n\n\n<li>Production configuration<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Example<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">You can restrict certain debug logs using:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>if (BuildConfig.DEBUG) {\n\n    Log.d(\n        \"MoiksDebug\",\n        \"Debug-only message\"\n    )\n}<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Depending on your Android Gradle configuration, you may need to enable generated <code>BuildConfig<\/code> fields and import your module&#8217;s <code>BuildConfig<\/code> class.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Important security practice<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Never log sensitive information such as:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Passwords<\/li>\n\n\n\n<li>Authentication tokens<\/li>\n\n\n\n<li>Private user messages<\/li>\n\n\n\n<li>Payment details<\/li>\n\n\n\n<li>Personal identification information<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Production logging should be minimal and privacy-conscious.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">22. Common Android Debugging Mistakes<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Mistake 1: Ignoring Logcat Errors<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">When an application crashes, review the exception and stack trace instead of randomly changing code.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Mistake 2: Logging Everything<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Excessive logs make useful information harder to find.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Use clear, meaningful tags and messages.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Mistake 3: Logging Sensitive Data<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Avoid printing passwords, tokens, or private user information.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Mistake 4: Not Using Breakpoints<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Logs are useful, but breakpoints allow you to inspect the actual execution state.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Mistake 5: Assuming Compose Runs Only Once<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Composable functions may recompose multiple times.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Understand state and recomposition before interpreting repeated logs.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Mistake 6: Ignoring Exceptions<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Avoid silently swallowing exceptions.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, this makes debugging difficult:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>try {\n    performOperation()\n} catch (exception: Exception) {\n    \/\/ Ignored\n}<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Handle expected failures appropriately and log useful diagnostic information during development without exposing sensitive data.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Mistake 7: Debugging the Wrong Process<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">If Logcat doesn&#8217;t show your expected messages, verify that you&#8217;ve selected the correct device and application process.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">23. Android Logcat Quick Reference<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><th>Method<\/th><th>Use Case<\/th><\/tr><tr><td><code>Log.v()<\/code><\/td><td>Detailed diagnostic messages<\/td><\/tr><tr><td><code>Log.d()<\/code><\/td><td>Debugging application behavior<\/td><\/tr><tr><td><code>Log.i()<\/code><\/td><td>Informational events<\/td><\/tr><tr><td><code>Log.w()<\/code><\/td><td>Potential problems<\/td><\/tr><tr><td><code>Log.e()<\/code><\/td><td>Errors and exceptions<\/td><\/tr><tr><td><code>Log.wtf()<\/code><\/td><td>Severe unexpected conditions<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\">Useful Logcat filters<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>tag:MoiksDebug<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>level:ERROR<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>package:mine<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Debugger shortcuts to remember<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Breakpoint: Click next to a line number.<\/li>\n\n\n\n<li>Debug: Run using the Debug action.<\/li>\n\n\n\n<li>Step Over: Execute the current line.<\/li>\n\n\n\n<li>Step Into: Enter a called function.<\/li>\n\n\n\n<li>Resume: Continue execution.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">24. Practical Exercises<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Try these exercises in Android Studio.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Exercise 1: Log Activity Lifecycle Events<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Add logs inside:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>onCreate()\nonStart()\nonResume()\nonPause()\nonStop()\nonDestroy()<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Run the application and observe the lifecycle messages.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Exercise 2: Debug a Compose Counter<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Create a counter screen.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Log the counter value whenever the user clicks the button.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Exercise 3: Use a Breakpoint<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Place a breakpoint inside a Kotlin function.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Inspect variable values before and after executing a calculation.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Exercise 4: Investigate an Exception<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">In a disposable practice project, deliberately trigger a <code>NumberFormatException<\/code>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Inspect the stack trace in Logcat.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Then fix the problem using:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>toIntOrNull()<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\">Exercise 5: Filter Logcat<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Create logs using the tag:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>MoiksDebug<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Filter Logcat to display only relevant messages.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">What We&#8217;ve Learned<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">In this tutorial, we learned:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>What Android Logcat is<\/li>\n\n\n\n<li>How to open Logcat<\/li>\n\n\n\n<li>Android logging levels<\/li>\n\n\n\n<li>How to write Kotlin log messages<\/li>\n\n\n\n<li>How to filter Logcat<\/li>\n\n\n\n<li>How to investigate application crashes<\/li>\n\n\n\n<li>How to understand stack traces<\/li>\n\n\n\n<li>How to use breakpoints<\/li>\n\n\n\n<li>How to inspect variables<\/li>\n\n\n\n<li>How to debug Jetpack Compose state<\/li>\n\n\n\n<li>Debug vs Release builds<\/li>\n\n\n\n<li>Logging security best practices<\/li>\n\n\n\n<li>Common Android debugging mistakes<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Understanding Logcat and debugging tools is an essential skill for every Android developer.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">As you build more complex applications using Jetpack Compose, ViewModel, Coroutines, Room, and Retrofit, these tools will become even more useful.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">What&#8217;s Next?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Now that we understand how to debug Android applications, we&#8217;ll explore another important topic:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Android Build Variants Explained: Debug, Release, Gradle &amp; APK vs AAB<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In the next tutorial, we&#8217;ll cover:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>What Android build variants are<\/li>\n\n\n\n<li>Debug and Release builds<\/li>\n\n\n\n<li>Android Gradle Plugin basics<\/li>\n\n\n\n<li>Build types<\/li>\n\n\n\n<li>Product flavors<\/li>\n\n\n\n<li>Version codes and version names<\/li>\n\n\n\n<li>APK vs Android App Bundle<\/li>\n\n\n\n<li>Signing configurations<\/li>\n\n\n\n<li>Build configuration best practices<\/li>\n\n\n\n<li>Preparing applications for Google Play<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Happy Coding!<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Continue learning modern Android development with <strong>Moiks Developer Blog<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Learn how to debug Android applications using Android Studio Logcat, Kotlin logging, breakpoints, and stack traces. A practical beginner guide with Jetpack Compose examples.<\/p>\n","protected":false},"author":1,"featured_media":90,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":0,"footnotes":""},"categories":[4,333],"tags":[],"class_list":["post-89","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-android-basics","category-android-tutorials"],"_links":{"self":[{"href":"https:\/\/moiks.com\/blog\/wp-json\/wp\/v2\/posts\/89","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/moiks.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/moiks.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/moiks.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/moiks.com\/blog\/wp-json\/wp\/v2\/comments?post=89"}],"version-history":[{"count":1,"href":"https:\/\/moiks.com\/blog\/wp-json\/wp\/v2\/posts\/89\/revisions"}],"predecessor-version":[{"id":91,"href":"https:\/\/moiks.com\/blog\/wp-json\/wp\/v2\/posts\/89\/revisions\/91"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/moiks.com\/blog\/wp-json\/wp\/v2\/media\/90"}],"wp:attachment":[{"href":"https:\/\/moiks.com\/blog\/wp-json\/wp\/v2\/media?parent=89"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/moiks.com\/blog\/wp-json\/wp\/v2\/categories?post=89"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/moiks.com\/blog\/wp-json\/wp\/v2\/tags?post=89"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}