🐛 Autofocus returning errors on newest Android devices

[buildgreatthings]

What were you trying to do?

I want to autofocus on the center of the video on an Android device. IF the device does not support autofocus, I want it to gracefully terminate. I add an if statement that checks the support for autofocus before actually calling the autofocus function.

https://mrousavy.com/react-native-vision-camera/docs/api/interfaces/CameraDevice#supportsfocus

Reproduceable Code

With a camera reference instantiated


        if (camera?.supportsFocus) {
        console.log('supports focus');
        // grab the centerpoint to autofocus on
        const centerPoint = {
          x: Dimensions.get('window').width / 2,
          y: Dimensions.get('window').height / 2,
        };

        console.debug(`Autofocusing on center`);
        return cameraRef.current.focus(centerPoint);
        }

### What happened instead?

The device waits for the focus function for several seconds and then spits the following error. This behavior is Android specific

### Relevant log output

```shell
This device does not support autofocus:  [unknown/unknown]: [unknown/unknown] Cancelled by cancelFocusAndMetering()

Device

Samsung s22

VisionCamera Version

1.0.3

Additional information

• I am using Expo
• I have read the Troubleshooting Guide
• I agree to follow this project's Code of Conduct
• I searched for similar issues in this repository and found none.

[wilav-dev]

Similar issue: Cancelled by another startFocusAndMetering()

[scaralfred]

Are there any plan to fix this?
Samsung S22 still present this issue

[osbornZ]

Are this issue fixed？
I got this similar ：
[unknown/unknown] None of the specified AF/AE/AWB MeteringPoints is supported on this camera.

[mrousavy]

Hey! I've rewritten the entire Android codebase of VisionCamera from CameraX to Camera2 in the efforts of ✨ VisionCamera V3.

I just now completed the Camera2 rewrite and I believe the core structure is running, but there might be some edge cases to iron out. Can you try and test the PR #1674 for me to see if you can still reproduce this issue here?

Here's an instruction on how you can test that: #1674 (comment)

If the issue cannot be reproduced with that version/PR anymore, then hoorayy, I fixed it! 🎉
Otherwise please let me know and I'll keep this issue open to keep track of it.

Thank you!