I am PM from Kwai team, and got a problem regarding with Google sign-in. While signing-in or logging Kwai app via Google, there is an obvious mantle before choosing and confirming Google account, please check the third pictures attached.
According to the mantle, no behaviors can be performed while mantle showing, which is wired on the sides of users' experience.
Could you please check in what situation would the mantle show? Will it be possible to drop it through signing-in or logging in?
Many thanks,
Leo
Related
I have an Android app that uses Google SignIn as a sign-in method.
In the Google Play Console, I'm supposed to provide a test account for Google to conduct app reviews. However, I'm facing an issue with that.
Even though I provide a Google account to test, as you can see in the below screenshot, there's an Identification Verification step that blocks Google reviewers to proceed with their job.
From my understanding, this step appears when Google suspects a sign-in. Although this test account is created/used in Japan, Google reviewers use it in other countries e.g. India (most of the time), the US, etc, that would be why this sign-in is considered as suspicious.
Then here's a question. What can I do about this situation? Just for your references, I already tried the following but nothing helped.
Disable 2FA (i.e. No additional authentication is configured)
Sign out from the test account in all of my devices (IIRC, with this approach, previously Google reviewers succeeded in sign-in without the Identification Verification step, but seems not this time)
Google reviewers or even their support team will never help me with this so it'd really be appreciated it if you know the workaround. Thanks.
I have created a project at Google Developer Console. And I have followed the steps to create an OAuth Consent screen to ask users for their consent to let me use their email address and Google Calendar for my App. App is still at Test Mode, and everything is working fine.
But for the users of Google Workspace (G Suite) (#domain.com) the consent screen is not working. It just ends up saying that Something went wrong and ... the request is malformed.... I am sure it isn't malformed, because it is just working fine for non-workspace (#gmail.com) users.
I got it working later by Manage Domain Wide Delegation by logging into the Google Workspace Admin account and manually setting up my Apps's service account Client ID and Scopes. The process allowed users of that #domain.com (non-admin) email to get my consent screen working.
But this is not practical. I can't ask every #domain.com email address user to contact their Google Workspace Admins and add my app to the domain wide delegation area manually.
There are apps and services out there which connected to my non-admin Google Workspace account without having my Admin do it for me.
So there must be some way to get my consent screen work on #domain.com email addresses hosted at Google Workspace without involving the Admin account or Domain wide delegation stuff.
How can I get it done? Please help, I can't find any solution online.
EDIT More banging head in the wall, but no similar issues found on the internet. So what I feel like is that I need to wait for my OAuth application to be approved for production for it to work for Google Workspace accounts. PLEASE HELP if you know there is some other issue and I can try to fix...
Thanks.
Looks like there was some temporary issue with Google. I emailed them, and the issue was fixed.
I have an app available for download which uses Google Sign In. Most people do not have any problem signing in using Google Sign in so I know it is set up correctly with the right keys. However very occasionally we see the following error.
SIGN_IN_FAILED 12500
The docs say
The sign in attempt didn't succeed with the current account.
Unlike SIGN_IN_REQUIRED. when seeing this error code, there is nothing user can do to recover from the sign in failure. Switching to another account may or may not help. Check adb log to see details if any.
I suspect something has been disabled by a GSuite admin but I cannot see anything you can do to disable Google Sign In. In GSuite help I read under “View and revoke third-party applications connected to the user's Google Account”:
You can revoke service access only after it's been granted. You can't preemptively block users from granting access to specific apps.
Can anyone suggest what could cause this - for example how I could reproduce this issue by setting something in my own GSuite account?
I created an App with the GSuite administrator account. But now when I go back I am my work user(rob) and have no access to the App I created.
If I then go to Google and switch accounts there is no issue for all other Google apps(drive, gmail etc) but Appmaker still shows me as rob.
How can I convince App Maker to work like all other Google apps and let me select the logged in user?
Most likely it happens because at this time App Maker doesn't provide users with account chooser widget like most other Google products. Here are some things to try to bypass this limitation:
use different chrome instances for better accounts separation (https://support.google.com/chrome/answer/2364824) - I would highly recommend this approach. I have about 10 different accounts and this feature saves me tons of time and gives peace of mind
use incognito window
log out from other accounts (in theory, when you open AM it will ask you to choose an account and re-login)
I am adding members in my Firebase project through console with the role of "Project Editor" which have all view permissions acc to docs. But by login as a member I am not able to see the Analytics. I tried changing role to "Project Owner" but still Analytics are not visible.
I am working with Firebase for the first time and new with the roles concept. Please help if anyone have solution to this.
Thanks in advance.
What do you mean by the term "not visible", are you seeing a plain blank screen or the dashboards are there but no data yet?
I'd suggest you to try the following workarounds:
If you have multiple Google accounts logged in at the same time, please logged them out and use only the account for Firebase. Also, use Google Chrome incognito mode.
Turn off Ad blockers or check if the Analytics domain is disabled by your Network administrator.
Open the Google Chrome developer mode, then check if there's any error logs or stack trace on the console. Reach out to the Firebase Support team by creating a ticket here.
Hope this helps.
Got the solution
I tried other gmail id that is with "gmail.com" domain rather than my "company_name.com" domain and the analytics is now visible that is previously only blank white screen.
It is because in company domain there are some restriction on user access.