alex-breen

@nadetastic Has this bug regressed? I encounter the bug on Chrome and Safari with Authenticator on latest: "aws-amplify": "^6.0.26", "@aws-amplify/ui-react": "^6.1.6",

Hi @cwomack - My cognito settings are: > Refresh token expiration: 30 day(s) > Access token expiration: 1 hour(s) > ID token expiration: 1 hour(s) Does this happen in prod?...

Update: On production, I've encountered the issue twice (about every 24 hours). The console logs show the errors: ``` Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'cognito:username')...

Another update (reproduction is slow because it seems to occur after several hours of sleep or inactivity): - Cognito is able to re-establish a connection (token refresh?) on its own...

I have Hub logs with today's failed sync. I hope this is helpful. .Steps to repro: wake up from sleep. What I see is that the Hub says the model...

Do you recommend I call `Datastore.start()` after the Hub event "ready"? My aim is to reset the sync process for cases in which it thinks it is syncing, but it...

@svidgen - I don't think so, as no error events are passed. Datastore events indicate everything is working (syncQueriesReady) and Auth is fine.

@cwomack - I've tried cycling a stop and start of `Datastore` every time there is a `Hub` `networkStatus` event. But the sync doesn't get restablished. The websocket connection (eg: wss://abc.appsync-realtime-api.us-east-1.amazonaws.com/graphql?header...)...

To reproduce (artificially): - On Chrome devtools, change the `accessToken` (remove one letter) - On Chrome devtools, set `Network` to `Offline` - Wait a few seconds. Change the `accessToken` back...

Hi @chrisbonifacio - I've jotted down a few things that might help shed some light: - I do see that often a `ready` event does not follow `syncQueriesReady` after a...