Socket.io timeout does nothing when there is JWT token available

[marshallswain]

@Creiger commented on Mon Dec 19 2016

Steps to reproduce

When the feathers server is not running and there is already a JWT token stored in client cookies, this function

app.authenticate().then(showApplication, showLogin);

never fires anything. It does not throw any error also. When i delete JWT token, showLogin function is fired.

Expected behavior

I think this should throw an error after socket.io timeout set in app configuration.

Actual behavior

Does nothing.

---

@marshallswain commented on Tue Jan 03 2017

Thanks @Creiger I'm moving this to the feathers-authentication-client repo.

[marshallswain]

This will also need fixing in the old feathers-authentication/client plugin.