Abhi Patel

+1 on falling back to IAM if there are no userpool credentials

Hi @chrisbonifacio, thanks for the quick response! So in that repro example, if you reload the page, are there no more cognito-identity calls on the second one since we pull...

@chrisbonifacio upgraded to 6.2.0, and still having the same issue, so I don't think its a version issue! Please let me know if there's any other information I can provide....

Hi @chrisbonifacio, just wondering if there is an update here!

> @cwomack Please let me know if I understand correctly: calling `Auth.signIn()` on the server-side (i.e inside a server component/action) will **NOT** set the cookies? from what i understand, authentication...

Hi @nadetastic thank you for the response! That code snippet works for me as well, and I am able to see the custom claims in my next app as well....

@nadetastic Yeah, the call hits our lambda code, which gets called from Appsync. The appsync resolver, `getCurrentUser(input: GetCurrentUserInput): UserDetails!` which is connected to the lambda code that just prints the...

So fetchUserId is just a simple wrapper around the Auth library ``` export const fetchUserId = async (Auth): Promise => { try { const userId = (await Auth.currentAuthenticatedUser()).signInUserSession.idToken.payload.ID; refreshToken(Auth); return...

After doing some digging, I can see that the error happens here: https://github.com/aws-amplify/amplify-js/blob/736918491e74d9aefb543fa4e531efe867195521/packages/api-graphql/src/GraphQLAPI.ts#L285 https://github.com/aws-amplify/amplify-js/blob/736918491e74d9aefb543fa4e531efe867195521/packages/api-graphql/src/GraphQLAPI.ts#L170-L177 However, when running the same function in my getServerSideProps call, `Auth.currentSession().getAccessToken().getJwtToken()`, it return the token successfully....

Also some other info that we found out: The error that we were getting, No Current User, has been fixed! We figured out the issue happened since we had been...