`RLMException` in unit tests about realm-swift HOT 3 CLOSED

➤ PM Bot commented:

Jira ticket: RCOCOA-2326

from realm-swift.

Realm's notifications require a scheduler to post the notifications on. By default we use the current thread's runloop (mostly since historically that's the only thing we could use), which these days only works on the main thread unless you've specifically gone out of your way to set up a runloop on the background thread.

The simplest way to fix your test is to add a .subscribe(on:) call to your Combine pipeline, passing in a serial dispatch queue. This will result in your .sink() block being called on that queue, so if you do anything more complicated there than call fulfill() thread-safety can get complicated. Notably you can't access the realm instance from within that block and instead have to use the values passed to it as a parameter.

A more complicated approach would be to confine your entire test to an instance of an actor and do realm = try! await Realm(actor: actor), but I have no idea if Quick has reasonable support for doing that.

from realm-swift.

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

from realm-swift.