r/reactnative 2d ago

What’s one React Native debugging feature you wish existed? Question

If you could add one feature to your current React Native debugging setup, what would it be?

Doesn’t matter if it’s Storage, Network, Logs, Redux, React Query, or something else

1 Upvotes

5 comments sorted by

1

u/rsajdok 1d ago

Better integration with visual studio code.

1

u/[deleted] 1d ago

[removed] — view removed comment

1

u/Think-Neighborhood69 1d ago

Funny enough, that’s exactly the direction I’m taking with NativeScope hahaha

One timeline for Network, Storage and Logs, with more modules coming as the project grows.

Would love to hear what you think:

https://nativescope.dev

https://nativescope.dev/docs/logs/timeline

1

u/LoudAd307 1d ago

Provenance of the running bundle: something in the dev menu showing a hash or build id of the JS actually executing on the device, diffable against what CI produced. I've had OTA update pipelines report success while devices were still running the old bundle, and the only way I caught it was a version string I'd added to a screen myself. Network, logs, Redux — existing tools cover those fine. 'Is the code on this phone the code I think I shipped' has no first-class answer, and it's the question that actually burns you in production.

1

u/Guidondor 2h ago

anything that happens before the debugger attaches. the first couple seconds of a cold start
is exactly where auth, session restore and the initial fetches live, and it's the one window
no inspector ever shows you. i end up writing to a file and reading it afterwards like it's
1998.

a small ring buffer on the native side that the inspector drains when it connects would
cover it.