Why does my Expo App crash even with an ErrorBoundary? - react-native

Question

I added an ErrorBoundary to my app, but even with an ErrorBoundary my app crashes on errors. Here is a snack with some sample code: https://snack.expo.dev/jq6vGCOoP, also included below:
class ErrorBoundary extends React.Component {
constructor(props) {
super(props);
this.state = { error: null, hasError: false, errorInfo: null };
}
static getDerivedStateFromError(error) {
return { hasError: true, error };
}
componentDidCatch(error, errorInfo) {
// Catch errors in any components below and re-render with error message
this.setState({
error,
hasError: true,
errorInfo,
});
// You can also log error messages to an error reporting service here
}
render() {
if (this.state.hasError) {
// Error path
return (
<View>
<Text>Something went wrong.</Text>
</View>
);
}
// Normally, just render children
return this.props.children;
}
}
export default function App() {
return (
<ErrorBoundary>
<AppInner/>
</ErrorBoundary>
)
}
function AppInner() {
throw new Error('Error here');
return <></>;
}
I've defined my ErrorBoundary and wrapped it around AppInner, a child component in which I manually throw an error. It kind of works, in developer mode when I run my app using expo start, I get a red error which I can dismiss and I can see the Something went wrong error text. However, when I run the app in production mode using expo start --no-dev --minify, the app just crashes. This is also expected if it crashes locally, but I've also tried pushing the app up onto Expo using eas update, and the app also crashes when trying to load it through Expo hosted services.
Anyone have any ideas?