Realm 0.97 throws if notification block is added on thread without runloop #52
Labels
Comments
|
Just faced this problem. Really w8 for fix. =) |
|
Yeah sorry about this probably will be a day or two before I can implement my solution. |
bigfish24
pushed a commit
to realm/realm-swift
that referenced
this issue
Jan 5, 2016
… a thread without a runloop as long as we are on the same thread as the transaction, since the calling of the block won't occur via the named pipe. This is a strange use-case but came up with RBQFetchedResultsController via RBQRealmNotificationManager: Roobiq/RBQFetchedResultsController#52 RBQRealmNotificationManager registers a notification block on the same thread as the transaction, which is probably not a common use-case beyond a component like this.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
RBQRealmNotificationManager, should be refactored to use a singleton worker thread that will receive the Realm notifications and pass along changes toRBQFetchedResultsControllerso that the dev never has to worry about passing changes toRBQRealmNotificationManageron a background queue/thread that doesn't have a runloop.The text was updated successfully, but these errors were encountered: