realm-js expo sdk51 to sdk52：Could not find the Realm binary. Please consult our troubleshooting guide

How frequently does the bug occur?

Always

Description

I upgraded from expo sdk51 to sdk52 and got the following error： Error: Could not find the Realm binary. Please consult our troubleshooting guide: https://www.mongodb.com/docs/realm-sdks/js/latest/#md:troubleshooting-missing-binary, js engine: hermes [Component Stack]

Stacktrace & log output

&platform=android&de…=hermes-stable:1086 Error: Could not find the Realm binary. Please consult our troubleshooting guide: https://www.mongodb.com/docs/realm-sdks/js/latest/#md:troubleshooting-missing-binary, js engine: hermes Error Component Stack:
    at ContextNavigator (&platform=android&de…es-stable:154322:24)
    at ExpoRoot (&platform=android&de…es-stable:154271:28)
    at App (<anonymous>)
    at ErrorToastContainer (&platform=android&de…es-stable:440863:24)
    at ErrorOverlay (<anonymous>)
    at withDevTools(ErrorOverlay) (&platform=android&de…es-stable:116872:27)
    at RCTView (<anonymous>)
    at View (&platform=android&de…mes-stable:38202:43)
    at RCTView (<anonymous>)
    at View (&platform=android&de…mes-stable:38202:43)
    at AppContainer (&platform=android&de…mes-stable:38074:25)
    at main(RootComponent) (&platform=android&de…es-stable:106313:28)
anonymous	@	&platform=android&de…=hermes-stable:1086
reactConsoleErrorHandler	@	&platform=android&de…=hermes-stable:3777
anonymous	@	&platform=android&de…hermes-stable:18221
registerError	@	&platform=android&de…=hermes-stable:4234
anonymous	@	&platform=android&de…=hermes-stable:4135
overrideMethod	@	&platform=android&de…hermes-stable:31679
reportException	@	&platform=android&de…=hermes-stable:3743
handleException	@	&platform=android&de…=hermes-stable:3768
handleError	@	&platform=android&de…=hermes-stable:3655
reportFatalError	@	&platform=android&de…=hermes-stable:1150
guardedLoadModule	@	&platform=android&de…e=hermes-stable:157
metroRequire	@	&platform=android&de…le=hermes-stable:82
get	@	&platform=android&de…ermes-stable:125677
metroContext	@	&platform=android&de…ermes-stable:125910
loadRoute	@	&platform=android&de…ermes-stable:151869
_loop	@	&platform=android&de…ermes-stable:151899
getDirectoryTree	@	&platform=android&de…ermes-stable:151994
getRoutes	@	&platform=android&de…ermes-stable:151818
getRoutes	@	&platform=android&de…ermes-stable:151704
initialize	@	&platform=android&de…ermes-stable:148438
anonymous	@	&platform=android&de…ermes-stable:148582
mountMemo	@	&platform=android&de…hermes-stable:71842
useMemo	@	&platform=android&de…hermes-stable:72251
useMemo	@	&platform=android&de…=hermes-stable:7680
useInitializeExpoRouter	@	&platform=android&de…ermes-stable:148582
ContextNavigator	@	&platform=android&de…ermes-stable:154358
renderWithHooks	@	&platform=android&de…hermes-stable:70924
mountIndeterminateComponent	@	&platform=android&de…hermes-stable:74803
beginWork	@	&platform=android&de…hermes-stable:76040
performUnitOfWork	@	&platform=android&de…hermes-stable:81033
workLoopSync	@	&platform=android&de…hermes-stable:80802
renderRootSync	@	&platform=android&de…hermes-stable:80768
performSyncWorkOnRoot	@	&platform=android&de…hermes-stable:80336
flushSyncWorkAcrossRoots_impl	@	&platform=android&de…hermes-stable:67953
flushSyncWorkOnLegacyRootsOnly	@	&platform=android&de…hermes-stable:67924
scheduleUpdateOnFiber	@	&platform=android&de…hermes-stable:79984
updateContainer	@	&platform=android&de…hermes-stable:83086
render	@	&platform=android&de…hermes-stable:83678
renderElement	@	&platform=android&de…hermes-stable:40248
renderApplication	@	&platform=android&de…hermes-stable:37980
anonymous	@	&platform=android&de…hermes-stable:37514
runApplication	@	&platform=android&de…hermes-stable:37564
__callFunction	@	&platform=android&de…=hermes-stable:3206
anonymous	@	&platform=android&de…=hermes-stable:2967
__guard	@	&platform=android&de…=hermes-stable:3152
callFunctionReturnFlushedQueue	@	&platform=android&de…=hermes-stable:2966

