|
2012-11-15
, 14:11
|
|
Posts: 1,034 |
Thanked: 784 times |
Joined on Dec 2007
@ Annapolis, MD
|
#92
|
|
2012-12-03
, 18:00
|
Posts: 5 |
Thanked: 4 times |
Joined on Nov 2012
@ Accra-Ghana
|
#93
|
|
2013-07-08
, 15:30
|
Posts: 260 |
Thanked: 86 times |
Joined on Jan 2012
|
#94
|
|
2013-07-17
, 19:42
|
Posts: 260 |
Thanked: 86 times |
Joined on Jan 2012
|
#95
|
|
2014-09-15
, 11:34
|
|
Posts: 217 |
Thanked: 89 times |
Joined on Dec 2013
@ Indonesia, Banyuwangi
|
#96
|
I ran the social-status-updater-config command, which reports that I'm already logged in with no error.
So I re-ran the social-status-updater-config command and used it to log out and then back in. Still I got a token authentication failure when using the status updater.
New auth bug?