Repository navigation
Conversation
vzaidman
approved these changes
Nov 3, 2026
meta-codesync Bot
pushed a commit
to react/react-native
that referenced
this pull request
Nov 9, 2026
## Summary Frame timings and screenshots in the React Native DevTools CDP backend have been on in canary since the flag was added. Enable them by default, matching the DevTools frontend, which no longer gates the Performance panel's frames track behind an experiment. **Why now? / Launch support** I always intended to follow up on this. The canary rollout earlier in the year followed significant hardening of this feature on both platforms, including active use in multiple product teams at Meta across various device classes — have been pretty confident this was prod ready for a while. For (and Expo SDK 59), I'll have the cycles to support this (docs, any integration issues) through to launch. Changelog: [General][Changed] - **React Native DevTools**: Frame timings and screenshots in the Performance panel are enabled by default ## Test Plan - `node packages/react-native/scripts/featureflags/index.js --update` regenerated the six flag files; the diff has the same shape as 66b3ae6 ("Promote fuseboxWebSocketEventsEnabled to stable"). - Agent review of any commits on `main` since promotion to canary — nothing flagged. **Sanity check: E2E** With react/react-native-devtools-frontend#288 applied. | iOS | Android | | - | - | | <img width="1676" height="937" alt="Screenshot 2026-10-30 at 18 30 58" src="https://github.com/user-attachments/assets/455eedf5-0c1c-4f0c-86ea-800fdcc69175" /> | <img width="1676" height="938" alt="Screenshot 2026-10-30 at 18 33 05" src="https://github.com/user-attachments/assets/e8c1500d-48e8-43c1-a3d7-4d72b2de3f1a" /> | Differential Revision: D129345367 Pull Request resolved: #59686
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Hard-enable the Performance panel frames and screenshots track for React Native targets. Paired with (and depends on) react/react-native#59686.
Changes
ENABLE_TIMELINE_FRAMESand its gating in the Performance panel. The screenshots checkbox and the frames track are always present, and the screenshots setting defaults to on for React Native targets.FuseboxFeatureObserver. Theunstable_frameRecordingEnabledprotocol field stays, unread.Stored
enable-timeline-framesvalues are dropped bycleanUpStaleExperiments; a savedtimeline-show-screenshotsvalue is kept.Test plan
npm run linton the changed files, andnpm run buildfor the fulldevtools_all_filestarget.REACT_NATIVE_DEBUGGER_FRONTEND_PATH: the Performance panel opens with the "Screenshots" checkbox enabled and no reload banner.Upstreaming plan
devtools-frontendrepo following the contribution guide for Meta employees OR contribution guide.