On Fri, Nov 23, 2012 at 5:59 PM, Christopher Masser wrote:
> SOLVED:
> accountManager.invalidateAuthToken(account.type, null); doesn't seem to be
> enough.
> One has to provide the name of the old token instead of null.
> Although the documentation says that the token can be null and it will
> inv
sorry, corrected here:
*try*{
calendarList = CalendarService.calendarList().list().execute();
}*catch* (Exception e) {
e.printStackTrace();
accountManager.invalidateAuthToken(account.type, myToken);
//start all over
}
On Thursday, November 22, 2012 10:30:41 AM UTC+1,
SOLVED:
accountManager.invalidateAuthToken(account.type, null); doesn't seem to be
enough.
One has to provide the name of the old token instead of null.
Although the documentation says that the token can be null and it will
invalidate it for the whole account type.
Here is what works:
*try*{
UPDATE:
I asked some of my users with this problem to create a new Google account
on the same device and the new account seemed to work.
The problems seemed to start when they deleted some calendars on
gmail.com/calendar.
On Thursday, November 22, 2012 10:30:41 AM UTC+1, Christopher Masser wrote
4 matches
Mail list logo
