Hui Zhao

Thanks for the additional information @brianlenz I was able to reproduce this unexpected token clearing. Apologies for my misunderstanding, the `getCurrentUser()` does trigger a service call when the `accessToken` is...

Hi @brianlenz we release v6.6.7 with should fix this unexpected token clearing behavior. Details please see the linked PR description. Please upgrade and test again, thanks!

Hi @brianlenz I was able to reproduce with the following conditions: 1. The persisted access token is expired 2. The device has spotty network connection The expected behaviors is: 1....

Hi @matt-prinold-grazinga thanks for reaching out. With Amplify Gen2, setting up the data resources and modeling the schema are done by TypeScript. That's a separate process from write your Flutter...

Oh good find, thanks for pointing this out @matt-prinold-grazinga, IIRC, Amplify Flutter doesn't have the corresponding automatically generated `listBy` methods. I will mark this a bug and look into how...

Hi @thedevopsguyblog at a glance I don't think the issue you encountered is unrelated to this one. Were the request headers you pasted were from the requests sent to your...

Hi @thedevopsguyblog when you call `Amplify.configure()` on the client-side of your app, have you specified `{ ssr: true }`? From your description it sounded like the Amplify client-side functionalities are...

Hi @thedevopsguyblog sorry for about the delayed response. Could you provide a minimal next.js app that can reproduce the issue you encountered?

Hi @mattiLeBlanc yes we are looking into this. Thank your for your patience.

> I'm experiencing this too. Multi auth roles present on models, unauth users experience `NoValidAuthTokens: No federated jwt` when they should be at least able to `{ allow: public, operations:...