Add specific exception for auth errors being sent to to the Sync Session error handler #1643
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #1640
This adds a specific exception class for auth errors being sent to the SyncSession error handler. This is relevant as this indicates the user's credentials are no longer valid and they need to log in again.
Some open questions:
SyncException
when we already haveAuthException
underAppException
. But relaxing the interface would be a breaking change and besides, this is the only "App" type exception that would surface here anyway.SyncSessionExpiredException
,SyncAuthException
,SyncSessionAuthExpired
. ChoosingAuthExpiredException
was somewhat arbitrary, except it felt short and to the point. Not sure ifSync
orSession
should somehow be part of the name to separate it more from the genericAuthException
that is anAppException
. All our other specific exception types end withException