nicola cabiddu

@papafe I read your implementation and tried to understand the issue myself. But I don't, at least not fully. It seems you have this method in your library that checks...

> ExternalCommitHelper OK, but core cannot know which thread it is that would be calling `RefreshAsync`. I'll talk to @tgoyne in order to understand his proposal.

@fealebenpae do you think exposing `get_version_of_latest_snapshot()` will make it possible for the SDKs to build such functionality? The only problem I have with building such a thing inside core is...

yes @nirinchev ...

Isn't this already covered by this? https://github.com/realm/realm-core/pull/5540 We miss: 1. Exposure in the C API 2. Async version.

OK so it seems we have 2 different issues: 1) close and delete for good everything if init data callback fails (we don't need to expose this). I think that...

> OK, I see what you mean. I don't see an easy solution, though. You can either block until all the sessions are closed or signal that all the sessions...

Adding @danieltabacaru in order to understand how complex would it be to fix this API before to expose it in the C API

> We could investigate fixing the `SyncSession` implementation to do what it advertises instead. What will this fix do? This is not clear to me. You don't want the client...

> realm_app_sync_client_wait_for_sessions_to_terminate I would say we need this to allow SDKs to unlink successfully realm files on Windows. All the SDKs that run on Windows have this problem of needing...