oauthTokenRefreshException thrown but not using oauth flow about amplify-js HOT 13 CLOSED

If Amplify is used only on the client side, then you wouldn't need the SSR flag.

Strange, we kept the same key format between v5 and v6, so the refresh token should be there. Probably asking the end user to delete their keys and authenticate again might help.

from amplify-js.

I think the library might not being able to pull in the tokens from the current storage mechanism. Hence the error showed. Can you run your application and do the following,

1. authenticate.
2. call fetchAuthSession with the forceRefresh flag enabled.
3. check if the error was thrown
4. check where the tokens are stored

In addition to that, we added additional support for Next-JS as well and the configuration requires to pass the SSR flag.

Amplify.configure(config, {
  ssr: true // required when using Amplify with Next.js
});

from amplify-js.

Thank you for your response. I will let you know in the incoming weeks if happening regularly !

from amplify-js.

hello @clement-faure . Can you please expand how you are able to reproduce this issue ? Plase share,

• amplify configuration
• code snippets
• dev environment

from amplify-js.

the OAuthTokenRefreshException is usually thrown when storage doesn't have a refresh_token . Can you make sure tokens are stored in the cookies ?

from amplify-js.

Thank you for your quick response !

Amplify configuration :

Amplify storage mode (default localeStorage) :

When use click on remember checkbox true, storage in persisted in local storage, otherwise stored in cookies for session

from amplify-js.

I was not able to reproduce it on my own, i have a production environment with +1000 customer, and i got this error in my Sentry. This error happened after migrating to aws amplify v6

from amplify-js.

I'm gonna try that right away. I'm not using SSR on my application, do i have to enabled SSR flag necessarily ?
Amplify is only used on client side environment.

from amplify-js.

I confirm that all is working fine when reproducing your steps. Tokens are stored in local storage when "remember me" checkbox is checked, otherwise in cookies (like i've implement in my updateCognitoTokenSavingMechanism)

I think the error is linked to aws-amplify upgrade, my customer probably logged in on aws amplify v5, and when reloading app and refreshing token on aws amplify v6, the error has been thrown ? But it's not happening to all my customers.. very strange.

from amplify-js.

@clement-faure, I'll put the pending-response label on this issue for now until we hear back from you on implementing @israx's guidance above.

from amplify-js.

@clement-faure, wanted to check in and see if you're still experiencing this. Let us know if you are!

from amplify-js.

put the pending-response label on this issue for now until we hear back from you on implementing @israx's guidance above.

The issue didn't happened again so i think we can close this issue safely !

from amplify-js.

@clement-faure, appreciate the quick reply! I'll close this issue then for now, but feel free to leave further comments or context if this persists.

from amplify-js.