Google 0auth/2FA push broken in last update?

Graph_Curious

I have a google account with 2fa, which only allows authorization from my 'trusted device'

Last week, this worked fine. My phone wouldn't 'bing' that it got a message, but when I unlocked it, I'd have the 0auth screen asking if I wanted to allow the google login for that account ...and the 2fa worked fine that way

Yesterday (after the most recent GrapheneOS update) when I try, the phone never receives the 0auth request. Tried hitting 'resend' etc ... Never shows the screen on the phone to allow the goggle auth. I had full network, bars, etc...

Did anything change or roll back? I haven't installed or changed anything other than the GraphOS update and reboot

proclaim

Graph_Curious
Hi,
since a few days for me it is also impossible to login on Google using the 2fa method.
I don't get the usual dialog to identify me with my Yubikeys . I have tried everything, but nothing helps.

I post here for my issue .
https://discuss.grapheneos.org/d/4880-unable-to-start-google-session-google-play

I think my problem is similar to yours.

muhomorr

Graph_Curious Does Play services app have the "Notifications" permission?

Graph_Curious

muhomorr no permissions had been changed from when it was working before the update, to it not working after the update ...

But I checked, and no : google play services had notifications turned off... I've enabled it and we'll see how it works
There's a lot of notificationsI don't need here . . .

csis01

I'd suggest that you set the google account to use "google authenticator" for 2fa. When it presents the qr code, you can scan it with ANY TOTP application, like AndOTP, and from then on use that for authentication.