Devise trackable module not working

[smarquez1]

Columns:
sign_in_count, current_sign_in_at, last_sign_in_at, current_sign_in_ip, last_sign_in_ip

are not being updating after user logs in.

[booleanbetrayal]

FWIW - initial glance seems that this is working on my end:

back_royal_development=# select sign_in_count, last_sign_in_at from users where id=1;
 sign_in_count |      last_sign_in_at       
---------------+----------------------------
           118 | 2014-11-07 17:09:47.986049
(1 row)

and with subsequent login ...

back_royal_development=# select sign_in_count, last_sign_in_at from users where id=1;
 sign_in_count |      last_sign_in_at       
---------------+----------------------------
           119 | 2014-11-07 17:11:24.351536
(1 row)

[smarquez1]

Thanks @booleanbetrayal , must be an issue with my configuration. Are you using the latest devise/ng-token auth betas?

[markusklooth]

This also doesn't work for me. I'm using 0.1.29.beta7.

[lynndylanhurley]

Hey guys, I think I just fixed this recently. Can you all try version 0.1.30.beta3 to confirm?

If this solves the problem then I'll push an official release.

[smarquez1]

@lynndylanhurley - I'm already using devise_token_auth, '0.1.30.beta3' and "ng-token-auth": "~0.0.24-beta6"

[markusklooth]

Just upgraded to devise_token_auth 0.1.30.beta3 and it doesn't work. the following attributes are still empty:
remember_created_at: nil, sign_in_count: 0, current_sign_in_at: nil, last_sign_in_at: nil, current_sign_in_ip: nil, last_sign_in_ip: nil

[booleanbetrayal]

sorry @smarquez1 - I'm on devise_token_auth 0.1.30.beta3 and ng-token-auth 0.0.24-beta1. I had migrated our Rails project from a vanilla Devise, cookie-based authentication scheme .. but I can't imagine that'd make any difference.

[mvoloz]

same for me using devise_token_auth 0.1.30.beta3 with ng-token-auth 0.0.24-beta6

[lynndylanhurley]

Ok thanks guys! Looks like I didn't have good enough coverage on this. I'll try to push a fix out later today.

[lynndylanhurley]

It looks like trackable was set for email sign-in, but not OAuth sign-in. Version 0.1.30.beta5 should contain the fix.