10.20.0-beta.5 Missing Constructor Error

[djgoulart]

How frequently does the bug occur?

All the time

Description

I did a clean install of version realm@10.20.0-beta.5 to test if it would work with reanimated2.
But from the beginning I got the "Missing Realm constructor" error message.

Im using:

    "expo": "~45.0.0",
    "expo-dev-client": "~0.9.6",
    "expo-splash-screen": "~0.15.1",
    "expo-status-bar": "~1.3.0",
    "react": "17.0.2",
    "react-dom": "17.0.2",
    "react-native": "0.68.2",
    "react-native-web": "0.17.7",
    "realm": "10.20.0-beta.5"```

### Stacktrace & log output

```shell
Error: Missing Realm constructor. Did you run "pod install"? Please see https://realm.io/docs/react-native/latest/#missing-realm-constructor for troubleshooting
at node_modules/react-native/Libraries/Core/ExceptionsManager.js:95:4 in reportException
at node_modules/react-native/Libraries/Core/ExceptionsManager.js:141:19 in handleException
at node_modules/react-native/Libraries/Core/setUpErrorHandling.js:24:6 in handleError
at node_modules/@react-native/polyfills/error-guard.js:49:36 in ErrorUtils.reportFatalError
at node_modules/metro-runtime/src/polyfills/require.js:203:6 in guardedLoadModule
at http://10.0.2.2:8081/index.bundle?platform=android&dev=true&minify=false&app=com.realmexpo&modulesOnly=false&runModule=true:142813:3 in global code

Invariant Violation: "main" has not been registered. This can happen if:
* Metro (the local dev server) is run from the wrong folder. Check if Metro is running, stop it and restart it in the current project.
* A module failed to load due to an error and `AppRegistry.registerComponent` wasn't called.
at node_modules/react-native/Libraries/Core/ExceptionsManager.js:95:4 in reportException
at node_modules/react-native/Libraries/Core/ExceptionsManager.js:141:19 in handleException
at node_modules/react-native/Libraries/Core/setUpErrorHandling.js:24:6 in handleError
at node_modules/@react-native/polyfills/error-guard.js:49:36 in ErrorUtils.reportFatalError### Can you reproduce the bug?

Yes, always

Reproduction Steps

You can use the repo below as example and just configure a Sync App.
https://github.com/djgoulart/realm-sync-error|url

Version

10.20.0-beta.5

What SDK flavour are you using?

Atlas App Services (auth, functions, etc.)

Are you using encryption?

No, not using encryption

Platform OS and version(s)

Android SDK 32

Build environment

Which debugger for React Native: ..

Cocoapods version

No response

[takameyer]

@djgoulart Thanks for reporting! Can you confirm that node_modules/realm/react-native/android/src/main/jniLibs/ has something in it? There should be 4 folders containing librealm.so

[djgoulart]

@djgoulart Thanks for reporting! Can you confirm that node_modules/realm/react-native/android/src/main/jniLibs/ has something in it? There should be 4 folders containing librealm.so

@takameyer Yes there are 4 folders with 1 file each.

[takameyer]

@djgoulart Ok thanks, I am also able to reproduce this, with and without expo. Will continue to investigate why.

[takameyer]

@djgoulart It seems the the @realm/react is not resolving the parent dependency to realm v10.20.0-beta.5 and instead downloading its own. This related to this issue we have witnessed on iOS #4622
We will be preparing a new release for Hermes soon, as there are updates from master that need to be backported that @realm/react requires.

[takameyer]

Just an update. We have a PR for @realm/react which will fix the missing constructor. We still need an update to -beta to support some missing features on master

[djgoulart]

@takameyer I would like to help more. Askme if you need anything.

[takameyer]

@djgoulart we are working hard on a new release, which will solve this issue. Please be patient 🙂