Cannot login to Google Account with Google Prompt 2FA

[mouse-man]

• Did you search for similar issues before submitting this one?
  Yes

• Describe the issue you encountered:
  When signing in to Google Account, I have 2FA set with Google Prompt being the primary. When logging in, the prompt goes to phone, but before I can approve, says 2FA failed. Have to use another 2FA method to login.

• Platform (Win7, 8, 10? macOS? Linux distro?):
  Win8.1, Win10

• Brave Version (revision SHA):
  Brave: 0.13.5
  rev: 1db81cb
  Muon: 2.56.8
  libchromiumcontent: 56.0.2924.87
  V8: 5.6.326.50
  Node.js: 7.4.0
  Update Channel: dev
  os.platform: win32
  os.release: 6.3.9600
  os.arch: x64

• Steps to reproduce:

  1. Login to Google Account
  2. Get prompt
  3. Get Denied message

• Actual result:
  Denied access

• Expected result:
  Granted Access

• Will the steps above reproduce in a fresh profile? If not what other info can be added?
  Yes

• Is this an issue in the currently released version?
  Yes

• Can this issue be consistently reproduced?
  Yes, has happened on 2 machines.

• Extra QA steps:
  1.
  2.
  3.

• Screenshot if needed:
  Will record next time I try this.

• Any related issues:

[philkloose]

I've got the same issue -- Brave browser shows immediate 2FA failure although my phone receives (Yes|No) prompt successfully. I have to fall back to Google Authenticator. Other details identical except for OS which is Win 7 (x64).

[srirambv]

+1 from community https://community.brave.com/t/gmail-2fa-authentication-not-working-when-shield-is-up/3532

[LaurenWags]

+1 from community (see # 16 in this post: https://community.brave.com/t/issue-small-bugs-found-in-first-couple-hours-of-using-brave/5075)

[luixxiul]

+1 #10579

[deive]

Also getting this with Chrome Version 60.0.3112.113 and Android.
Chrome instantly shows “Your sign-in attempt timed out. Resend the prompt to try again.” and does not react when I tap yes on the phone

[volcani]

I also getting in with resembling problem.
"One tap auth" doesn't work.
When I get prompt from google to my phone, brave shows me "time out" dialogue without second.

My enviroment is

Wiindows10 32bit
brave 0.19.53 reve09025b

Strangely, google chrome on same device works normaly.
Only brave deny my access.

[winteraz]

I'm developing a http proxy and for some reasons I have the same error with "One tap auth" regardless of the browser. Any idea what might cause that?

[srirambv]

+1 from https://community.brave.com/t/google-prompt-sign-in-immediately-timed-out-on-youtube/11607

[srirambv]

+1 from #12196

[thereseng]

Same problem here. Need to use Google Authenticator

[bbw22]

This is definitely still a problem in normal tabs and private tabs. End up having to use sms to authenticate.

Brave: 0.21.18
V8: 6.4.388.41
rev: 580be78
Muon: 4.8.2
OS Release: 17.4.0
Update Channel: Release
OS Architecture: x64
OS Platform: macOS
Node.js: 7.9.0
Brave Sync: v1.4.2
libchromiumcontent: 64.0.3282.140

[freimer]

I have a slightly different issue, but related. 2FA does not work in Brave even with shields down when using a Yubikey:

Brave: 0.21.24
V8: 6.5.254.36
rev: 19c78a1
Muon: 4.9.3
OS Release: 16.7.0
Update Channel: Release
OS Architecture: x64
OS Platform: macOS
Node.js: 7.9.0
Brave Sync: v1.4.2
libchromiumcontent: 65.0.3325.162

This is for github, gitlab, and basically any 2FA site I tried. It works perfectly fine in Chrome.
Version 65.0.3325.181 (Official Build) (64-bit)

[csleary]

@freimer Yeah, Brave doesn't seem to support Fido U2F, as the Yubikey won't flash to prompt. 🙁

[freimer]

Actually, this works with brave-beta...

[bsclifton]

This may have been fixed with #11401 in 0.22.x (if you imported from Chrome)

For folks experiencing this: can you please try our 0.22.x release?
https://github.com/brave/browser-laptop/releases/tag/v0.22.9dev

[csleary]

@bsclifton Does indeed sort it. Thanks Brian!

[bsclifton]

@csleary awesome! I'll close this issue for now- let's re-open if 0.22.x does not work for you (as @freimer mentioned, beta is on the 0.22.x version, which is why it worked)

[DanEhrlich]

Still hapenning

Brave: 0.22.22
V8: 6.5.254.41
rev: 6303310
Muon: 5.1.2
OS Release: 17.5.0
Update Channel: Release
OS Architecture: x64
OS Platform: macOS
Node.js: 7.9.0
Brave Sync: v1.4.2
libchromiumcontent: 65.0.3325.181

[qmlowery]

I'm getting this issue as well.

Brave | 0.22.22
V8 | 6.5.254.41
rev | 6303310
Muon | 5.1.2
OS Release | 10.0.16299
Update Channel | Release
OS Architecture | x64
OS Platform | Microsoft Windows
Node.js | 7.9.0
Brave Sync | v1.4.2
libchromiumcontent | 65.0.3325.181

[eljuno]

+1 from community https://community.brave.com/t/brave-cant-login-with-google-tap-your-smartphone-feature/26460?u=eljuno

[ghost]

Why is this closed? This is still an issue

Brave	0.23.31
V8	6.7.288.46
rev	3148ace
Muon	7.1.5
OS Release	17.5.0
Update Channel	Release
OS Architecture	x64
OS Platform	macOS
Node.js	7.9.0
Brave Sync	v1.4.2
libchromiumcontent	67.0.3396.103

[jacobc-eth]

Still happening for me as well.

[zeroxxx2]

How's this closed? The crap's still going on. If you can't fix it don't close it. Incompetent.

[bsclifton]

@zeroxxx2 it's not closed actually. It was thought that a patch earlier this year fixed it (which it didn't) and the issue was re-opened (back in May)

