I cant see the component boundary

Hi, I cant see the boundary component when I throw an error.

the throw error: throw new Error('💥 CABOOM 💥'); trigged by onPress

and the only error that show was the react-native error screen. I was click in dismiss, but the error boundary component not show.

https://user-images.githubusercontent.com/30187750/103559676-6e7e9e80-4eae-11eb-9b64-eb3ad1bdc0cf.mov

[carloscuesta]

No problem, a pleasure to explain. Thanks to you aswell for creating the demo repository ❤️

Have a great day!

[carloscuesta]

Hey @DwCleb

I cant use the state to show the error component, this is not flow in development.

You don’t need state to show the ErrorBoundary component. What happens is that on development mode some errors are catched by the LogBox component -> https://reactnative.dev/blog/2020/07/06/version-0.63#logbox

This component is made for catching unhandled errors on release mode. Not for displaying errors on development. You can read more about this in here: https://carloscuesta.me/blog/managing-react-native-crashes-with-error-boundaries

So you won’t able to render the ErrorBoundary component on Development just by throwing an error from the Button. Because those type of errors are getting caught by the LogBox component on development. As taken out from react-native docs: https://reactnative.dev/docs/debugging#logbox

On release mode, it will work because the LogBox it’s not shipped to your application, so the component will catch all the JavaScript errors just by using the ErrorBoundary component.

The goal is catch JS error, and with State I’m forced a component error show, it’s a controlled situation, not a real situation of error. Using state worked, but this not a real case.

As you say, you’re simulating an error so that clearly it’s not a real case. You’re trying to force an error to render the ErrorBoundary component on development. If you want to render the ErrorBoundary, using the throw Error, use react-native run-ios --variant=release to set the application on release mode, and avoid the LogBox component.