How frequently does the bug occur?

Sometimes

Description

Previously, with expo sdk 46 and realm 11.* app crashed on every app open in release build (which made sense, since realm 11 expects React Native 0.70). After upgrading expo SDK to latest beta, the app crashes on start in around 30% of cases in release mode with weird exception, I will attach the stack trace below.

I didn't have any luck reproducing it in nightly build or in the local release build with expo dev-client. The only reproducible case for now is building production app via EAS.

Environment:

"expo": "~47.0.0-beta.8",
"react-native": "0.70.4",
"realm": "11.1.0",
"@realm/react": "0.4.0",

What I can see in the logs (second line is caused by the first, I assume):

Unhandled JS Exception: Error: Missing Realm constructor. Did you run "pod install"? Please see https://docs.mongodb.com/realm/sdk/react-native/install/ for troubleshooting, js engine: hermes

Invariant Violation: Failed to call into JavaScript module method AppRegistry.runApplication(). Module has not been registered as callable. Registered callable JavaScript modules (n = 11): Systrace, JSTimers, HeapCapture, SamplingProfiler, RCTLog, RCTDeviceEventEmitter, RCTNativeAppEventEmitter, GlobalPerformanceLogger, JSDevSupportModule, HMRClient, RCTEventEmitter.
        A frequent cause of the error is that the application entry file path is incorrect. This can also happen when the JS bundle is corrupt or there is an early initialization error when loading React Native., js engine: hermes

For additional context (I've seen those as reasons for crashes in other tickets):

• I'm not using firebase libraries in my app.
• Don't have useFrameworks set.

Stacktrace & log output

No response

Can you reproduce the bug?

Yes, sometimes

Reproduction Steps

No response

Version

11.1.0

What SDK flavour are you using?

Local Database only

Are you using encryption?

No, not using encryption

Platform OS and version(s)

iOS

Build environment

No response

Cocoapods version

No response