Vinzent

`gotrue 1.6.0` got just a few minutes ago released. Do you really still experience this issue? What version of `gotrue` where the production app using? What jwt expiry time have...

There was a fix in [1.5.6](https://github.com/supabase/gotrue-dart/blob/main/CHANGELOG.md#156) about jwt expiry margins. This may be the cause.

It might be important to update to 1.5.7 though, depending on how important the session emitted by the inAuthStateChange stream is.

You should get logged out when this error comes up. You get this error for example when you sign out on another device.

We currently only sign out on the specific error message `Invalid Refresh Token: Refresh Token Not Found`. I don't know what the reason for a 401 response is. We emit...

That seems to be the response of a call to postgrest which failed, because the call to refresh the jwt didn't work. > could it be that the JWT was...

It's technically not possible to invalidate a jwt. It's only invalid after its expiry time. Your error shows again that the refreshing of the jwt somehow didn't work. What is...

Hmm 1 week is definitely long enough. We currently try to refresh the jwt 60 seconds before expiry. I'm wondering why that sometimes doesn't work in your case.

> Invalid Refresh Token: Refresh Token Not Found I encountered this, if I sign out on another device or session, because Supabase invalidates all refresh tokens on sign out call.

I reported that [here](https://github.com/supabase/gotrue/issues/248) long ago. From what I see, invalidating all refresh tokens in the only effect of calling the `logout` endpoint. I don't like that behavior, so @dshukertjr...