My Google services were working fine through the October outage until I accidentally logged out of one of my Google accounts. I’m now unable to log back into it in the Account settings. I can open the settings for the microG connection, but clicking any of the menu options there (Sign-in & security, Personal info & privacy, Account preferences) just boots me back to the previous screen. If I try to add the account as Google (rather than microG), after I select my Google account, I get “This app is blocked. This app tried to access sensitive info in your Google Account. To keep your account safe, google blocked this access.”
2 Likes
It would appear that Google has tightened the screws on authorised access to applications not known to Google.
For a few days now, I’ve been unable to access my Gmail business emails on the /e/OS email client. To get round this problem, I’ve been forced to download the official Gmail app.
Fortunately, syncing with the /e/ calendar still works without a hitch.
Maybe it’s possible to go into Google’s security settings and create a specific password for a ‘less secure application’, which will be dedicated to the Google account on /e/OS?
2 Likes
I finally managed to correct the problem as followed:
-
Through Internet, went to my Google account => Security tab => 2-step validation => App password, then generate a specific password for a third-party application. (Make a note of the password as there is no way of displaying it afterwards).
-
Then go to the smartphone’s email application => Inbox => select the Google account, go to Settings => Incoming server, and change the authentication method to ‘Normal password’, and then insert the newly created password.
My Gmail emails now do work again fine on /e/OS default mail app.
Note that I did NOT delete my Google nor MicroG accounts from Seetings => Account Manager…
The wording above was translated by myself from a French layout base, so the words in the English display may not be identical…
1 Like
reads like oauth2 within Mail posed the problem? what is your /e/ or /e/mail version? can’t see a current entry on this at Issues · e / Backlog · GitLab
No idea, but it works when generating a third party app password. In my case oauth2 is active in my Google account security settings.
Not sure if it needs to raise an issue as it’s a Google “politic” decision that impacts most third party mail clients.
1 Like
see the “this app is blocked” issues at k9mail or their forum. Tracked at /e/-gitlab Google account doesn't sync anymore (#8374) · Issues · e / Backlog · GitLab - the PR changes the client-id, so I guess it’s about either api scopes requested or even manual review.
Thanks, everybody, for your help!
1 Like
This topic was automatically closed after 90 days. New replies are no longer allowed.