related:  issue 621224 ?

Please take a look!

I have a test account that I haven't used in for sometime. Now when I try to login with that account I am getting the error 206.

Not sure if this is related but at the time of adding the account with username and password I see a message that some terms changed and asking me "Agree or Ask me later". I haven't read that so I tapped on "Ask me later".

After that the account is added in keychain but everytime when I select the account, its showing me the 206 error.

Since this is non-RVG bug, please let me know if you need password for the test account to repro.

Deleted: Screen Shot 2017-07-26 at 1.14.15 PM.png 71.4 KB

	Screen Shot 2017-07-26 at 1.14.15 PM.png 71.4 KB View Download

cc'ing jlebel@ as well!

Raising priority, since this sounds like it's preventing at least some users from signing into Chrome. Mihai - is this an issue with iSL or with Chrome signin?

Re-assigning to Jerome to take a look

I think this looks like https://bugs.chromium.org/p/chromium/issues/detail?id=621224

shikanthg: Yes, we need the account details to be able to test this bug. May I ask you to send them over email to me and jlebel@? It would also be good to share it in the internal bug b/32468091.

email sent + updated internal bug as well.

(Buganizer throwing backend error when updating, so i will post whenever its working again)

Increasing the priority as we should now have a repro case.

I just reproduce it while I was trying to add my chromium account to my own cellphone. Luckily, I had the fix from  Issue 749699 . The error message is:
"Échec de la connexion. Veuillez réssayer plus tard. (ChromeSigninError: -206, com.google.HTTPStatus: 403)"
Translation: Connection failed. Try again later.
403 is: HTTP 403 Forbidden

It looks like a server side error.

I tried right after, and I didn't have the error.

Has someone already reached out to chaowei with the recent repro's to ask for any server side error logs? I can if not.

I didn't do it. I thought chaowei was not on the server side.

Just to make sure, the request that fails, is to get hosted domain for an identity:
https://cs.corp.google.com/chrome-ios_internal/chrome/browser/providers/signin/chrome_identity_service_impl.mm?q=GetHostedDomainForIdentity&dr=C&l=435

That should be that request:
https://www.googleapis.com/plus/v2whitelisted/people/me?fields=coverPhotos(url,isDefault),emails(metadata/primary,value),images(metadata/primary,url),metadata/ownerUserTypes,names(displayName,givenName,familyName,metadata/container),organizations(current,domain),extendedData(hd)&extension=includedomaininfo

Just fyi I've updated b/32468091, not sure if you are cc'ed there jlebel.

The issue was that the quota limit has been reached for the SSO client. It was an issue for all iOS app. The quota has been changed from 1700 QPS to 35 QPS.

I meant 35k QPS. :)