Realm accessed from incorrect thread. #4410
Assignees
Labels
Comments
kneth
added a commit
to realm/realm-core
that referenced
this issue
Jun 16, 2022
4 tasks
kneth
added a commit
to realm/realm-core
that referenced
this issue
Jun 17, 2022
3 tasks
kneth
added a commit
to realm/realm-core
that referenced
this issue
Jun 20, 2022
kneth
added a commit
to realm/realm-core
that referenced
this issue
Jun 24, 2022
kneth
added a commit
to realm/realm-core
that referenced
this issue
Jun 27, 2022
* Client reset: use ThreadSafeReference instead of SharedRealm (related to realm/realm-js#4410) * Update C API * Modify tests - object store and C API Co-authored-by: Brian Munkholm <[email protected]>
|
Fix in core has been merged and we are waiting for a release |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
How frequently does the bug occur?
All the time
Description
When using client reset with discard local, one callback fails.
Stacktrace & log output
libc++abi: terminating with uncaught exception of type Napi::Error: Realm accessed from incorrect thread.Can you reproduce the bug?
Yes, always
Reproduction Steps
See #4361
Version
11.13.0
What SDK flavour are you using?
MongoDB Realm (i.e. Sync, auth, functions)
Are you using encryption?
No, not using encryption
Platform OS and version(s)
node.js
Build environment
Which debugger for React Native: ..
Cocoapods version
No response
The text was updated successfully, but these errors were encountered: