Shape of the consumer-defined parameters the sync notification carries (device ids, type filters…).
Optional ReadonlyonFires when a previously-available session is definitively lost:
the boot-time restore found persisted state but could not sign
in, or a sync cycle ended unauthenticated after the auth-retry
chain gave up. The auto-sync disarms at the same moment
(rescheduling would hammer the account with a doomed sign-in
every cycle); a successful authenticate() — e.g. the user
logging back in — re-arms it. Fires once per loss episode.
Optional ReadonlyonFires when a sync cycle ends authenticated after an
onAuthenticationLost episode — the user logged back in or a
retry recovered the session. Fires once per loss episode, so the
two events always alternate.
Optional ReadonlyonInvoked after a successful HTTP response is received.
Optional ReadonlyonInvoked when a request fails permanently (retries exhausted).
Optional ReadonlyonInvoked before each backoff-scheduled retry attempt.
Optional ReadonlyonInvoked when a request is dispatched for the first time.
Optional ReadonlyonInvoked after each sync trigger (auto-timer or a sync-decorated mutation), with the consumer-defined scoping parameters.
Callback bundle invoked around SDK lifecycle moments. All callbacks are optional and non-throwing — the SDK ignores any exceptions they raise so a buggy observer cannot break the request flow.
Two scopes coexist here:
onRequest*) — fires for every outgoing HTTP call.onSyncComplete) — fires after each sync trigger (auto-timer OR a sync-decorated mutation), once the downstream device state has been refreshed.