Debug Android Project like a PRO applying breakpoints♦️🔴

 


Debugging Android App has been always been a nightmare a newbies. As a beginner, we always run behind writing the code, developing the logic, being a fresher this is really good but once we start working in organisation, we come across various projects/use-cases which looks ambiguous to understand, here debugging comes into picture. If you came across this situation, this article if especially articulated for you.


In this article, I’ll walk you through debugging a code snippet in Android Studio using the Eclipse keymap. Let’s get started!”

[Step 1: Creating an Empty Project] First, Let’s create a default Empty Project in Android Studio, which is built using Jetpack Compose.

[Step 2: Configuring Eclipse Keymap] I’m targeting developers who use Eclipse keymap, which is available by default on Windows machines and can also be configured on Mac. So, let’s first set up Eclipse keymap in Android Studio. (Demonstration of configuring Eclipse keymap settings in Android Studio.)

[Step 3: Running the Project in Debug Mode] Now, let’s run the project in debug mode and explore how to navigate using shortcut keys.

  • “I’ll use F8 (with the function key) to navigate breakpoints one by one.”
  • “I’ll use F6 (with the function key) to step through the code line by line within a method.”

[Step 4: Evaluating Expressions] To check the current value stored in a variable, I select a specific part of the code and press Ctrl + U to evaluate the expression. Alternatively, you can right-click and choose the same option from the menu. (Demonstration of evaluating expressions and checking variable values.)

And that’s it! Now you know how to configure Eclipse keymap and use essential debugging shortcuts in Android Studio. I hope this helps! Don’t forget to like, share, and subscribe. See you in the next one!


Comments

Post a Comment

Popular posts from this blog

Optimize Jetpack Compose: Performance & Best Practices

Image
      Jetpack Compose offers a declarative approach to building UIs in Android. However, like any UI framework, optimization is key to achieving smooth performance and a great user experience. This detailed guide expands on the provided checklist, offering in-depth explanations and practical code examples for each optimization technique. I. Core Principles: Laying the Foundation for Performance Use Stable Types:  Compose relies on stable types to efficiently track changes and minimize recompositions. A stable type guarantees that if two instances of the type are equal according to  equals() , they will always be equal. Using unstable types can force unnecessary recompositions.   // Stable data class (recommended) data   class   User ( val  name: String,  val  age:  Int ) // Unstable list (avoid directly in Compose state) // Use SnapshotStateList instead val users = remember { mutableStateListOf<User>() } // Cor...
Read more

JIT vs AOT Compilation | Android Runtime

Image
           D id you ever think, what happens when you install your app in your Android device, it shows INSTALLING for fraction of second and app get opens. What happens exactly behiend the scene? Found Interesting???? Cool !!! let’s clear all the doubt in this blog. You would have definetely read the buzz words JIT(Just-in-time) and AOT(Ahead of time) at many ocassions. We’ll dig it down in details in this article, stay tuned…. Android apps run on Android Runtime (ART) , which replaced Dalvik since Android 5.0 (Lollipop). ART supports both JIT (Just-In-Time) Compilation and AOT (Ahead-Of-Time) Compilation to improve performance and efficiency. JIT (Just-In-Time) Compilation How it Works: Compiles bytecode into native machine code at runtime (when the app is executed). Stores frequently used methods in memory to speed up subsequent executions. Advantages: Faster app installation because it doesn’t require full compilation beforehand. Reduces s...
Read more

From ‘Master’ to ‘Main’: The Meaning Behind Git’s Naming Shift

Image
                             Git changed its default branch name from master to main due to concerns about inclusivity and to remove references to terms with problematic historical connotations. The term master has been associated with slavery, and many tech communities sought to use more neutral and inclusive language. Reason for the Change: Inclusivity & Sensitivity- Many organizations aimed to remove racially charged terminology from software development. Consistency Across Communities- Other projects and platforms, such as Github, Gitlab, and software frameworks, also made similar changes. Modern Naming Conventions- main is a cleaner and more intuitive name, as it represents the primary branch of a repository. Interesting Facts —  It wasn’t originally about slavery  — The term Git did not originate from the master/slave concept used in computing. It likely came from Bitkeeper , a version contro...
Read more