[Imap-protocol] Gmail - OAUTH2 - failures since Feb 23

Hi,

My apologies to everyone for a message about Gmail that has nothing to
do with IMAP specifically.

Hoping someone from Google (perhaps Brandon Long who I've seen lurk
here?) can respond and we can take the discussion off the list.

---

Since Feb 23, we're seeing login / auth failures affecting a good
number of users.

We support OAUTH2 and get the token through Google Play Services.

I saw the issue on one of my phones and was able to debug it:

- Most of the time, our code would get a valid looking token from
Google Play Services

- A web API request using this token to get the user's name, email and
profile photo would work fine

- And yet, using this token to log into Gmail would get "status code
400, bad request" from Gmail's IMAP and SMTP servers.

At other times, there'd be a failure inside GoogleAuthUtil.getToken
with GoogleAuthException: Unknown

So this looks to me like some back-end failure on Google's side,
specific to Gmail (by comparison, the user profile API is just fine).

We found a workaround:

Removing our app from "authorized apps" in "your Google account", and
the user re-authorizing the app seems to work.

But until this is done, authentication keeps failing, even if our code
refreshes the token again.

Is this a known issue?

Are there changes we need to make or is this a bug (looks like a bug to me)?

If this is confirmed as a bug on Google's side, when can we and our
users expect a fix?

Thanks, and my apologies again to the IMAP list!

PS - the app is called Aqua Mail, not sure if the issue is affecting
only our app.

-- K
_______________________________________________
Imap-protocol mailing list
[email protected]
http://mailman13.u.washington.edu/mailman/listinfo/imap-protocol