[Authenticator] Sign-in fails after refresh token has expired

[pmellaaho]

Before creating a new issue, please confirm:

• I have searched for duplicate or closed issues.
• I have read the guide for submitting bug reports.

Which UI component?

Authenticator

Gradle script dependencies

// Put output below this line
authenticatorVersion = "1.2.3"

Environment information

# Put output below this line
Gradle 8.7

Please include any relevant guides or documentation you're referencing

#145

Describe the bug

So, the fix for this problem should have been released with Authenticator v.1.2.3
#145

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 maybe it also needs to be fixed in handleSignInFailure()?

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)

1. Sign in with a user
2. Let the refresh token expire
3. Launch the app again, sign in screen will re-appear
4. Try to sign in again
5. 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

[mattcreaser]

Agree this should have been resolved. We'll need to take a look at why it wasn't.

[pmellaaho]

I was really happy to find out that after updating to Authenticator 1.3.0, the sign-in started working in the above mentioned scenario. I really don't know why that is but that seems to be the case.

[github-actions]

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.

[mattcreaser]

Looked into this briefly and in Authenticator 1.2.3 the Amplify dependency was still on 2.18.0 - it should have been updated to a newer version in that release, but wasn't. The dependency was updated to Amplify 2.21.1 in Authenticator 1.3.0.

The actual fix was in Amplify 2.19.1, so this is why it wasn't resolved in Authenticator 1.2.3.