Authenticated user commands such as fetchUserAttributes, fetchAuthSession, getCurrentUser hang without response

[Dante-Capobianco]

Before opening, please confirm:

• I have searched for duplicate or closed issues and discussions.
• I have read the guide for submitting bug reports.
• I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

Amplify APIs

Authentication

Amplify Version

v6

Amplify Categories

No response

Backend

None

Environment information

# Put output below this line

Describe the bug

When trying to call fetchAuthSession or user attributes or get current user in the frontend (to see if user exists before signing them in, nothing happens. It just hangs there with no message or network call & the console statements I put right after it do not hit (but the ones before do). I am using await & I have properly configured my Amplify because other commands like confirmsignup work (make the network call & return a response)

A simple example is the following:

console.log('hit1')
console.log(await fetchUserAttributes());
      console.log('hit2')

Expected behavior

Expect network call to be made then to get error because no user found to catch.

Reproduction steps

1. Install aws amplify and aws-amplify-auth
2. set up amplify using .configure
3. make calls to these functions

Code Snippet

// Put your code below this line.

Log output

// Put your logs below this line

aws-exports.js

No response

Manual configuration

No response

Additional configuration

No response

Mobile Device

No response

Mobile Operating System

No response

Mobile Browser

No response

Mobile Browser Version

No response

Additional information and screenshots

No response

[Simone319]

Hello @Dante-Capobianco , thank you for reporting this issue. We will try to reproduce the issue on our end, and provide an update.

[Dante-Capobianco]

[like] Dante Capobianco reacted to your message:

…

________________________________ From: Simone319 ***@***.***> Sent: Thursday, July 31, 2025 10:02:33 AM To: aws-amplify/amplify-js ***@***.***> Cc: Dante Capobianco ***@***.***>; Mention ***@***.***> Subject: Re: [aws-amplify/amplify-js] Authenticated user commands such as fetchUserAttributes, fetchAuthSession, getCurrentUser hang without response (Issue #14490) [https://avatars.githubusercontent.com/u/24464634?s=20&v=4]Simone319 left a comment (aws-amplify/amplify-js#14490)<#14490 (comment)> Hello @Dante-Capobianco<https://github.com/Dante-Capobianco> , thank you for reporting this issue. We will try to reproduce the issue on our end, and provide an update. — Reply to this email directly, view it on GitHub<#14490 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BE6RN44X27R7UI2LM4QMFJ33LHSTTAVCNFSM6AAAAACCXGHBCCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCMZZGMYDOMJTGA>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[Simone319]

Hello @Dante-Capobianco,

I'd like to clarify: are you calling fetchUserAttributes, fetchAuthSession, or getCurrentUser before the user has signed in?

If so, you should observed error message such as User needs to be authenticated to call this API. The reason why you didn't observe network call is that these APIs don't make network calls to Cognito - instead, they read authentication data from local storage that's only populated during the sign-in process.

[Dante-Capobianco]

Hello @Dante-Capobianco,

I'd like to clarify: are you calling fetchUserAttributes, fetchAuthSession, or getCurrentUser before the user has signed in?

If so, you should observed error message such as User needs to be authenticated to call this API. The reason why you didn't observe network call is that these APIs don't make network calls to Cognito - instead, they read authentication data from local storage that's only populated during the sign-in process.

Yes, let me clarify: I expected these auth functions to return an error message (like they are successfully doing in my SSR setup in middleware) but it is simply hanging. It makes sense that I would not see a network call, but the issue is with it hanging then any code following these function calls simply do not run (confirmed with console statements only running beforehand). This issue also spreads to the sign in function calls (and likely many others I currently am not using in my logic) where it's hanging.

[Simone319]

Hello @Dante-Capobianco , now I understand your ask is to be able to handle the error, so that the following code can continue to run. Have you tried catching the error? I'm able to wrap the fetchUserAttributes() in a try-catch block and continue the code execution.

console.log('hit1')
    try {
      await fetchUserAttributes()
    } catch (error) {
      console.log(error.message)
    }
    console.log('hit2')

Console log:

hit1
User needs to be authenticated to call this API. 
hit2

Let me know if this is the experience you're looking for.

[Dante-Capobianco]

Hello @Dante-Capobianco , now I understand your ask is to be able to handle the error, so that the following code can continue to run. Have you tried catching the error? I'm able to wrap the fetchUserAttributes() in a try-catch block and continue the code execution.

console.log('hit1')
    try {
      await fetchUserAttributes()
    } catch (error) {
      console.log(error.message)
    }
    console.log('hit2')

Console log:

hit1
User needs to be authenticated to call this API. 
hit2

Let me know if this is the experience you're looking for.

Hello, yes this is it. Instead of logging the error then hit2 it simply hangs and only logs the first "hit" statement. One thing I've noticed is the only time it works in my frontend code is before the component hydrates/finishes mounting, where the error logs in my backend, then for all future instances it simply hangs. The intention is not to run fetchuserattributes & other functions at the root level to run on every re-render, but I did this as a test to see when it does and does not work

It is strange that I've only seen confirm sign up work, while sign in, fetchauthsession, fetchuserattributes, getcurrentuser, etc don't work