Mmmm but periodically in this case is 1 hour?
Our use case is interesting because we have a limited number of clients, it’s ok to show an activity indicator if something were to go wrong on the server e.g. Sync crashes, but it is critically important that they reconnect asap. In our use case 1 hour is not appropriate. Which is why I’m so keen to restart asap.
The error handler is called with a valid session in other cases:
- When sync is reset while the app is running, and you’ve a session opened already
From your reply, I understand that I should expect app.syncManager.errorHandler to be called if I do not have a session. And I would expect .failure(error) from the Realm.asyncOpen block if I have a valid session.
I placed breakpoints in both place and tried pausing and terminating syncing after a successfull connection as well as restarting the app while the pause and terminate conditions were true. But no breakpoints were hit. Only the logs gave an indication there was an issue.
I’m using v10.21.1 of Realm. Is there some set of configuration ot debug options that would cause this?