NativeScope module 02 · available now

See every request in the context that made it matter.

Capture HTTP and GraphQL, find the exact call, inspect the complete exchange, replay with control and follow a response into the storage it changed. Fully local, inside the same Studio.

Add NetworkRead the docs
  • Local only
  • Bounded memory
  • Configurable redaction
Network · NativeScope Studiolive
NativeScope Network displaying a request list, request detail and response body

HTTP + GraphQLone operation-aware timeline

fetch + XHRautomatic development capture

1 lineto enable the whole module

0 cloudaccounts, proxies or remote dashboards

Unified timeline
live
All trafficHTTPGraphQLMutations
TypeOperation or endpointStatus
QUERY

GetViewer/graphql

200
MUT

UpdateSettings/graphql · 2 variables

GQL 1
GET

/api/profileHTTP · 148 ms

200
POST

/checkoutHTTP · 1.2 s

409

One timeline, two protocols

GraphQL should not look like a wall of POST requests.

NativeScope recognizes GraphQL over HTTP automatically. Queries, mutations, persisted operations and batches keep their operation names, variables and semantic errors without another client adapter or schema upload.

  • Document and variables remain separate.
  • Filter by protocol, query, mutation or batch.
  • GraphQL errors stay visible even when HTTP returns 200.
Explore GraphQL debugging

Control the session

Keep the signal. Lose the noise.

Capture controls, filtering and session-level analysis stay close to the timeline without changing how your app makes a request.

Focus without deleting history

Start a new capture from this moment, keep earlier traffic behind a marker and return to it whenever context matters.

Learn more

Search every layer

Combine URL, header and body search with method, status, duration, protocol and GraphQL operation filters.

Learn more

Read complete payloads

Inspect request, response and headers separately. Large bodies stay bounded, then load completely only when requested.

Learn more

Understand the session

Open Insights for request volume, failures, p95 latency, transferred data, a timeline and endpoint-level drill-down.

Learn more

Hear only what matters

Use a local sound for every request, failures only or selected endpoint rules, with a compact volume control.

Learn more

Follow storage impact

See which storage entries changed immediately after a response and open the exact value in the Storage module.

Learn more

Replay HTTP and GraphQL

Change the request, not your concentration.

Query parameters and headers are structured rows. Common header names are suggested but never forced. JSON bodies are formatted and validated; GraphQL gets dedicated Operation and Variables editors. Untouched sections keep the captured request exactly as it was.

  1. 01
    Choose the sessionOriginal capture or current app credentials.
  2. 02
    Edit only what mattersQuery, headers, body, operation and variables stay separate.
  3. 03
    Replay, compare, follow impactThe new execution is tagged in the request list.
Learn replay and compare
NativeScope structured request replay editor
NativeScope Network Insights showing request volume, failures, latency, transferred data and endpoint performance

Network Insights

One request explains a call. The session explains the problem.

Step back from individual payloads without leaving the Studio. Insights turns the current capture into a readable overview of volume, failures, p95 latency, transferred data and endpoint behavior across HTTP and GraphQL.

  • Read traffic and failures over time.
  • Rank endpoints by calls, errors, latency or bytes.
  • Analyze every request or only the active filters.
Explore Network Insights

The whole integration

One line turns the module on.

Use the defaults first. Fine-tune body capture, limits, ignored URLs and redacted headers only when the app needs it.

See every option
nativescope.config.ts
import { defineNativeScopeConfig } from
  "react-native-nativescope/app"

export default defineNativeScopeConfig({
  modules: {
    network: true,
  },
})
The module appears when the app reconnects.

Useful boundaries

Detailed when you ask. Bounded when you do not.

Preview first. Large payloads send a bounded preview to keep the request list responsive. The full body loads on demand, with a 32 KB preview and 2 MB retention limit by default.

Buffers stay finite. Request history and retained bodies have explicit, configurable limits instead of growing with the session forever.

Your credentials stay local. Redact additional headers when necessary, and remember that replay performs a real request with real side effects.

Network is live

Stop reconstructing the request from logs.

Enable NetworkExplore Storage