You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Keep reads bounded with `--depth`/`find`, treat `@c` refs as reload-local, profile only the investigated interaction, and run the same command in remote Android sessions; the CLI manages the companion tunnel.
39
+
Keep reads bounded with `--depth`/`find`, treat `@c` refs as reload-local, profile only the investigated interaction, and run the same command in remote Android sessions; the CLI manages the needed local service tunnel.
Copy file name to clipboardExpand all lines: src/utils/command-schema.ts
+19Lines changed: 19 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -386,22 +386,40 @@ React Native internals:
386
386
Use this for React Native performance/profiling and internals that the accessibility tree cannot expose: components, props, state, hooks, ownership, slow renders, and rerenders.
1. Verify the app is connected: react-devtools status, then wait --connected if needed.
401
411
2. Start profiling immediately before the interaction.
402
412
3. Drive the interaction with normal agent-device commands.
403
413
4. Stop profiling.
404
414
5. Inspect slow components and rerenders.
415
+
6. Use profile report @cN for render causes and changed props/state/hooks; use get component @cN for current props/state/hooks.
416
+
417
+
Rules:
418
+
Start with get tree --depth 3 or find <name>; use find --exact when fuzzy results are noisy.
419
+
@c refs reset after reload/remount. After reload, wait --connected and inspect again.
420
+
Keep the profile window narrow; unrelated navigation makes render data noisy.
421
+
For cross-platform validation with explicit device selectors, prefer isolated --state-dir and restart react-devtools between platforms.
422
+
Remote Android runs normally through agent-device react-devtools; the CLI manages the needed local service tunnel. Expo support depends on the SDK's bundled React Native runtime.
Use snapshot, screenshot, logs, network, and perf for device/app runtime evidence. Use react-devtools only when component internals or React rendering behavior matters.`,
0 commit comments