You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes (I still don't get what exactly causes this behavior), after many successful requests, the token my front-end has seems to have expired, given that the devise-token-auth api is responding with a 401 error, but the expiry is far from reaching 0. The strangest part is that if I just refresh my page (which fires a "validate token" request to the backend), my frontend sends the exact same token that was being rejected and the backend is responding with 200. All the following requests from this point are working correctly, until this whole thing start happening again.
Any idea about what could cause that and how to solve it?
Using devise_token_auth 0.1.43
I developed the frontend integration by myself...
The text was updated successfully, but these errors were encountered:
Sometimes (I still don't get what exactly causes this behavior), after many successful requests, the token my front-end has seems to have expired, given that the devise-token-auth api is responding with a 401 error, but the expiry is far from reaching 0. The strangest part is that if I just refresh my page (which fires a "validate token" request to the backend), my frontend sends the exact same token that was being rejected and the backend is responding with 200. All the following requests from this point are working correctly, until this whole thing start happening again.
Any idea about what could cause that and how to solve it?
Using devise_token_auth 0.1.43
I developed the frontend integration by myself...
The text was updated successfully, but these errors were encountered: