Direct answer
Android Chrome pages and WebViews that call WebView.setWebContentsDebuggingEnabled(true) expose network events and console.* output through the Chrome DevTools Protocol. TabQA attaches during mirroring and records requests, responses, and page logs in Network and Console tabs. Console supports text, regular-expression, and Verbose, Info, Warning, or Error level filters.
Confirm whether the target is capturable
| Content source | Current support |
|---|---|
| Requests and console.* from an Android Chrome page | Supported |
| Hybrid page with WebView debugging enabled | Supported |
| WebView without debugging | Not supported |
| Native libraries such as OkHttp or Retrofit | Not supported |
| Uncaught exceptions, browser-internal logs, and JavaScript evaluation | Not supported |
Diagnose a failed request
- Start mirroring and open the network panel.
- Reproduce the issue and filter requests by status or keyword.
- Review URL, method, status, timing, headers, body, and response.
- Copy a sanitized cURL to replay one request or export a sanitized HAR for engineering.
Inspect page Console output
- Switch to Console in Page debugging.
- Filter messages and sources with plain text, or enter /pattern/flags for a regular expression.
- Combine Verbose, Info, Warning, and Error levels; Verbose is hidden by default.
- Messages appear newest first, with an option to preserve them across navigation and target changes.
Storage and redaction boundaries
- Network and Console each keep at most 1,000 entries; a network text-body side is limited to 256 KiB and one Console message to 32 KiB.
- Binary bodies are not retained.
- Console is a read-only view of page console.* output and does not execute JavaScript.
- Common auth headers and sensitive key names are masked, but application data explicitly written to Console still needs review.
- Capture runs in the local test session the user explicitly starts.