fix: catch error in cameraProviderFuture.get() #757
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Handle camera initialization failures gracefully instead of crashing the app.
On devices or emulators without cameras, ProcessCameraProvider.getInstance().get() throws an exception that was previously uncaught, causing the app to crash. This change catches the exception and dispatches an ErrorEvent to the JS layer via the onError callback.
The error message extracts the root cause from nested exceptions for cleaner error reporting (e.g., "Device reporting less cameras than anticipated. Available cameras: 0" instead of a wrapped ExecutionException).
closes #756
How did you test this change?