-
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
Crash in table.hpp:251: [realm-core-10.1.4] Assertion failed: !key.is_unresolved() #3611
Comments
Seems to be related to the collection listener. It executes the first time and crashes on subsequent triggers.
|
@RosenTomov Thank you for the bug report. Do you only observe it on iOS? We have recently fixed a couple of logic errors in the notification system and we will try to see if your crash is related. |
Hello @kneth, the error was caused by a reference to a non-existent object. ex:
It's been working fine since we removed the id. We didn't get to test it on android. |
You shouldn't see a native crash but a JavaScript exception might be fine. |
I get the same error, and can reproduce it on demand. The strange thing to me is that it happens when updating a value. I suppose the object still exists ; it is just mutated. |
@euZebe great! Would you mind putting together a small project / guide on how to reproduce it?
|
That's non straight forward since it is an existing project I have just started on. I'll do my best.
The data is updated successfully, but I have not yet located exactly where the error is occuring. |
I went a bit further in the issue: I have a screen with two tabs, one for a patient form (which I can edit) and the other with acts related to this patient. When updating the patient from the form, the app closes and I get the above error. Here is a piece of code which produces the error:
Remarks:
I tried to reproduce it in a simple example but I did not manage to get the error yet. |
I have the exact same issue. If I do an update with
and I have an active listener, then my whole app crashes, but change is written. |
@euZebe Does |
This issue appears to be related to realm/realm-core#4175 and should be fixed in realm-js 10.3.0 or later (the core monorepo releases). |
@euZebe Please try to upgrade to v10.3.0. |
We tested it again by manually setting a reference to a non-existent object, now crashes the app and throws the following:
instead of the original error. iPhone SE Simulator - iOS 14.4 |
Hey @RosenTomov thanks for the update, glad to hear the assertion is fixed. |
Realm JavaScript v10.4.1 has the fixed mentioned above. I am closing the issue, and if you continue to observe the crash, please create a new issue. |
Replaced names with "App".
Crash Report
Steps to Reproduce
I think it was either from collection listener or filter query. Happened only once. I'm still trying to reproduce it.
Version of Realm and Tooling
Realm JS SDK - 10.2.0
React Native - 0.63.4
OS: MacOS Catalina 10.15.7
Client OS & Version: iPhone SE 2 Simulator iOS 14.4
The text was updated successfully, but these errors were encountered: