I need help doing the verification process for one of my applications, but I do not know what the problem is, for several days I have been trying to send the application and this is the link to the application's home page
https://khotwhteech.manbij.net/Homepageapps
My application does not contain any linked site and Google's response is as follows. Hi,
Thank you for your response.
To proceed with the verification process for your project khotwhteech, you will need to provide a homepage that accurately represents your app's identity to Google users.
To update the homepage URL linked to your OAuth Consent Screen, you may do so by taking the following steps:
Sign-in to Google Cloud Console
Select the project ID:khotwhteech
Go to Credentials on OAuth consent screen
Enter the homepage URL
Click Submit
Please reply to this email once you have made the appropriate updates to your site and/or your OAuth Consent Screen so that we may continue with the verification process.
Thank you for your patience. If you have any questions, please reply directly to this email. I don't know what's wrong, is there any advice or way to solve?
Related
My application needs to interact with the Google API's using some specific scopes, so I need to submit it for verification. When doing so, I use the Prepare for verification button in the screenshot below.
After completing the form, the toast message “Your app has been submitted for verification” appears and I am redirected to the same screen. However, the status "Needs verification" remains and no change is visible to indicate that my app is in the process of being verified. I am able to repeat the process without any visible change.
I submitted the application for the first time 2 weeks ago, but still no change. Is this a bug in Google's platform? How should we proceed (without having to buy a 100$/month support subscription)?
Thanks a lot
You can check your app verification status via email;
Your project's last submitted OAuth consent screen is under review. Additional information about your app, if required, may be requested via email at the email addresses you provided in the Developer contact information section of the Prepare for verification process. Expect the first email within 3-5 days.
You can find more information about this process in the Oauth Verification documentation.
If so happens that your app is a "restricted scope app" verification may take a few weeks instead of a 3-5 days.
You should have get an email with the confirmation that your app is being verified. If not try again and check your spam folder. If you aren't getting any emails then go to IssueTracker and report a bug.
We are working on a Django app, in which we are using Gmail API's services (Restricted SCOPE).
As our app is still under construction so we didn't submit it for verification on the google cloud form. The app that we are trying to authenticate is used for internal development and we did not publish it to our users.
So we are facing "This app is not verified" screen and fortunately, we can log in after skipping this screen by clicking on the Advance option. We tried it with our personal and test accounts it works well.
But whenever our client trying to authenticate Gmail with the app he is facing this issue. "Sign in with Google temporarily disabled for this app".
We checked we did not reach the limit of 100 users accessing the application.
Is this because of the location issue? or our client is using some kind of Anti Virus or any other extra security checkup? What issue it can be? can someone please help?
"Sign in with Google temporarily disabled for this app".
Once you have reached this point you have used up your quota of users who can sign into your application. As you mention the limit is 100 users who have authenticated your application.
What counts as a user has been debated for a long time.
If a developer authenticates your app then revokes their access then authenticates again this in my experience is probably counted as two against your quota.
So its not really number of unique users, but number of users who have seen an consented to the consent screen.
As you have now reached this limit your only option is to
wait for verification
create a new project on developer console and start the verification process again but with a new 100 users
You should setup for Oauth consent screen.
You can setup Oauth consent screen for oauth authenticate through "navigation -> APIs&Services -> Oauth consent screen".
Then you need to fill in required informations below.
Your app logo (if applicable)
Your app name, which will be a dynamic link to give users your app's support email address
The data you are requesting, or scopes, which you will add in the next step
Links to your app's privacy policy and terms of service
After you fill in domain,links..etc properly, You can use oauth authentication on your app.
I tried to set up social login for my website but I accidently uploaded a logo to the OAuth consent screen, which has locked my app in a verification Status: Needs verification. I get the following message:
"Because you updated the application logo, your app registration requires verification by Google. Please prepare your app to submit for verification".
I am unable to delete this application and set up a new one (without a logo) or remove the logo from the existing one. It's totally locked me up? I also get a message that it will only allow 100 logins before it stops. How can I get rid of this thing, I've got a banging headache, and spent 8 hours going around in circles... Should I just remove the google login from my website? Is that my only option now?
Please help me!
For anyone facing this issue in 2021:
If you place a logo on Oauth consent screen by mistake, submit your app for verification. This will allow you to use the consent screen as before.
When you are contacted by a representative, inform them you want to use the app withouth the logo.
You can also follow this thread or add your +1 in issue tracker.
Our desktop application integrates with Facebook using the desktop app workflow and for approx. 18 months has been working without any problems. However, we are starting to get reports from some users that they cannot get past the login process.
When the login is successful Facebook should be attaching the access_token to the redirect_uri. Our application detects this and moves the user to the main part of our Facebook integration. What appears to be happening in some situations is that the access_token parameter is missing which causes our application to leave our embedded browser window open with the following message from Facebook:
"Success
SECURITY WARNING: Please treat the URL above as you would your password and do not share it with anyone."
What is strange is that this does not occur with all Facebook accounts and which Facebook accounts it occurs with seems to be changing. For example, we had a report of this approx. 1 week ago but could not duplicate it with my own Facebook account or with a colleague's Facebook account. Today, I still cannot duplicate it with my own Facebook account but my colleague now gets the problem.
The URL our code sends to Facebook is:
https://graph.facebook.com/oauth/authorize?client_id=xxxx&redirect_uri=http://www.facebook.com/connect/login_success.html&type=user_agent&display=popup&scope=read_friendlists,user_photos,friends_photos,user_photo_video_tags,friends_photo_video_tags,user_events,friends_events,user_groups,friends_groups
Reading the latest API documentation it looks like they recommend a different way to connect which we have also tried:
https://www.facebook.com/dialog/oauth?client_id=xxxx&redirect_uri=http://www.facebook.com/connect/login_success.html&scope=read_friendlists,user_photos,friends_photos,user_photo_video_tags,friends_photo_video_tags,user_events,friends_events,user_groups,friends_groups&response_type=token
To rule out our application as the cause we have tried these URLs directly within a web browser. What we find is that when using my Facebook account the browser re-directs to the success URL that includes the access_token parameter but when using my colleague's account the browser re-directs to the success URL that includes the access_token and then immediately re-directs again to the success URL without the access_token.
so... As far as we can tell this is either:
a) A change to the API which we cannot find documented anywhere
b) A bug in Facebook
c) Something that is now controlled by the user's Facebook security settings
Is there anybody who could explain why Facebook is acting differently with different accounts and how we can go about fixing this?
Thanks.
Kevin.
I have the same problem in my desktop applications.
And I just solve it with careful reading in ht*ps://developers.facebook.com/docs/howtos/login/login-for-desktop/. The solution is to change redirect_uri from ht*p://www.facebook.com/... into ht*ps://www.facebook.com/...
Hope this will help you just like it help me
NB:
change ht*p into http
sorry i have to change the http into ht*p so that i can post the answer.
I wonder what is the right technique to streamline the login to my site via Facebook.
Currently, I have a web site integrated with Facebook Login button. Right now, it's an independent web site, and not a "Facebook app" (running in the canvas). While this is not my decision, this could change in long term if matters.
The way the authentication work: the "fb-login-button" is redirected to my application URL using onlogin() event; the server side uses the cookie to retrieve the "access token" and perform further Graph API work. The business logic resides on the server side.
The current business requirement is the following:
Suppose someone posts a link to my site, somewhere in Facebook, for example in our site community page:
http://www.mysitedomain.com/offer1
A Facebook logged-in user clicking on the link - should get to the target page, after his Facebook identify got verified, and the result should be personalized for that user.
If a Facebook user already has an active session with my site - trivial.
Assuming a user had approved my site (app) in the past, but has no active session - here I am looking for the best practice to do the login.
Also, I would appreciate a hint how to handle the app authorization (i.e. showing the Facebook authorization dialog) in a most efficient way.
Thanks for any hint.
Check out FB Login Architecture and FB.getLoginStatus. Based on FB documentation, If you use javascript sdk, it only triggers a Popup on the same page and once authenticated it will go back to the same page. So once the login status is confirmed then you can get users information from graph api and update via AJAX on your page. You can also checkout this server side login. Hope this helps.