Android Debugging: Troubleshooting Errors & Crash Diagnoses

Every developer spends a significant portion of their career debugging code. When your application crashes or Gradle fails to build, understanding how to read Logcat stack traces and diagnose build logs separates amateur programmers from seasoned engineers.

Top 6 Most Common Android Crashes & Exact Fixes

1. NullPointerException (NPE)

Cause: Attempting to invoke a method on an object reference that is null.

Fix: Migrate code to Kotlin non-nullable types, use safe calls object?.method(), and provide fallbacks via the Elvis operator ?:.

2. ActivityNotFoundException

Cause: Calling startActivity(intent) where the Activity is not declared in the manifest.

Fix: Add <activity android:name=".MyActivity" android:exported="false" /> inside AndroidManifest.xml.

3. NetworkOnMainThreadException

Cause: Performing an HTTP request or socket read directly on the main UI thread.

Fix: Wrap network calls in Kotlin Coroutines with withContext(Dispatchers.IO) {}.

4. OutOfMemoryError (OOM)

Cause: App heap memory exhausted, usually from decoding full-resolution camera bitmaps.

Fix: Use Coil or Glide for automatic downsampling, and use LeakCanary to detect leaked Activity contexts.

5. SecurityException (Permission Denied)

Cause: Calling sensitive APIs (Camera, Location) without asking for runtime permission.

Fix: Declare permission in AndroidManifest.xml AND request at runtime via ActivityResultContracts.RequestPermission().

6. Gradle Sync Failed: Unsupported Java Version

Cause: Project requires Java 17/21, but Android Studio is pointing to an older Java 8/11 JDK.

Fix: In Android Studio, go to Settings > Build, Execution, Deployment > Build Tools > Gradle and set Gradle JDK to embedded JDK 17 or 21.

Mastering Android Studio Logcat 2.0

Logcat displays system messages and custom debug logs. Use Logcat query syntax to isolate crashes instantly:

package:mine level:error — Filters logs to display only uncaught exceptions from your own app package.
tag:MyTag — Filters output to logs emitted by Log.d("MyTag", "...").
is:crash — Isolates the fatal crash stack trace showing the exact class and line number of the failure.

Frequently Asked Questions (FAQ) - Student & Interview Review

Q1. What is the difference between Log.v, Log.d, Log.i, Log.w, and Log.e?

They represent logging severity levels: **Verbose** (v), **Debug** (d), **Info** (i), **Warn** (w), and **Error** (e). Debug logs are typically stripped from production release builds using ProGuard/R8 rules.

Q2. How do I fix 'Installed Build Tools revision is corrupted' in Gradle?

Open `Tools > SDK Manager > SDK Tools`, uncheck the problematic Build-Tools version, click Apply to uninstall, then check it again and click Apply to re-download a fresh copy.

Q3. How do I set breakpoints and inspect variables in Android Studio?

Click in the gutter next to any line of code to set a red breakpoint dot. Click the **Debug App** icon (green bug). When execution hits the breakpoint, the debugger pauses the thread, allowing you to evaluate expressions, inspect variable memory values, and step over lines.