Can you reproduce the bug?

Always

Reproduction Steps

"expo": "~52.0.17" "react": "18.3.1", "realm": "20.1.0", "react-native": "0.76.3",

Version

"realm": "20.1.0"

What services are you using?

Local Database only

Are you using encryption?

Yes

Platform OS and version(s)

android

Build environment

Which debugger for React Native: "@gorhom/bottom-sheet": "^5.0.6", "@react-native-firebase/analytics": "^21.6.1", "@react-native-firebase/app": "^21.6.1", "@react-native-firebase/auth": "^21.6.1", "@react-native-firebase/crashlytics": "^21.6.1", "@rneui/base": "^4.0.0-rc.8", "@rneui/themed": "^4.0.0-rc.8", "@sdcx/pull-to-refresh": "^0.23.0", "axios": "^1.7.9", "crypto-js": "^4.2.0", "dayjs": "^1.11.13", "ethers": "^6.13.4", "expo": "~52.0.17", "expo-blur": "~14.0.1", "expo-camera": "^16.0.9", "expo-clipboard": "^7.0.0", "expo-constants": "~17.0.3", "expo-crypto": "^14.0.1", "expo-dev-client": "^5.0.5", "expo-font": "~13.0.1", "expo-image-picker": "^16.0.3", "expo-linear-gradient": "^14.0.1", "expo-linking": "~7.0.3", "expo-localization": "^16.0.0", "expo-router": "~4.0.11", "expo-splash-screen": "^0.29.16", "expo-sqlite": "~15.0.3", "expo-status-bar": "~2.0.0", "expo-system-ui": "~4.0.5", "expo-web-browser": "~14.0.1", "fast-xml-parser": "^4.5.0", "i18next": "^24.0.5", "jsencrypt": "^3.3.2", "lodash-es": "^4.17.21", "lottie-react-native": "^7.1.0", "qs": "^6.13.1", "react": "18.3.1", "react-i18next": "^15.1.4", "react-native": "0.76.3", "react-native-confirmation-code-field": "^7.4.0", "react-native-easy-toast": "^2.3.0", "react-native-encrypted-storage": "^4.0.3", "react-native-exit-app": "^2.0.0", "react-native-gesture-handler": "~2.20.2", "react-native-qrcode-svg": "^6.3.12", "react-native-reanimated": "~3.16.1", "react-native-safe-area-context": "4.12.0", "react-native-screens": "~4.1.0", "react-native-svg": "^15.10.1", "realm": "20.1.0", "zustand": "^5.0.2"

Cocoapods version

No response

Dec 11 '24 08:12 jaytaxx

This might be helpful https://github.com/realm/realm-js/issues/6933.

Dec 11 '24 13:12 susonthapa

#6933 is locked, so to ask here as we are hitting similar problem after upgrade 51->52.. Is it even possible to use Realm on Expo 52, anyone had success?

May 28 '25 16:05 jsmircic

Yes it is useable: running "expo": "~52.0.46", "react-native": "^0.77.1", and realm "realm": "^12.14.1". Got no issues. I only see this warning every now and then in development when hot reloading especially if it is in my data layer (TS files not TSX) but a simple closing and reopening the app fixes it.

Jun 06 '25 13:06 nojas01

Yes it is useable: running "expo": "~52.0.46", "react-native": "^0.77.1", and realm "realm": "^12.14.1". Got no issues. I only see this warning every now and then in development when hot reloading especially if it is in my data layer (TS files not TSX) but a simple closing and reopening the app fixes it.

Thank you, had a dependency hell but sorted it out, all good now 🥳

Jun 09 '25 11:06 jsmircic