[bsclifton]

...and then closed/re-opened again right now, because I clicked the wrong button 😛

[scgruber]

I just came here after encountering this issue. I was able to work around by setting Cookie Control to Allow all cookies for accounts.google.com, after which my two-factor push immediately started working.

Brave: 0.23.79
V8: 6.8.275.24
rev: 51b4905
Muon: 8.0.7
OS Release: 4.4.0-130-generic
Update Channel: Release
OS Architecture: x64
OS Platform: Linux
Node.js: 7.9.0
Brave Sync: v1.4.2
libchromiumcontent: 68.0.3440.84

[studro]

Writing to confirm @scgruber's workaround:

Cookie Control(Clear all)
https?://accounts.google.com:
Allow all cookies

My version details are as follows.

Brave | 0.23.105
V8 | 6.8.275.24
rev | 9a46f8f
Muon | 8.0.9
OS Release | 10.0.17134
Update Channel | Release
OS Architecture | x64
OS Platform | Microsoft Windows
Node.js | 7.9.0
Brave Sync | v1.4.2
libchromiumcontent | 68.0.3440.84

[erasmus]

Still there in v0.24.0

[Northshoot]

Same critical issues as it preventing usinge most common webapps, any progress?

Brave: 0.24.0 
V8: 6.9.427.23 
rev: f657f15bf7e0e0c50a2b854c6b05edb59bfc556c 
Muon: 8.1.6 
OS Release: 18.0.0 
Update Channel: Release 
OS Architecture: x64 
OS Platform: macOS 
Node.js: 7.9.0 
Brave Sync: v1.4.2 
libchromiumcontent: 69.0.3497.100

[bsclifton]

For folks experiencing this problem: can you please try out new Beta release?
https://brave.com/download-beta

You should be able to import everything from your existing Brave install (except Brave Payments- for that, you'd want to export your wallet). The problem should be fixed there

Unfortunately, I don't think we'll be able to address this issue with this code-base. My recommendation would be to try the Beta and if the problem persists, let me know and I can help create an issue in our new repository:
https://github.com/brave/brave-browser

[bsclifton]

Looks like this is possibly still an issue in our new code-base; issue is being tracked with brave/brave-browser#1356

[TheGorf]

Can confirm. Experiencing this issue as of this morning.

Brave: 0.25.2
V8: 6.9.427.23
rev: 8ea2a9c
Muon: 8.1.8
OS Release: 17.7.0
Update Channel: Release
OS Architecture: x64
OS Platform: macOS
Node.js: 7.9.0
Brave Sync: v1.4.2
libchromiumcontent: 69.0.3497.100

[s10mcow]

@bsclifton Beta works as it should...