19

I tried logging in with a Google account, but I got the following error:

screenshot of detailed code: 400 error

13
  • From the error message, I think this is a bug.
    – Zackary
    Commented Nov 3, 2018 at 22:23
  • 1
    I have the same problem. Running iOS. Hasn't worked for 2 days. Commented Nov 4, 2018 at 8:57
  • See also meta.stackoverflow.com/q/376216/1338846 (iOS) Commented Nov 5, 2018 at 22:29
  • I've been experiencing this bug for more than 2 weeks and they have no solution so far. Commented Nov 22, 2018 at 21:00
  • Why? Why I did logout from app? Will never logout from iOS app at least. Commented Nov 23, 2018 at 8:26
  • @EzequielBarbosa there is nobody that can fix it. The only android developer SE ever hired (Kasra) no longer works for Stack Exchange. Commented Nov 24, 2018 at 10:11
  • @SonictheInclusiveHedgehog because it actually made the image too small for mobile users
    – ArtOfCode
    Commented Nov 24, 2018 at 23:18
  • @ShadowWizard I forgot I had an OpenID associated to this account, but still it's strange we this bug popped up without the app being updated. Even more strange is the fact SE is lacking programmers lol. Commented Nov 25, 2018 at 1:49
  • @EzequielBarbosa nothing strange... SE made a business decision to ditch the apps in favor of working on other things. I'm only surprised they let the apps slowly decay and fall apart rather than just shutting them down. This cause hundreds of people who still use the apps to get frustrated. Commented Nov 25, 2018 at 7:31
  • In theory they still do bug fixes. In practice I don't know. And until SE gets web notifications, this is still the only way to get notifications on mobile Commented Nov 26, 2018 at 3:16
  • Same problem here. I got new android phone and now I can't login on the app anymore. Commented Nov 29, 2018 at 5:10
  • @animuson Would you mind posting an answer explaining what the issue was? Commented Nov 30, 2018 at 2:00
  • @Sonic it's no less than a miracle they fixed it; Expecting details is really way too much. :) Commented Dec 1, 2018 at 23:29

1 Answer 1

3

This has been fixed as of 1 Dec 2018, re download the app if still experiencing problems based on my experience.

EDIT: Earliest fix was apparently 29 Nov 2018

1
  • 1
    According to SE staff it was fixed before December 1. (Nov 29) Commented Dec 1, 2018 at 23:40

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .