I have a strange case where a request to the signout API returns a 401 in production. What’s the rea...
a
I have a strange case where a request to the signout API returns a 401 in production. What’s the reason for that? How can I solve it? The issue is that users are basically never able to sign off
r
hey @Ale, Pocket this means that the access token has expired. It should trigger an auto refresh
a
I notice that a request to our service graphql api returns 401 because the session can’t be verified. But the consequent request to refresh the session triggered by the st sdk returns 200
r
Hmm. I would need to know what the debug logs say
Could you enable this in prod and show the output during one such verification failure