Skip to content

fix(react-native): support react-native-webgpu 0.19 - #10

Open
reczkok wants to merge 1 commit into
fishjam-cloud:mainfrom
reczkok:fix/drop-rnwebgpu-native-texture
Open

reczkok wants to merge 1 commit into
fishjam-cloud:mainfrom
reczkok:fix/drop-rnwebgpu-native-texture

Conversation

@reczkok

@reczkok reczkok commented Oct 28, 2026

Copy link
Copy Markdown

react-native-webgpu 0.12 removed the rnwebgpu/native-texture feature (wcandillon/react-native-webgpu#498). Native frame import is always on now and requestDevice throws when that name is in requiredFeatures, so on 0.12+ the camera device can't be created and assertWebGpuDeviceSupportsCameraImport rejects any device the app passes in.

REQUIRED_FEATURES now lists only the platform feature (dawn-multi-planar-formats on iOS, opaque-ycbcr-android-for-external-texture on Android).

The peer range stays >=0.5.15, since 0.5.15–0.11 turn the native-texture features on by themselves when the adapter has them. The only difference there is that an adapter without them fails on the first frame instead of at device creation.

This also bumps react-native-webgpu from 0.10.1 to 0.19.2, which brings Dawn 157, readable native errors on Android, and destroy() on shared texture memory and fences (wcandillon/react-native-webgpu#516) that we need to stop per-frame fence memory growth on Android. No API changes were needed.

Test

yarn tsc passes. Background blur works in fishjam-chat on an iPhone 17 Pro Max (iOS 27.2) with react-native-webgpu 0.19.2 and this build. I haven't run it on Android.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant