Your first capture on Android
With capture running, open an app you want to debug: a browser like Chrome, or your own app if you’ve trusted the certificate in a debug build.
Choosing which apps to capture
Section titled “Choosing which apps to capture”HTTPGlass attributes each request to the app that made it, by name and icon, using Android’s connection-owner lookup. You pick which installed apps to capture; traffic from apps you didn’t pick doesn’t show up. You can change the selection at any time without restarting capture.
Reading a row
Section titled “Reading a row”Each row shows the method, path, status code and the app that sent it. Tap a row to open the detail: request, response, headers, and a body viewer that fits the content type (Pretty, Tree, Raw, Hex for JSON; images; and so on). A GraphQL tab appears for GraphQL operations, showing the operation name, query and variables separately.
Decrypted vs encrypted rows
Section titled “Decrypted vs encrypted rows”If the certificate step is done and the app is a browser or one of your own trusted debug builds, you’ll see the decrypted request and response body. For everything else, the row still shows up — host, size, timing, method, status — but the body reads as an encrypted connection, not blank or broken. HTTPGlass labels this plainly rather than pretending it has access it doesn’t. See Why doesn’t Android decrypt this app? if you expected a specific app to decrypt and it didn’t.
If nothing shows up
Section titled “If nothing shows up”- Check that the app you opened is one you selected for capture.
- Check capture is actually running: look for the notification with Pause/Resume/Stop, or the Quick Settings tile.
- Some manufacturers’ battery optimisation can stop capture in the background. See Battery and background capture.