🐛 Resizer in frameOutput fails on Samsung Galaxy Z Flip7

[rudolfmedula]

Prerequisites

• I have read and followed every applicable step in the Nitro Modules Troubleshooting guide.
• I have read the VisionCamera Troubleshooting guide.
• I have searched existing issues and found nothing matching.
• I am on the latest version of react-native-vision-camera, or have a specific reason I cannot upgrade.

Reproduction

https://github.com/rudolfmedula/react-native-vision-camera/pull/1/changes

Steps to reproduce

on Android Samsung Galaxy Z Flip7 F766B

• run sample app with changes from the linked repro repo

What did you expect to happen?

resizer.resize(frame) returns resized frame

What actually happened?

Resizer crashes with Failed to allocate Vulkan memory for the imported AHardwareBuffer image. (VkResult -13).', {}

Affected platforms

Android (device)

Device(s) affected

Samsung Galaxy Z Flip7 F766B

VisionCamera version

5.0.4

React Native version

0.84.0

React Native architecture

New Architecture (Fabric / bridgeless)

Features being used

• Preview
• Photo capture
• Video capture
• Frame Processors (worklets)
• Skia Frame Processors
• Code/Barcode Scanner
• Location metadata
• Multi-cam
• Depth data
• HDR / custom dynamic range
• Custom format / FPS / resolution

Relevant logs / stack trace

2026-04-30 11:39:38.719   991-20949 [[@]]CameraProperty     ven...re.camera.provider-service_64  I  [setImageSize:828] CaptureSize[0] : 4080 3060
2026-04-30 11:39:38.719   991-20949 [[@]]CameraProperty     ven...re.camera.provider-service_64  I  [setImageSize:839] MaxCaptureSize[0] : 4080 3060
2026-04-30 11:39:38.719   991-20949 [[@]]CameraProperty     ven...re.camera.provider-service_64  I  [setImageSize:828] CaptureSize[1] : 4000 3000
2026-04-30 11:39:38.719   991-20949 [[@]]CameraProperty     ven...re.camera.provider-service_64  I  [setImageSize:839] MaxCaptureSize[1] : 4080 3060
2026-04-30 11:39:39.302 20739-20832 ReactNativeJS           com...o.nitro.camera.example.simple  E  'Resizer.resize(...): Failed to allocate Vulkan memory for the imported AHardwareBuffer image. (VkResult -13).', {}

Additional context

No response

Submission

• The reproduction I linked is either (preferred) a PR against this repo that adds a failing harness test following the harness-tests README, or (fallback) a public repo that reproduces the bug on a fresh clone. I understand the issue will be closed without one.
• I pasted logs as text (not screenshots).
• I wrote this report in my own words. I did not paste AI-generated descriptions of the bug.

[jslok]

Can you check isResizerAvailable?

I had a user on a flip 6 report an issue. I don't have one so I cannot test it, but I am guessing isResizerAvailable is returning false and you will have to implement a fallback for those cases.
https://visioncamera.margelo.com/api/react-native-vision-camera-resizer/functions/isResizerAvailable

[rudolfmedula]

Can you check isResizerAvailable?

I had a user on a flip 6 report an issue. I don't have one so I cannot test it, but I am guessing isResizerAvailable is returning false and you will have to implement a fallback for those cases. https://visioncamera.margelo.com/api/react-native-vision-camera-resizer/functions/isResizerAvailable

I don't have the Flip 7 available I just borrowed it when debugging so I can't really check right now, but according to the docs the isResizerAvailable is basically a check whether you have android > 28.

I was able to fix my case by switching pixel format on Android from yuv to native in useFrameOutput (you cannot use enablePhysicalBufferRotation option in that case). The reason I needed to use enablePhysicalBufferRotation was because I believe there is a bug in the shader logic when using scaleMode: 'contain' - the bug being the images are basically distorted which can be validated by saving/inspecting any resized image (when using enablePhysicalBufferRotation looks correct, without it the images are distorted). I have AI patch of the shader issue in case anyone encounters it but that's a separate issue I guess