google-signin

问题 I'm facing this issue and am not able to find a solution to it. I have Google Sign In implemented in my app using firebase. The problem I'm facing is that whenever the Sign In dialog dismisses a black strip runs across the screen from top to bottom. It moves very fast but still is noticeable. I want to remove this black strip that runs across the screen so the user smoothly returns to the screen. I tried to add overridePendingTransition(0, 0); in onPause() and onResume() methods but still

问题 I am adding the Google One Tap api to a React application. I am correctly getting the one tap login modal showing up. However, I clicked to close the modal, and now am getting the following response, which I see is based on the cool down period for this api: { "g": "display", "h": false, "j": "suppressed_by_user" } Since I am testing the application, is there a way to override this cool down period? Looks like the following: componentDidMount() { const handleCredentialResponse = response => {

问题 I am adding the Google One Tap api to a React application. I am correctly getting the one tap login modal showing up. However, I clicked to close the modal, and now am getting the following response, which I see is based on the cool down period for this api: { "g": "display", "h": false, "j": "suppressed_by_user" } Since I am testing the application, is there a way to override this cool down period? Looks like the following: componentDidMount() { const handleCredentialResponse = response => {

问题 My app has a Sign in with Google button. When I try to sign in on iOS 13.0 GM GIDSignInDelegate didSignInForUser:WithError: returns this error: Error Domain=com.google.GIDSignIn Code=-1 "The operation couldn’t be completed. (org.openid.appauth.general error -3.)" I have no clue how to fix this issue. I'm using Google Sign In 5.0.0 as part of Firebase 6.8.1. 回答1: I figured it out! The AppAuth-iOS , which is a open-source dependency of GoogleSignIn SDK, has been updated from 1.1.0 to 1.2.0 in

问题 My app has a Sign in with Google button. When I try to sign in on iOS 13.0 GM GIDSignInDelegate didSignInForUser:WithError: returns this error: Error Domain=com.google.GIDSignIn Code=-1 "The operation couldn’t be completed. (org.openid.appauth.general error -3.)" I have no clue how to fix this issue. I'm using Google Sign In 5.0.0 as part of Firebase 6.8.1. 回答1: I figured it out! The AppAuth-iOS , which is a open-source dependency of GoogleSignIn SDK, has been updated from 1.1.0 to 1.2.0 in

问题 I'm using several social providers on my site, including Google. I would like to ask for password to Google account each time user requests one of my actions. This is for security reasons. With Facebook, we can send auth_type=reauthenticate parameter. Is there something like this in Google API? I'm not looking for refreshing tokens, I need to make sure user types his password at any state: whether already authenticated or not. 回答1: I read your posts and I can relate to your frustration on

问题 I'm using several social providers on my site, including Google. I would like to ask for password to Google account each time user requests one of my actions. This is for security reasons. With Facebook, we can send auth_type=reauthenticate parameter. Is there something like this in Google API? I'm not looking for refreshing tokens, I need to make sure user types his password at any state: whether already authenticated or not. 回答1: I read your posts and I can relate to your frustration on

问题 I'm getting the the Developer (Code:10, message:10:) error when trying to sign in using Google Sign-in while using FirebaseUI's Authentication. All works well on development, but when I sign my bundle using my upload key and then run it on a device, it fails. I looked at associated questions here, here and here and the answers didn't help. As you'll see below, I've tried their recommendations. What I've tried: Add SHA1 fingerprints to the Project Settings at the Firebase Console for debug,

问题 I just implemented Google JavaScript sign-in button to our homepage, and everything works the way it suppose to, but thats sometimes bad.. So the thing is that our users use our application on the same computer, 3-4 different users per day. Having a google sign in gives us access to implement some Google product features in our own site. I understand that sign-in with google signs you into the Google account, and also gives permission to application. Also i understand that this is the way it

问题 My Android App already has a SHA1 fingerprint on Google developers console generated by another developer some time back. Now, I am debugging Google Sign-in bug in the App and it turns out that Google Sign in uses the default SHA-1 found in .android/debug.keystore to make a request in the OAuth authentication process. And I had generated a new debug key yesterday because after all it is debug. How do I add or incorporate this new debug key to Google's developer console to make a successful