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.
Cannot see red error screen in case of javascript errors
See original GitHub issueI am in the processing of migrating our app from v0.59.9 to v0.63.3. While i got other things migrated successfully, i noticed that javascript (non-fatal) errors that used to be thrown in a red screen earlier are not reported the same way. For basic javascript errors like undefined is not a method, the app crashes and then i have to check adb log cat and then de-obfuscate them using metro-symbolicate to see what the error is. I am tried running the app with --variant=debug without success. Is there a better way to see these errors without this cumbersome process?
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
This worked after removing
import com.facebook.react.BuildConfigand adding thisandroid:usesCleartextTraffic="true"to the manifest file. Never been more happy to see an error screen.i was able to get the developer menu working by removing this from MainApplication.java:
import com.facebook.react.BuildConfig.Re: https://github.com/facebook/react-native/issues/26417