-
Notifications
You must be signed in to change notification settings - Fork 585
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enabling React Native Debug mode causes Error: _expandEmbeddedObjectSchemas must be of type 'function', got (undefined) #3442
Comments
This is happening also in android with the example of the docs. If debug mode is not enabled, works like a charm. |
Thanks for reporting this. I admit (and this is truly unfortunate) that we don't have in-depth integration tests for our library when running in Chrome debugging mode. The app that I was using to test the fix in #3411 inferred its schema, which lead to the unfortunate consequence that I didn't catch this case when solving the other issues. I have a PR ready with a fix for this in #3446, which is currently in review and you can expect a new release as soon as this gets merged. Thank you all for your patience on this. |
I am facing the same issue i think the issue is still open |
Support for the React Native Chrome debugger with Realm is being deprecated, as it is no longer the recommended way to debug React Native applications. In our case, supporting the Chrome debugger requires many extra layers of indirection and workarounds, which means it does not work especially well and has a high maintenance overhead. Instead we are moving to supporting the Flipper debugger, which will become the recommended way to debug React Native apps once the React Native project's migration to the Hermes engine is complete (at which point the Chrome Debugger will not work anywhere). Please see our beta branch with Hermes support to try it out and provide feedback. Thanks for your patience! |
@tomduncalf I saw the error message that realm isnt compatible with chrome debug tools and supports flipper . I tried using flipper now I am getting the ""RSockets are being deprecated at Flipper. Please, use the latest Flipper client in your app to migrate to WebSockets." I am not sure how to proceed since flipper was automatically installed in my app . And upon using flipper my app starts hanging/crashing. The relevant versions are as follows: |
@KaulSalil unfortunately Tom is no longer on the Realm JS team. As a general advice, please consider creating your own issue. This will increase your likelihood of a fast resolution. In this particular instance, you should upgrade your app to the latest version of React Native to get the "latest version of the Flipper client in your app". |
To make React Native use the latest compatible flipper version see https://fbflipper.com/docs/getting-started/react-native/ "Latest version of Flipper requires react-native 0.69+! If you use react-native < 0.69.0, please, downgrade react-native-flipper to 0.162.0 (see this GitHub issue for details)." |
@ws333 I tried using the latest version of everything (realm,react-native,react)[maybe I need to update flipper on the native side as well ] but I wasnt able to get flipper to work along with realm react native . I have been referring to the : https://www.mongodb.com/docs/realm/sdk/react-native/test-and-debug/debugging-with-flipper/ but havent been able to get it to work . In case react-native+realm+flipper works at your end please share the versions you are using . Opened a github issue for the same as well: #5440 |
Goals
Enable React Native Debug mode in order to troubleshoot console errors, set breakpoints, profile app, and monitor network requests.
Expected Results
Mobile app connects to React Native Debugger successfully and I'm able to set breakpoints, profile app, and monitor network requests, view console errors
Actual Results
Mobile App crashes with the following error
Steps to Reproduce
yarn ios
to build react native application and install on device.Code Sample
Version of Realm and Tooling
The text was updated successfully, but these errors were encountered: