-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Bad Version Exception when delivering change notifications #4660
Comments
@sblepa could you please share more information about this crash? Short of a full Xcode project that we can run to trigger the exception, it'd be useful to know what the contents of your notification block is, including the query or object being observed. Thanks. |
@jpsim Thanks for the reply, unfortunately I can't share my project code here, also I can't reproduce it manually, it happens randomly (although it happens most when I go into a certain screen in the app). What is much more worrying and I think is a side effect of this issue, is sometimes after I get the BadVersion, I get stuck in a lock waiting for a Realm transaction to start, this happens on the main thread which causes the main thread to stop responding, and it never gets released, this is also something I can't reproduce manually but happens quite a lot in the current version, I'll paste here the stack trance of all threads when it gets stuck:
|
@jpsim Please let me know if you suggest to downgrade my Realm version for now |
Hi @sblepa. You can also email us your Xcode project privately at help@realm.io. Please reference this issue in the body of the email and let us know if you decide to. |
Hi @sblepa, it's hard for me to recommend that you downgrade to a previous version of Realm considering that most releases fix more bugs than they cause, but if a version of Realm is catastrophically failing for you, then obviously you need to do something to avoid that. However, we'd much rather you shared with us how we can trigger this bug so we can not only help you with it, but also hopefully prevent others from hitting it. |
The fix for this shipped in 2.4.4. |
Great news thanks, can you please share the commit for this fix? |
The commit is in the object store repository, and can be viewed here (SHA in URL). Note that, although the fix was pushed on the 19th of January, the updated version of the object store dependency containing that fix (and all subsequent fixes) wasn't actually pulled into a Cocoa release until 2.4.4. |
This appears to be a slightly different issue than #4144. Caught with Realm 2.4.2. Backtrace:
Re-posted from #4144 (comment).
The text was updated successfully, but these errors were encountered: