fix: Catch InitializationException and rethrow in onError callback

[mrousavy]

What

The CameraProvider Future was throwing an InitializationException when less Cameras can be found than anticipated:

- androidx.camera.core.InitializationException: androidx.camera.core.CameraUnavailableException: Device reporting less cameras than anticipated. On real devices: Retrying initialization might resolve temporary camera errors. On emulators: Ensure virtual camera configuration matches supported camera features as reported by PackageManager#hasSystemFeature. Available cameras: 0
-     at androidx.camera.core.CameraX.lambda$initAndRetryRecursively$2$androidx-camera-core-CameraX(CameraX.java:433)
-     at androidx.camera.core.CameraX$$ExternalSyntheticLambda2.run(D8$$SyntheticClass:0)
-     at java.util.concurrent.ThreadPoolExecutor.processTask(ThreadPoolExecutor.java:1187)
-     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1152)
-     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
-     at java.lang.Thread.run(Thread.java:784)

This PR catches this issue when it happens in a configure(...) call, and rethrows it in the onError callback (the React prop to <Camera />).

This makes sure the app doesn't crash and can still be handled by the user.

Changes

Tested on

Related issues

• Fixes 🐛 InitializationException - Device reporting less cameras than anticipated #3179

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
react-native-vision-camera	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 20, 2025 9:42am

[rb-adnan]

@mrousavy please check the pipeline failure. seems issue in accessing val due to try catch scope. need this MR asap!! thanks

[mrousavy]

Dude stop being impatient this is free software - if you need this "asap" do it yourself.

I'll focus on this when I have free time.

[mrousavy]

overruled by #3385