Hui Zhao

Hi @nerdifydev, thanks for providing the details. >It throws an error in the catch block of Auth.currentSession. Do you have any details of the caught error, such as the message...

Thanks for the addition details @nerdifydev, also and @ashishsoniDotsquares do you get the same error when this issue happened? Could you both determine, did this happen at a occasion, for...

Sorry about the segmented requests @nerdifydev could you also confirm, after the `error Network error` happened, was the end user able to continue using the app, e.g. re-signing in, and...

Hi all, [[email protected]](https://github.com/aws-amplify/amplify-js/releases/tag/aws-amplify%405.3.25) is now released, it uses a retry logic now on failed service calls for refreshing sessions.

Hi @danielshin @brianlenz in v6 the `getCurrentUser()` reads only locally persisted `accessToken`, and it doesn't attempt to make any service call over network. If the `accessToken` doesn't exist it throws...

Hi all, we've started testing the code changes with Next.js v15. Thanks for your patience.

Hi all, the Next.js 15 support is now testable with the tag release `next-15`. You can start testing with your project by installing the tag version ```shell npm install aws-amplify@next-15...

Hi @austinjlaverty thanks for following up. For `getCurrentUser(contextSpec)` call we have integration tests that verified it should work with Next.js 15 with the tag release. Can you provide your server...

Hi @akamfoad you analysis is correct regarding this issue. `Amplify` is a singleton to serve the configuration and common states, you need to ensure all your packages are using the...

> I'm surprised that the formal Amplify documentation say that Next JS 15 is supported but this is still open and the latest version of the next-adapter does not support...