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
First of all, we have a custom wrapper around Realm, for us to be able to manage entities and everything related with our database.
Seems like version 10.40.2 introduced Actor.preconditionIsolated() for runtime actor checking which causes the following error:
The fundamental issue seems to be the same though - you're trying to use a Realm on the wrong thread/actor. It implies that the methods you're calling on your database manager are not executing on the correct actor (which appears to be the database manager itself).
What do you mean? I haven't audited the code you posted, but as I said, the fundamental problem is that you're accessing the same realm from multiple actors, which is not allowed.
I ended up using a DispatchQueue instead of actors, but thanks, If you want to see the final implementation please let me know, if not just close the discussion
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
First of all, we have a custom wrapper around Realm, for us to be able to manage entities and everything related with our database.
Seems like version 10.40.2 introduced
Actor.preconditionIsolated()for runtime actor checking which causes the following error:RealmSwift/Realm.swift:1468: Precondition failed: Incorrect actor executor assumption; Expected 'UnownedSerialExecutor(executor: (Opaque Value))' executor.This is the wrapper I talked about.
Here are my fails to migrate it.
ThreadSafeReference(to: entity)andrealm.resolve()I really want to understand how can I migrate this wrapper to be able to keep track of all Realm updates
All reactions