Xavier Seignard

Aaaaannd still happening with: ``` react-native 0.72.5 react-native-vision-camera 3.6.4 react-native-worklets-core 0.2.4 ```

~Looking at the code closely:~ ~- First, look at `CameraManager.openCamera`: https://developer.android.com/reference/android/hardware/camera2/CameraManager#openCamera(java.lang.String,%20android.hardware.camera2.CameraDevice.StateCallback,%20android.os.Handler)~ ~- It throws a `CameraAccessException`: https://developer.android.com/reference/android/hardware/camera2/CameraAccessException~ ~- The `CameraManager.openCamera` extension ([here](https://github.com/mrousavy/react-native-vision-camera/blob/main/package/android/src/main/java/com/mrousavy/camera/extensions/CameraManager%2BopenCamera.kt#L45)) derives the thrown error with `CameraDeviceError.fromCameraDeviceError`~ ~- Looking...

MMM, you're right, sorry for the confusion. That's weird they transform error codes in between the call to `openCamera` and the `onError` handler 🤔 I do reproduce the inital error...

Ok, after a good night of sleep, I know the problem. If you look at my frame processor: ``` const measurePupillaryDistanceInPixelsJS = Worklets.createRunInJsFn(measurePupillaryDistanceInPixels); const frameProcessor = useFrameProcessor((frame: CameraFrame) => {...

Still happening in release mode 🤷 Actually I never succeedeed to make `react-native-vision-camera@v3` work on android release builds (with proguard enabled)

I confirm it is happening too with `expo@49` and `[email protected]`

I'm not sure @BrianCodeItUp solution is the best approach as you don't need to patch this lib to keep it working. Just edit your own `android/build.gradle` I'd recommend relying on...

Hello 👋 I have the same error and I was not able to fix it by removing `@babel/plugin-proposal-class-properties` as it is needed by `react-native` itself ([random example](https://github.com/facebook/react-native/blob/main/packages/react-native/Libraries/Components/Touchable/TouchableWithoutFeedback.js#L119)) and some parts...

please don't use @hbel solution 😬 rely on a custom dev client (see: https://docs.expo.dev/develop/development-builds/introduction/) and use a custom plugin to change `androidXBrowser` in the `ext`, you can have a look...

Hello, We are facing the same issue. We use react-18next, and when we use the [``](https://react.i18next.com/latest/trans-component) component, here's how our translations look like: ...