Comment 18 for bug 1389028

I'm setting this back to Fix Released. As stated by the original reporter in comment #15, this was due to a corrupted account on the server, which had two different tokens somehow registered for the device. This would cause the account to be created successfully when logging in via Online Accounts, but when the account would be used by the scope, it would see from the server that the credentials were invalid (because the server was expecting a different token), and the scope would delete the local account and require the user to log in again (because it appeared to have invalid credentials on the device). By deleting both tokens on the server, via the web site, and then logging in again, the issue was resolved for Mathijs.