Quantcast
Channel: Active questions tagged react-native+ios - Stack Overflow
Viewing all articles
Browse latest Browse all 16750

How to efficiently trace the source of error in React Native?

$
0
0

I'm getting the following error and I'm beyond frustrated. Expo doesn't point towards the source of the error for some reason and I've been combing through all of my codes for the past half an hour to find this mysterious variable, "st". I'm assuming this is some typo that I've made. I've commented out all of my screens, but still the same error. So I've combed through all of the query and mutation files, App.js, etc, but still no luck. I've even combed through the back end files to no avail. I've removed and re-installed my node modules, but still the same error. Is there a way to trace the source of this more efficiently? Or is this even a typo error or is this something else? Please help!!

enter image description here

I get the following instruction:

info PRO TIP When you see Red Box with stack trace, you can click any stack frame to jump to the source file. The packager will launch your editor of choice. It will first look at REACT_EDITOR environment variable, then at EDITOR. To set it up, you can add something like export REACT_EDITOR=atom to your ~/.bashrc or ~/.zshrc depending on which shell you use.

so I set up my vcode in bashrc as the REACT_EDITOR but clicking on the error doesn't launch the editor to the source file.


Viewing all articles
Browse latest Browse all 16750

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>