Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Useless Errors

See original GitHub issue

React Native is an amazing development platform don’t get me wrong…but the LogBox and debugging is almost completely useless and amounts to putting console statements everywhere. i.e. console.log('hey, here...1');

Seriously it’s one of the worst debugging experiences ever. The call stack is worthless and the errors are so vague and don’t show where it happened, etc.

Issue Analytics

State:
Created 2 years ago
Reactions:2
Comments:5

Top GitHub Comments

1reaction

timothyerwincommented, Jul 29, 2021

Here is a simple example that shows in a nutshell all that is wrong with the errors in general. It’s like it was designed by an internal React Native developer to figure out internal issues but is practically useless for end developers who need to see their own code. Same with the call stack. It’s like 50 internal React Native functions instead of showing my code it always shows 1000 lines of React Native code.

Screen Shot 2021-07-29 at 11 55 19 AM

99% of the time it’s a bug in my code. I know that, but the debugger turns it into a needle in a haystack situation where it shows anything but my code.

Again, not a slight against React Native itself, which is a beautiful work of art…just the debugging is a PITA.

0reactions

safaiyehcommented, Aug 7, 2021

Thanks for the issue, and I agree I have not had a good experience with the errors. This issue would be better to open at the metro repo https://github.com/facebook/metro.