Hi @Paolo_Manna I should say, my initial expectation is that the syncManager.errorHandler block should be called when an error occurs (e.g. reset error or client reset while running).
But I’m not seeing the block getting triggered except when I restart the app. Unless I restart the app while sync is still terminated, in which case, I get no notifications.
I had a look at the underlying C++ code, and I don’t see a route to notification of failure apart from report_connection_state_change(ConnectionState::disconnected, &error_info); // Throws
But as far as I could see, the only way to see something might’ve gone wrong is by observing the connection state for a change from Connecting → Disconnected which I need a session for but if I use asyncOpen I don’t have a session?
I must have missed something?