valn1

Hello, for what i know, this problem can be solved simply by changing `VideoCompressEventEmitter.removeSubscription(subscription);` by `subscription.remove()` as the method removeSubscription has been removed in https://github.com/facebook/react-native/commit/d39643b9de11c6b44984166ede34a7f44de76fe5#diff-9f250e6d8a5ec553d894b660a762e5975e048fcb822ece9d1af7a72d93b3cb71

i got the same error on react-native version 0.70.0, have you managed to fix it?

> I don't think this is the problem described in the issue. @erksch did not summarize precisely, because 2.10.0 is actually compatible with rn 0.70.0. You can easily use rn...

any update on this case?

yeah, it is not working as intended, like no matter how big is the timeout you set, it will reactivate right after scanning a code { this.scanner = node }}>

I can confirm that this is still happening in 0.70.5, my component has the following props: borderRadius={25} borderBottomLeftRadius={0} resizeMode={'contain'}

try adding this to your manifest: ``` android:largeHeap="true" android:hardwareAccelerated="true" ```

what should the orientation prop do in this case? i imagine the default "none" to just do nothing, "auto" to read the device's orientation and adjust accordingly and "portrait/landscape" to...

cool, should that not be changeable mid recording?

not as of right now. i fixed that in another app of mine that runs the v2 by using react-native-orientation-locker and doing a patch on the ios part of react-native-vision-camera,...