The Android Bundling completes successfully apparently but when I select the app in the “development servers” screen of the dev-client on my Android device I have the following error:
ERROR Error: Exception in HostObject::get(propName:Realm): java.lang.UnsatisfiedLinkError: couldn’t find DSO to load: librealm.so caused by: dlopen failed: cannot locate symbol “__emutls_get_address” referenced by “/data/app/~~RByWYhVyWSSKeF6nBOxNCg==/com.anonymous.realm11-yQ4HV5E7diRX4gos2lNp9w==/lib/arm64/librealm.so”… result: 0
ERROR 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.** ERROR 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**
What annoys me the most, apart from the fact that I lost hours on this problem already, is that I did not change anything in the @realm/expo-template-ts template. I may have missed something but it seems that the template and the procedure provided by MongoDB does not work today.
I haven’t been able to build an Expo + Realm app in the past month. Not a single template/repo/tutorial works. Truly disappointing. Our development has been stopped pretty much and it doesn’t look like they are gonna fix it anytime soon.
I had to change Task.ts (without babel) and I added some nice traces.
I tested it on my Android device with USB cable and I used the local Expo CLI recomended by expo not the global one recommended by mondoDb. That’s another proof that MondoDB does not maintain and test Realm on React Native at the moment.
Thank you for the help. I was able to run the app successfully in the android emulator, but not in Expo Go. I uninstalled expo-cli from global and installed it locally, but still getting a warning that the command npx expo start --dev-client is getting executed from he global package. I am unable to get the app to run with Expo Go on my android phone even with an USB cable ( I am also running on windows 10):
Error: Missing Realm constructor. Did you run "pod install"? Please see https://docs.mongodb.com/realm/sdk/react-native/install/ for troubleshooting
at node_modules\react-native\Libraries\Core\ExceptionsManager.js:null in reportException
at node_modules\react-native\Libraries\Core\ExceptionsManager.js:null in handleException
at node_modules\react-native\Libraries\Core\setUpErrorHandling.js:null in handleError
at node_modules\expo-dev-launcher\build\DevLauncherErrorManager.js:null in errorHandler
at node_modules\expo-dev-launcher\build\DevLauncherErrorManager.js:null in <anonymous>
at node_modules\expo\build\errors\ExpoErrorManager.js:null in errorHandler
at node_modules\expo\build\errors\ExpoErrorManager.js:null in <anonymous>
at node_modules\@react-native\polyfills\error-guard.js:null in ErrorUtils.reportFatalError
at node_modules\metro-runtime\src\polyfills\require.js:null in guardedLoadModule
at http://192.168.100.7:19000/index.bundle?platform=android&dev=true&hot=false&strict=false&minify=false:null in global code
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.
at node_modules\react-native\Libraries\Core\ExceptionsManager.js:null in reportException
at node_modules\react-native\Libraries\Core\ExceptionsManager.js:null in handleException
at node_modules\react-native\Libraries\Core\setUpErrorHandling.js:null in handleError
at node_modules\expo-dev-launcher\build\DevLauncherErrorManager.js:null in errorHandler
at node_modules\expo-dev-launcher\build\DevLauncherErrorManager.js:null in <anonymous>
at node_modules\expo\build\errors\ExpoErrorManager.js:null in errorHandler
at node_modules\expo\build\errors\ExpoErrorManager.js:null in <anonymous>
at node_modules\@react-native\polyfills\error-guard.js:null in ErrorUtils.reportFatalError
at node_modules\react-native\Libraries\BatchedBridge\MessageQueue.js:null in __guard
at node_modules\react-native\Libraries\BatchedBridge\MessageQueue.js:null in callFunctionReturnFlushedQueue
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.
at node_modules\react-native\Libraries\Core\ExceptionsManager.js:null in reportException
at node_modules\react-native\Libraries\Core\ExceptionsManager.js:null in handleException
at node_modules\react-native\Libraries\Core\setUpErrorHandling.js:null in handleError
at node_modules\expo-dev-launcher\build\DevLauncherErrorManager.js:null in errorHandler
at node_modules\expo-dev-launcher\build\DevLauncherErrorManager.js:null in <anonymous>
at node_modules\expo\build\errors\ExpoErrorManager.js:null in errorHandler
at node_modules\expo\build\errors\ExpoErrorManager.js:null in <anonymous>
at node_modules\@react-native\polyfills\error-guard.js:null in ErrorUtils.reportFatalError
at node_modules\react-native\Libraries\BatchedBridge\MessageQueue.js:null in __guard
at node_modules\react-native\Libraries\BatchedBridge\MessageQueue.js:null in callFunctionReturnFlushedQueue
Because “npx expo run:android” called “npx expo prebuild”, the app escapes from the “managed workflow”.
So you can’t use Expo Go anymore. But that’s perfectly fine because you now have an “Expo Development client” that can now contain the native android code of Realm and that can be used in the same maner as Expo Go.
Okay, thanks. I think I am understanding what you are explaining. I will have to do a bit of reading, new to mobile development. Just one final question that is of the most important to me: Will I be able to use EAS (Expo App Services) to publish and update my app?
Hey all (@Damian_Danev@Gilles_Jack)! It seems our templates did not have versions for realm and react-native pinned, so the ended up causing issues when new releases came out. We just made a release of the expo template that should now work out of the box. Let us know if you run into any issues. Thanks!
PS - in regards to Expo Go, this app is unfortunately not compatible with realm or any other third party library that isn’t part of the base Expo SDK. Although Expo Go, is a great way to get going and familiarize yourself with React Native, it’s unfortunately not built for adding third-party libraries to it on the fly (unless they are pure JS libraries). But through the dev-client one is able to build their own custom “Expo Go”-ish app which one can use to update code live to whatever device is running it. More information
I won’t test the new template myself because this procedure still requires to install expo-cli globally which is not recommanded by Expo and can cause problems.
Moreoverver, realm 11.7.0 still does not work in my react native project (“react”: “18.1.0”, “react-native”: “0.70.8”). I get the following error at launch :
Android Bundling complete 11692ms
ERROR Error: Exception in HostObject::get(propName:Realm): java.lang.UnsatisfiedLinkError: couldn't find DSO to load: librealm.so caused by: dlopen failed: cannot locate symbol "__emutls_get_address" referenced by "/data/app/~~03La_fqEioklXzthzhDdmA==/com.podcastcutter1-Q7Dmqzp7e-cL_yoxCHSZWQ==/lib/arm64/librealm.so"... result: 0
ERROR 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.
ERROR 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.