You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please include any relevant guides or documentation you're referencing
No response
Describe the bug
When Authenticator does a fetch auth session when launching it can get an ExpiredSessionException. If this happens it shows the Sign In screen again, but any attempts to sign in result in a SignedInException because there is already a user signed in.
This may be a bug in Amplify itself (to be verified if this expected), if not then this should be handled within Authenticator.
Reproduction steps (if applicable)
In your cognito pool set your refresh token expiry to 60 minutes. This is under App Integration > client. (this is not necessary, but makes the issue much easier to reproduce)
Sign in with a user
Let the refresh token expire
Launch the app again, sign in screen will re-appear
Try to sign in again
Expected: Sign in is successful
Actual: "Something went wrong"
Code Snippet
// Put your code below this line.
Log output
// Put your logs below this line
amplifyconfiguration.json
No response
Additional information and screenshots
No response
The text was updated successfully, but these errors were encountered:
So, the fix for this problem should have been released with Authenticator v.1.2.3
I tested this but unfortunately the sign-in is still not possible, here is the logs from Authenticator:
Moving to initial step: com.amplifyframework.ui.authenticator.enums.AuthenticatorStep$SignIn@42a7884
Moving to step: com.amplifyframework.ui.authenticator.enums.AuthenticatorStep$SignIn@42a7884
Encountered AuthException: SignedInException{message=There is already a user signed in., cause=null, recoverySuggestion=Sign out the user first before signing in again.}
Sending message: com.amplifyframework.ui.authenticator.util.UnknownErrorMessage@a46ea43
I suppose, after some debugging, that the fix was made to handleSignedIn() -method but it also needs to be fixed in handleSignInFailure()?
This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
Before creating a new issue, please confirm:
Which UI component?
Authenticator
Gradle script dependencies
// Put output below this line
Environment information
Please include any relevant guides or documentation you're referencing
No response
Describe the bug
When Authenticator does a fetch auth session when launching it can get an
ExpiredSessionException
. If this happens it shows the Sign In screen again, but any attempts to sign in result in aSignedInException
because there is already a user signed in.This may be a bug in Amplify itself (to be verified if this expected), if not then this should be handled within Authenticator.
Reproduction steps (if applicable)
Expected: Sign in is successful
Actual: "Something went wrong"
Code Snippet
// Put your code below this line.
Log output
amplifyconfiguration.json
No response
Additional information and screenshots
No response
The text was updated successfully, but these errors were encountered: