You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create a new React Native Project with npx react-native init TestProject, add Realm npm i realm, create some Schema, add a Listener and sort or filter
Code Sample
consttodoListener=(collection,changes)=>{// if you comment sorted and filtered out, the App will work with the debugger//collection.sorted('name');console.log(collection.filtered('name == $0','test'));setTodos(collection);};
Version of Realm and Tooling
Realm JS SDK Version: realm 6.1.0
React Native: 0.62.2
Client OS & Version: Ubuntu Mate 18 LTS
Which debugger for React Native: Chrome
The text was updated successfully, but these errors were encountered:
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).
Using Chrome Debugger and using sorted or filtered on Realm Collection kills the Application
Goals
Using the Chrome Debugger with Realm and sorting/filtering Realm Objects
Expected Results
App not crashing ...
Actual Results
App crashes as soon as the Debugger connects and the filtered or sorted action happens.
Steps to Reproduce
Either fork this small Project https://github.com/Shumuu/RealmSnapshot or
Create a new React Native Project with
npx react-native init TestProject
, add Realmnpm i realm
, create some Schema, add a Listener and sort or filterCode Sample
Version of Realm and Tooling
The text was updated successfully, but these errors were encountered: