I've noticed this with firebase auth, if you're logged in and don't refresh the page (but can use RW router navigation).
Once the token expires, its not refreshed automatically, as a result graphql calls start to fail.
I suspect this is an issue with other auth providers as well, and we might need to slightly modify the structure of AuthClient to support refresh events.
I've noticed this with firebase auth, if you're logged in and don't refresh the page (but can use RW router navigation).
Once the token expires, its not refreshed automatically, as a result graphql calls start to fail.
I suspect this is an issue with other auth providers as well, and we might need to slightly modify the structure of AuthClient to support refresh events.