⚡ Integrating LeakCanary in CI/CD - Automating Leak Detection

 

Introduction

So far, we’ve explored how LeakCanary detects leaks, analyzes heap dumps with Shark, and categorizes them. But in real teams, leaks often slip through because developers only check them locally.

The next step is automation: integrating LeakCanary into your CI/CD pipeline so leaks are caught before release. This transforms LeakCanary from a developer tool into a team safeguard.

🛠️ Configuring LeakCanary for CI

LeakCanary is designed for debug builds, but you can configure it to export leak reports for CI.

Gradle Setup

dependencies {
    debugImplementation "com.squareup.leakcanary:leakcanary-android:2.12"
}

Exporting Leak Reports

LeakCanary stores reports in:

/storage/emulated/0/Download/leakcanary/

You can configure CI to collect these reports after instrumentation tests.

🧑‍💻 Example: CI Script

# Run instrumentation tests
./gradlew connectedDebugAndroidTest
# Collect LeakCanary reports
adb pull /storage/emulated/0/Download/leakcanary ./ci-reports/leaks

Then, parse the reports in your CI pipeline to fail builds if leaks are detected.

📊 Diagram: CI/CD Workflow

Instrumentation Tests → LeakCanary Reports → CI Collects Reports → Shark Analysis → Build Pass/Fail

🚨 Best Practices

  • Run LeakCanary only in debug builds — avoid performance impact in release.
  • Automate report collection — don’t rely on manual checks.
  • Fail builds on critical leaks — use retained size thresholds to decide severity.
  • Archive reports — keep leak traces for regression tracking.

🔮 Coming Next

In Part 8, we’ll wrap up the series with LeakCanary Reporting & Advocacy — how to interpret leak traces, present findings to teams, and use them as advocacy material in talks and blogs.

Comments

Post a Comment

Featured Articles

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

Play Store Uploads with Fastlane Supply - 4

Image
If you’ve ever manually uploaded an APK or AAB to the Google Play Store, you know it can be a tedious process. From filling out all the necessary metadata to selecting the correct APK version, it can feel like a lot of repetitive work. But with Fastlane Supply , you can automate this entire process — making your app releases smoother, faster, and error-free. In this section, we’ll explore how Fastlane Supply works and how to set it up to upload your Android app directly to the Play Store with ease. Step 1: Set Up Google Play API Access Before you can upload your app with Fastlane Supply , you need to set up Google Play API access . This ensures that Fastlane can communicate with the Play Store and upload your APK or AAB. Here’s how you can set up API access: Create a Google Cloud project : Go to the Google Cloud Console. Create a new project. Enable the Google Play Developer API : In the Cloud Console, search for and enable the Google Play Developer API . Create a service account ...
Read more

Cracking Android SDE2/SDE3 Interviews in 2026: Deep Dives, Code, Follow-ups

Image
  Find Part -2 From Here Find Part -3 From Here Lifecycle & Components 1. Activity lifecycle states? Interviewer:  Walk me through the full Activity lifecycle and where you’d place data syncs. Candidate:  Absolutely. The Activity lifecycle defines how Android creates, displays, pauses, and destroys a screen. Correct usage ensures good performance, no leaks, and a smooth user experience. onCreate()  Called once when the Activity is created.  Used for one-time initialization such as: Dependency injection (Hilt) Initializing ViewModels Setting the UI with setContentView() or setContent {}  The UI is not yet visible, so no user interaction or heavy work should start here. onStart()  The Activity becomes visible to the user but is not yet interactive.  This is a good place to prepare UI-related resources or start observing data. onResume()  The Activity is in the foreground and fully interactive .  This is the best place to: Start sens...
Read more

Android Device Security: Sandboxing, Rooting, and Attestation Explained

Image
  As Android developers, understanding device security is essential to protect our apps and users. In this comprehensive guide, we’ll explore Android’s security architecture, including sandboxing, rooting and jailbreaking, and how to implement device attestation using SafetyNet and Play Integrity. We’ll cover each topic in detail, providing code snippets and best practices, following. What is Sandboxing in Android? Sandboxing is the security mechanism that isolates each app’s code and data from other apps and from the underlying system. In Android, this ensures that one app cannot freely read or modify another app’s private data or perform privileged operations unless explicit permissions or IPC channels are used.​ High-Level Idea Each app runs in its own isolated environment with: Its own Linux user ID (UID) and process. Its own private data directory (e.g., /data/data/<package_name>/ ). By default: One app cannot directly access another app’s files. An app cannot perfo...
Read more