This repository has been archived by the owner on May 13, 2023. It is now read-only.
fix: use _notifyException to handle recoverSession errors #131
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.
What kind of change does this PR introduce?
Currently, the only way to listen to exceptions thrown during
recoverSession
is to handleSupabaseAuth.initialSession
, which I think we should move away from, since it's a weird design pattern to just have a variable just for the initial session.This PR allows users to listen to errors emitted on
recoverSession
by addingonError()
ononAuthStateChanged
. So that it is easier to handle the initial auth exceptions as well as on going exceptions happening during token refresh can be all handled throughonAuthStateChanged
.