close
Skip to content

Promote fuseboxWebSocketEventsEnabled to stable - #58014

Open
huntie wants to merge 2 commits into
react:mainfrom
huntie:export-D116472859
Open

Promote fuseboxWebSocketEventsEnabled to stable#58014
huntie wants to merge 2 commits into
react:mainfrom
huntie:export-D116472859

Conversation

@huntie

@huntie huntie commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

Summary:
NOTE: 🚧 WIP — Exported as placeholder until the to dos below are resolved.

To dos

  • Fix request initiator (currently showing as WebSocket.js).

Changelog:
[General][Added] - React Native DevTools: Add support for inspecting WebSocket events in the Network panel (core only)

Differential Revision: D116472859

huntie added 2 commits August 18, 2026 09:06
Summary:
**Motivation**

Third-party networking stacks that replace React Native's networking modules have no supported way to report CDP and Web Performance network events, so their requests are invisible in the React Native DevTools Network panel and absent from `PerformanceResourceTiming`. Both integration paths are closed on Android:

- **Kotlin** — `InspectorNetworkReporter` is `internal`, reachable only from React Native's own `NetworkingModule` and `WebSocketModule`.
- **Native C++** — `react/networking/` is not exported through the `reactnative` prefab, so `NetworkReporter.h` cannot be included. iOS pods already get this via `React-networking`.

**This diff**

Opens both paths and documents them as unstable.

- `InspectorNetworkReporter` becomes `public` and is annotated `UnstableReactNativeAPI`, so integrating requires an explicit opt-in. Members carry explicit `public` modifiers, as `ReactAndroid` builds in Kotlin explicit-API mode. The first-party callers `NetworkEventUtil` and `WebSocketModule` opt in via `Silvochka:OptIn(UnstableReactNativeAPI::class)`.
- `react/networking/` is added to the prefab header export in `build.gradle.kts`, bringing Android to parity with what `React-networking` already ships to pods on iOS.
- Doc comments on `NetworkReporter`, `RCTInspectorNetworkReporter` and `InspectorNetworkReporter` drop the `[Experimental]` prefix and instead name each as the integration point for third-party stacks. The C++ and Objective-C headers have no annotation to lean on, so they carry a short paragraph noting that this is an unstable API whose exact location and shape may change; on Kotlin, `UnstableReactNativeAPI` already carries that contract and is enforced by the compiler.

On iOS no visibility change is needed — `RCTInspectorNetworkReporter` already ships via React-Core. Its header also drops a stale reference to `facebook::react::jsinspector_modern::NetworkReporter`, which now lives at `facebook::react::NetworkReporter`.

Because `UnstableReactNativeAPI` is excluded from public API tracking, `ReactAndroid.api` is unchanged. The C++ header edits are comment-only, so the C++ API snapshots are unchanged too.

Changelog:
[Android][Added] - **Network inspection**: expose network event reporting to third-party networking stacks as an unstable API

Differential Revision: D116472113
Summary:
NOTE: **🚧 WIP** — Exported as placeholder until the to dos below are resolved.

**To dos**

- [ ] Fix request initiator (currently showing as `WebSocket.js`).

Changelog:
[General][Added] - **React Native DevTools**: Add support for inspecting WebSocket events in the Network panel (core only)

Differential Revision: D116472859
@meta-cla meta-cla Bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Aug 19, 2026
@meta-codesync

meta-codesync Bot commented Aug 19, 2026

Copy link
Copy Markdown

@huntie has exported this pull request. If you are a Meta employee, you can view the originating Diff in D116472859.

@meta-cla

meta-cla Bot commented Aug 19, 2026

Copy link
Copy Markdown

Hi @huntie!

Thank you for your pull request.

We require contributors to sign our Contributor License Agreement, and yours needs attention.

You currently have a record in our system, but the CLA is no longer valid, and will need to be resubmitted.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. meta-exported p: Facebook Partner: Facebook Partner

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant