Comment 20 for bug 1983245

Revision history for this message
In , Nate-b (nate-b) wrote :

So it looks like there are two options here:
1. It was an unintentional regression in accountsservice that needs to be fixed
2. It was an intentional change in accountsservice (perhaps we were using the API wrong, or using deprecated API) and we need to adapt to it

Someone with accountsservice experience will need to investigate or bisect it.