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
So, I create a new instance of hoodie (new Hoodie('HOODIE_URL')) when the page is loaded, and I listen to error:unauthenticated events, but apparently this event is only triggered when the session is expired and the user reloads the page.
I put my couchdb session to expire in 15s just to test, and when the user is using the app, after 15s, the data syncing starts to throw 401s, and the user can't logout, but no error:unauthenticated is triggered, only if I reload the page.
Thanks!
The text was updated successfully, but these errors were encountered:
As soon as we have the new account & store modules glued together in hoodie-client, I'd suggest we make an integration tests to assure that hoodie.on("account:error:unauthenticated", handler) gets triggered when hoodie.on("store:error:unauthenticated", handler) gets triggered, to prevent this from happening in future
via @rogeriochaves hoodiehq/hoodie-server#413
Hello,
So, I create a new instance of hoodie (new Hoodie('HOODIE_URL')) when the page is loaded, and I listen to error:unauthenticated events, but apparently this event is only triggered when the session is expired and the user reloads the page.
I put my couchdb session to expire in 15s just to test, and when the user is using the app, after 15s, the data syncing starts to throw 401s, and the user can't logout, but no error:unauthenticated is triggered, only if I reload the page.
Thanks!
The text was updated successfully, but these errors were encountered: