TabQA logoTabQA

Network capture

Capture requests from Android Chrome and debug-enabled WebViews

Confirm that traffic comes from a browser page or a debuggable WebView before choosing the Chrome debugging protocol.

Direct answer

Android Chrome pages and WebViews that call WebView.setWebContentsDebuggingEnabled(true) expose network events through the Chrome DevTools Protocol. TabQA attaches to those targets during mirroring, records status, timing, requests, and responses, and exports sanitized cURL or HAR.

Android network capture and failed-request details in TabQA
The network panel and device reproduction share one session, making requests easier to align with user actions.

Confirm whether the target is capturable

Traffic sourceCurrent support
Android Chrome pageSupported
Hybrid page with WebView debugging enabledSupported
WebView without debuggingNot supported
Native libraries such as OkHttp or RetrofitNot supported

Diagnose a failed request

  1. Start mirroring and open the network panel.
  2. Reproduce the issue and filter requests by status or keyword.
  3. Review URL, method, status, timing, headers, body, and response.
  4. Copy a sanitized cURL to replay one request or export a sanitized HAR for engineering.

Storage and redaction boundaries

  • A session keeps at most 1,000 requests and 256 KiB per text body side.
  • Binary bodies are not retained.
  • Common auth headers and sensitive key names are masked, but application-specific fields still need review.
  • Capture runs in the local test session the user explicitly starts.

Sources and basis