Open sowiszcze opened 4 years ago
I have a similar issue.
Clean install of IITC-CE from the Play Store. When trying to sign in with a Google Account I can enter my email address / password. I then get a prompt from Google "is this you trying to sign in" after clicking yes Google Chrome opens the website myaccount.google.com.
When returning to IITC-CE mobile i'm not signed in and get stuck in the loop described above.
App version: 0.29.1 OS version: Android 9 / LineageOS 16 Device: OnePlus 5T
I suspect this is related to having 2 factor authentication enabled on my Google account.
Please check latest test build
@johnd0e can you provide a link?
@modos189 I can sign in with 2FA enabled on that build.
Still getting the same problem with Advanced Protection turned on. Nothing changed.
@sowiszcze Could you attach some screenshots?
And describe what is different when you
@sowiszcze
Workarounds
- Turning off Advanced Protection (big no-no)
Add one more workaround: use Google 2-Step Verification instead.
If there was some way to manually open standalone browser to login using Google account, for example turned on in settings or by additional button, that would probably solve the issue.
We are going to implement this in #290 (need more work there).
P.S. some notes about Advanced Protection Program (for future ref.):
App version: 0.29.1 OS version: Android 9/Oxygen OS 9.0.9 Device: OnePlus 5
I'm using fresh install of IITC Mobile. When I try to log in using my Google account with Advanced Protection turned on, I'm going through typical steps - putting in username, then password.
Expected result: Being prompted to connect and click my key. Actual result: I'm greeted with Sing-in stopped view informing me, that Google couldn't verify that this account belongs to me because of Advanced Protection being turn on.
Workarounds
Possible cause and solution This issue was present in previous IITC Mobile (no longer maintained) while Google login was moved from standalone browser-based to embedded browser one. Probably it's caused by some of Google restrictions on where authorization tokens can be used. If there was some way to manually open standalone browser to login using Google account, for example turned on in settings or by additional button, that would probably solve the issue.