Alex
Alex
@kkaplinski I also did this. Did you find the information about the limit? I mean, if it's GPU memory limit we need to check it and load different sprite (asset).
We also see a significant increase in these errors using React Native 0.76.7
@tmikov from mobx: ``` export function FlowCancellationError() { this.message = “FLOW_CANCELLED” } FlowCancellationError.prototype = Object.create(Error.prototype) ``` then: ``` throw new FlowCancellationError() ``` and try to read: ``` try { ......
@tmikov "fatal" - I meant it would crash the application.
@tmikov It's not the JS exception that crashes the application, it's the attempt to read the stack property. My case is that I have an unhandled `FlowCancellationError` exception, it goes...
https://github.com/callstack/react-native-slider/pull/738
@ChaparroAlberto I temporarily fixed this like this: ``` const isKeyboardVisible = useKeyboardState(state => state.isVisible); // or Keyboard.addListener('keyboardDidHide') useEffect(() => { if (Platform.OS !== “ios”) { return; } if (!isKeyboardVisible) {...
in the place where you have access to the modal ref
you can create a folder called Admob: - index.web.ts: ``` export {} ``` - index.ts: ``` export * from 'react-native-google-mobile-ads' ``` And use imports from Admob instead of directly react-native-google-mobile-ads...