Yavor Georgiev

I would recommend against homebrew - the self-hosted builders are not ephemeral and we should be able to provision what we need ahead of time instead of installing things during...

We still need a way to ask Core to asynchronously advance to latest and deliver notifications without locking up the calling thread - `RefreshAsync()` is unfortunately a public API and...

It doesn’t have to be a particular thread. The discarded .NET implementation called `RealmCoordinator::on_change()` from a worker thread, like the C++ `std::async`. `on_change()` is by definition thread-safe.

> `on_change()` is absolutely not thread-safe in the slightest Then I was very lucky 😅 We have users in .NET who need to programmatically advance to the latest read version,...

tl;dr We need an API like `Realm::refresh(std::function callback)`, where where when the callback is called the realm instance will have advanced to the latest version, and notifications will have been...

I advise against using `SyncSession::shutdown_and_wait()` because that blocks until _all_ sync sessions are closed and the sync client is shut down.

We could investigate fixing the `SyncSession` implementation to do what it advertises instead.

@Viktorianec can you tell if your app has been running in the background at the time the crashes happened? A possible cause might be trying to access the realm file...

Hey @tomkrikorian, thanks for reporting this. Can you share the schema of your app? A small Xamarin or console app project that reproduces the problem would also be invaluable.

You can email it to [email protected] and mention realm-dotnet#2977 in the subject line.