Hui Zhao

Hi @mkolbusz The fix for this issue has released with `[email protected]` and `@aws-amplify/[email protected]`, please upgrade to these versions. Thanks!

Hi @OrmEmbaar thanks for following up. When the access token and refresh token are both expired and the library attempts to refresh the tokens from the server side, it will...

Hi @OrmEmbaar I think I understood. In this case the Amplify library couldn't predict the paths you may have, so the cookies couldn't be removed. I think it may require...

Thanks for the follow up again @OrmEmbaar >Do you know under what conditions they expire in a week vs a year? The expiration period of the access token, ID token...

I'm closing this issue as the originally reported bug has been fixed. Please feel free to reach out if anything we can help with.

Hi @ndaba1 your issue seemed different from the OP, I will follow up in your linked issue. Please take a look there.

Hi @mattiLeBlanc I dug into the GraphQL API implementation and how it uses the `headers` callback function specified in the `libraryOptions`. It looks like a `.graphql()` call always calls `fetchAuthSession()`...

Hi @mattiLeBlanc >What happens is we can logout a user from the client app via the admin app, by revoking their refresh token. Then when the user navigates anywhere in...

Hi @mattiLeBlanc > Does the accessToken renewal trigger an unauthorised error on the first graphql request and then automatically fetch a new accessToken and try the query again, or will...

Hi all, we re-evaluated this issue, and we agree with that the patch provided above makes sense. We will be looking into merging the patch soon.