feat(authenticator): Handle SignedIn events from outside of Authenticator #236
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.
Issue #, if available: #235
Description of changes:
Authenticator now reacts to
SIGNED_INevents it receives from Amplify. Historically it didn't do this because the idea was that you would only use Authenticator for Sign In, and not use Amplify APIs directly, but #235 rightly points out that you currently would use Amplify for social sign in via Cognito's web UI, which would leave Authenticator in an incorrect state.In this PR Authenticator listens to events from Amplify for when the user signs in. If the event is not expected (i.e. Authenticator is not currently in the process of calling a sign in API) then it reacts to the sign in by going directly to the
SignedInState.How did you test these changes?
Amplify.Auth.signIn)Amplify.Auth.signInWithWebUI)Amplify.Auth.signInWithSocialWebUI)Documentation update required?
General Checklist
fix(liveness): message,fix(authenticator): message,fix(all): message)By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.