Camera.getAvailableCameraDevices() returns null on Android, physical device🐛

[stivenm16]

What were you trying to do?

I'm trying to access to all available Camera Devices but it returns null when I'm running my app on a physical device, however when I run the code in the emulator it works fine and returns a full array with options. The phone is connected via usb. This unexpected behaviour still persist after build it

Reproduceable Code

const TestComponent = () => {
  const { navigate } = useNavigation();
 
  useEffect(() => {
    const requestPermissions = async () => {
      await Camera.requestCameraPermission();
    };
    requestPermissions();
  });


  const devices = useCameraDevices();
  const device = devices.back;

  // console.log(devices, "devices"); => it returns null on physical device

  if (device == null)
    return (
      <View>
        <Text> Device null</Text>
      </View>
    );

  return (
    <View style={{ flex: 1, backgroundColor: "red", padding: 10 }}>
      <Camera style={{ flex: 1 }} device={device} isActive={true} />
      <Text>It works</Text>
    </View>
  );
};

What happened instead?

useCameraDevices() returns null when is called on a physical device

Relevant log output

No response

Device

Silver Max lite 2

VisionCamera Version

2.15.2 - 2.15.4

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.

[EmiBenitez]

any news about this? I have the same problem.

[Ntouris3]

I'm facing the same issue

[chj-damon]

I tried in Smartisan which is another brand and also the devices are all undefined.

[SohaibKtb]

same for Tecno devices

[myselfuser1]

Try this https://www.youtube.com/playlist?list=PLQhQEGkwKZUrempLnmxjt7ZCZJu1W3p2i

[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!