Maybe have a separate (injectable) error manager that does notifications and for instance can also group errors of various collections? But that could also be a new issue.
Depends on #877. See also #886 – it probably makes sense to think about error handling when defining the sync result data type.
Currently, handling of sync errors is scattered between various locations:
Syncer
throws errors (for instance when the content provider is not available, after #877) and handles others (SecurityException
,DeadObjectException
)SyncManager
throws and handles other errors (per collection)We should
and refactor accordingly.
Maybe have a separate (injectable) error manager that does notifications and for instance can also group errors of various collections? But that could also be a new issue.
Depends on #877. See also #886 – it probably makes sense to think about error handling when defining the sync result data type.
Depends on #896