Android Database Live Inspector

Android Database Live Inspector is an Android Studio App Inspection plugin for watching Room/SQLite database activity from a running debug app. It records SQL statements, bind args, timing, errors, and small result previews, then shows them in a custom App Inspection tab.

Install from JetBrains Marketplace: Install Plugin

What is inside

• plugin: Android Studio plugin UI and App Inspection tab.
• inspector: on-device inspector DEX that Android Studio injects into the app process.
• agent: app-side Room/SQLite wrapper that captures query events.
• protocol: shared JSON message types.
• stubs: compile-time inspection API stubs.

Build

./gradlew buildAll

The plugin zip is written under plugin/build/distributions/. Install it in Android Studio with Settings > Plugins > Install Plugin from Disk.

To use the agent from another local app:

./gradlew :agent:publishToMavenLocal

App setup

Release versions of the agent are published to Maven Central with their protocol implementation bundled into the AAR. It can be used from any app without GitHub credentials:

repositories {
    mavenCentral()
}

Add the agent to your debug app and wrap your Room builder:

dependencies {
    debugImplementation("io.github.ahmedvhashem.databaseliveinspector:agent:VERSION")
}

import dev.ahmedvhashem.databaseliveinspector.agent.DatabaseLiveInspector

DatabaseLiveInspector.install(context)

val builder = Room.databaseBuilder(context, AppDatabase::class.java, "app.db")
DatabaseLiveInspector.attachTo(builder, "app.db")
val db = builder.build()

Run the debug app, open Android Studio's App Inspection tool window, and select Database Live Inspector.

Release

Releases use one version for the plugin and agent. Before the first release, create a Maven Central Portal account and verify the io.github.ahmedvhashem namespace. Create an OpenPGP key, publish its public key, then configure these repository secrets:

• JETBRAINS_MARKETPLACE_TOKEN
• MAVEN_CENTRAL_USERNAME and MAVEN_CENTRAL_PASSWORD (a Central Portal user token)
• SIGNING_KEY (ASCII-armored private OpenPGP key) and SIGNING_PASSWORD

Then merge the release changes through a pull request targeting main and tag the merged commit with a stable semantic version:

git switch main
git pull --ff-only
git tag v1.0.2
git push origin v1.0.2

The publish workflow rejects non-vX.Y.Z tags, commits outside main, and commits that GitHub does not associate with a merged pull request targeting main. It publishes the signed agent to Maven Central first and then publishes the plugin to the default JetBrains Marketplace channel.