jtg

Same issue here. Does not always happen, but quite often. Happens on multiple devices since we updated. ``` 11-06 17:04:25.229 4303 5295 E Legacy-CameraDevice-JNI: getNativeWindow: Surface had no valid native...

Is there any solution to this?

https://react-native-vision-camera.com/docs/api/interfaces/CodeScanner#regionofinterest

What exactly is not working about it?

I am experiencing a similar problem. Using 1.1.6. In this line the dependency ends up comparing the buildNumber with the versionName. (f.e. 510 with 0.8.1) [https://github.com/SudoPlz/sp-react-native-in-app-updates/blob/ed1080b6ab379dacd44d550933ad3a8937ca78af/src/InAppUpdates.android.ts#L119](https://github.com/SudoPlz/sp-react-native-in-app-updates/blob/ed1080b6ab379dacd44d550933ad3a8937ca78af/src/InAppUpdates.android.ts#L119)  The number and...

> @Udit-takkar @xtl-geiger did you guys manage to solve it? Yes I ended up using the buildNumber from DeviceInfo and comparing it using a customVersionComparator.

@pedrodlz @leabaertschi I doubt it is possible using this dependency at the moment, seeing as it uses Android's `AppUpdateInfo` under the hood: https://github.com/SudoPlz/sp-react-native-in-app-updates/blob/master/android/src/main/java/com/sudoplz/rninappupdates/SpReactNativeInAppUpdatesModule.java#L91 And `AppUpdateInfo` only provides these values: https://developer.android.com/reference/com/google/android/play/core/appupdate/AppUpdateInfo.html...

Still an issue with some devices.

This would be indeed amazing to have, because using a raw hosted repository and uploading our plugins manually is not a good solution at all...