This pull request was exported from Phabricator. Differential Revision: D61885705

This pull request has been merged in cf356bd.

This pull request was successfully merged by @rubennorte in cf356bd

^{When will my fix make it into a release? | How to file a pick request?}

hi @rubennorte what was the rationale for this change? thanks!

hi @rubennorte what was the rationale for this change? thanks!

This is an internal API in React Native and it was logging too much data to Systrace in the current use cases that we had. We'll probably remove this API altogether as it's not used within React Native itself and it's not public.

hi @rubennorte what was the rationale for this change? thanks!

This is an internal API in React Native and it was logging too much data to Systrace in the current use cases that we had. We'll probably remove this API altogether as it's not used within React Native itself and it's not public.

@rubennorte Thanks for the response. Are the use cases that relied on these traces still relevant at Meta? If so, out of curiosity, how are those needs being addressed after this change?

For context, we used these traces to determine the number and duration of network calls during app startup, and used that data to help app developers reduce startup latency caused by excessive network requests on launch.

Thanks.

For context, we used these traces to determine the number and duration of network calls during app startup, and used that data to help app developers reduce startup latency caused by excessive network requests on launch.

Thanks.

@abhaywit I would recommend using the new Web performance APIs released as stable in 0.83 (https://reactnative.dev/blog/2025/12/10/react-native-0.83#web-performance-apis-as-stable).