Open the current inspection workflow
Follow the Network Inspector guide for the installed Studio version. The documented workflow uses App Inspection and a supported running app/process; menu labels can vary with IDE releases.
Check the documented device, library and process requirements before treating a missing request as an application bug.
Know the visibility boundary
Some networking stacks or native traffic may not be captured by the same inspection mechanism. Encrypted transport does not automatically prevent inspection inside a supported application stack, while unsupported networking can remain invisible.
| Observation | Possible explanation |
|---|---|
| No requests shown | Wrong process, unsupported stack or no matching activity |
| Long request duration | Server, network or client-side work needs separation |
| Repeated identical calls | Retry policy, lifecycle or duplicate observers |
| Sensitive headers visible | Test data and recording handling need care |
Reproduce one action at a time
Start from a known state, perform one operation and correlate timestamps with app logs. Inspect method, status, payload size and timing without copying user tokens into public reports.
A large response followed by a slow UI can indicate parsing or rendering after the request rather than network latency alone.
Pair local inspection with field data
Firebase Performance Monitoring can help identify production network patterns for supported instrumentation. It answers a different question from a local Inspector trace.
Compare equivalent endpoints and conditions. A fast Wi-Fi test does not clear a regression affecting mobile networks.
Choose a focused fix
Deduplicate requests, reduce payloads, cache appropriately or move parsing off the main thread based on evidence. APKLint's Performance Checker can organize that review, but it is not a packet capture tool and cannot read your app's live requests. Keep the trace and before/after measurement with the change.
Trace one catalog refresh through the client
Open a test build with a synthetic account, clear the displayed Inspector timeline and trigger one catalog refresh. Correlate the request's method, destination and timing with an application event identifier. If three equivalent requests appear, inspect observers, lifecycle restarts and retry behavior before assuming the server duplicated anything.
The Network Inspector documentation describes support for HttpsURLConnection and OkHttp-based traffic. At this guide's review, that boundary means an empty request list does not establish that a native or other unsupported client made no network calls. Verify the process and supported stack first. Avoid weakening transport security simply to make a request appear in the tool.
Separate transfer time from preparation of the screen
Suppose the response arrives quickly, but the loading indicator remains visible for another second. Add appropriate trace boundaries around parsing and applying the result, then inspect the main thread. Reducing server latency will not repair an expensive synchronous sort performed after the response has already arrived.
Conversely, a slow response body can dominate the operation even when response headers arrive promptly. Record payload size, connection conditions and server behavior when comparing candidates. A cached response and a fresh download are different workloads, so avoid presenting their difference as a code optimization.
Test an ordinary response, an authorization failure, a malformed body and a cancelled refresh. Check that each results in the correct visible state and that cancellation does not allow an old response to replace a newer result. Use test data and redact request headers or bodies before sharing captures, since inspection can expose credentials and personal content from an otherwise encrypted connection. Keep any interception or response-modification rule isolated to the diagnostic session and record that it was active. The resulting trace should establish what the client actually sent and received within the tool's visibility, while broader network coverage or production timing requires separate evidence suited to those questions.
Sources and further reading
Reference review: 29 September 2026. Examples illustrate the workflow; check your installed versions, release artifact and account-specific Console requirements before applying them. This guide is not a claim that APKLint executed your project or verified your private account.
Android inspection tools and practical release guides. About APKLint · Report a correction
