React Native 0.82 compatibility: which package combo (if any) is supported? Build errors & debugging notes

Questions
,
1

React Native 0.82 compatibility: which package combo (if any) is supported? Build errors & debugging notes

I’m trying to integrate Babylon React Native into a project on React Native 0.82.x. The docs/README suggest official support up to RN 0.73 with versioned packages like @babylonjs/react-native-iosandroid-0-71.
Before I downgrade my app, I’d like to confirm if there’s a known path to get Babylon running on RN 0.82 (or 0.8x in general), or if the only supported route today is pinning the app back to 0.71–0.73.

Environment

React Native: 0.82.x
Platform(s): Android (Pixel emulator) + iOS (later)
Hermes: enabled (can toggle if needed)
Babylon packages tried:
  - @babylonjs/react-native@<latest at time of testing>
  - @babylonjs/react-native-iosandroid-0-71 (also tested other -0-7x variants)
Node / npm: (please see npx react-native info)
OS: macOS (Apple Silicon)

What I Expected

  • A clear guidance on which @babylonjs/react-native-* package should be used with RN 0.82, or a confirmation that RN 0.82 isn’t supported yet.

What Actually Happens

  • Package resolution/peer-dep conflicts during install (example: react-native-permissions peer ranges tied to the -0-71 adapter).

  • When forcing installs, build/link issues occur. (I can provide exact logs if you want; see “Logs” below.)

  • Separate from Babylon itself, RN shows “Remote JS Debugging deprecated” warnings (expected on newer RN) — just mentioning that for completeness; not blaming Babylon for this.

Relevant Logs (sample)

npm ERR! ERESOLVE could not resolve
npm ERR! While resolving: @babylonjs/react-native@1.x
npm ERR! Found: react-native-permissions@5.4.2
npm ERR! Could not resolve dependency:
npm ERR! peer react-native-permissions@"^3.0.0" from @babylonjs/react-native@1.8.5
...

(If helpful, I can share a minimal public repo with RN 0.82 and the exact package versions that reproduce this.)

Questions

  1. Is React Native 0.82 currently unsupported for Babylon React Native?

  2. If unsupported, is there an official roadmap or branch targeting RN 0.8x?

  3. If partially supported, which exact package combination should be used on RN 0.82 (e.g., a specific @babylonjs/react-native-iosandroid-0-7x adapter or a nightly/canary)?

  4. Any known workarounds (patches, overrides, permission package versions, Gradle settings) to get Android running on RN 0.82?

  5. If the recommended path is to pin RN to 0.71–0.73, which version pairings (RN ↔ Babylon packages) are considered the most stable today?

Why I’m Asking
I’d like to avoid a large downgrade unless absolutely necessary. If 0.82 is not feasible yet, I’ll pin the project to a supported RN range for Babylon (e.g., 0.71–0.73) and follow the recommended adapter package.

Willing to Help
I can:

  • Provide a minimal public repro repo.

  • Test any candidate branch or canary build on RN 0.82 and report back.

  • Share full logs and package.json if needed.

2

cc @Cedric

3

Hi @MUHAMMED_ys welcome to the forum

We are in the process of reviewing a new BabylonReactNative package that will work with RN 0.82.

It’s not released as an NPM at the moment but the .tgz can be downloaded and you can install it manually (using npm install path_to_package.tgz)

It’s a single package that works for Android, iOS, Windows and for all RN versions.

it’s available here at the bottom of the page : New NPM · BabylonJS/BabylonReactNative@29e32bd · GitHub

Let me know how it goes on your side, it will help us validate the PR.

1 Like
4

Hi Cedric,

Thank you so much for the quick response — and I’m really sorry for seeing your message late. I had already started losing hope and decided to switch my project to use Filament for now. However, my interest in BabylonReactNative definitely remains strong.

If I can’t achieve the results I’m aiming for with Filament, I’d be more than happy to try out the new BabylonReactNative package and share my detailed feedback and experience with you.

I also wanted to extend a special thanks to you personally for your continued support and effort in keeping BabylonReactNative up to date.

6

@Cedric unfortunately the artifacts have expired. I tried to build the BabylonReactNative locally on macOS but hit a build error. I’ve implemented a fix, full details in the pull request:

1 Like
7

Merged and build in progress!

Thank you for testing! Did you find the package more easy to use ?

1 Like
8

Just exploring for now, but it is already clear this is a masterpiece (as is the rest of the project). The developer experience has improved significantly with the unified packages and I hope to get hands-on soon!

1 Like