Console
On native iOS and Android, console capture is not automatic — it is an integration you add, alongside any navigation integration:
import { consoleIntegration } from '@everframe/react-native/integrations/console';
<EverframeProvider config={{ sdkKey: 'evf_live_…', integrations: [consoleIntegration()] }}>It records log, info, warn and error by default — debug is not
included unless you ask for it:
consoleIntegration({ levels: ['log', 'info', 'warn', 'error', 'debug'] })Messages are capped at 2 048 characters and land as
breadcrumbs with kind: "console".
Native logs
Separately, and without any integration, the native side captures its own log
output below the bridge — stderr on iOS; Timber and System.out/System.err
on Android — flattened to info. So a report from a default install carries
native logs but not your JavaScript console.* calls until you add the
integration above.
There is no JS network capture
The native React Native entry ships no fetch or XMLHttpRequest instrumentation.
Requests your JavaScript makes are not recorded as network breadcrumbs, and
networkBodies.disabled is inert here as a result — there is nothing for it to
veto.
That is a gap, not a design decision. If network capture matters for your triage, the React SDK on the web has it, and the native SDKs capture the HTTP clients you wire in natively.
On React Native Web, the same package import resolves to the React SDK, which captures browser console and network context. The native console integration subpath above is for native hosts; web apps use the browser entry’s built-in capture. See React console and network.
Redaction
Everything that IS captured passes through the redaction engine before it is buffered, not before it is sent — so a token in a log line never reaches the buffer.