My app has been OAuth verified for youtube and youtube.upload.
When I OAuth with these scopes, it's still not working.
I get the following in the web browser as before verification. They closed out my ticket, so I have no means to contact them.
Sign in with Google temporarily disabled for this app
This app has not been verified yet by Google in order to use Google Sign In.
If you are a developer for this application, please submit a verification request to re-enable Sign in with Google. Learn more
Please advise
Sign in with Google temporarily disabled for this app This app has not been verified yet by Google in order to use Google Sign In.
If you are a developer for this application, please submit a verification request to re-enable Sign in with Google. Learn more
The message you are getting clearly states the issue. Your application is not verified or its verification has bee removed. In order to fix this you must go thought he verification process. You might want to check your email and see if there is any messages from google as to why your verification was removed. I have seen several posts like this over the last week it seams Google may be going though projects.
Related
We have a mobile app and our users got a
"sign in with google temporarily disabled for this app"
When they tried to login their YouTube account with iOS (There's no problem with Android devices).
We submitted a verification request long time ago, and we got from YouTube an email (May 26th 2020),(May 26th 2020):
"Hi Adam,
Thanks for working with us on the YouTube API Services compliance review. We have completed your review and do not require any further actions from you at this time.
We may reach out again to re-review your API Client for compliance with YouTube API Services Terms and Policies.
We appreciate your time working with us on this and please continue to comply with the YouTube API Services Terms and Policies."
Since then, nothing had changed and our app hasn't been verified yet, and our users can't connect with their youtube accounts.
What can we do? We are just waiting and we don't even know how to contact YouTube and ask about our specific case/project.
Thanks you,
Adam.
sign in with google temporarily disabled for this app
Means that your application has not been verified by google. You need to go through the verification process.
You can use a project for development without verification. However there are some limitations (more information here). Basically, you have now reached the limit of 100 users accessing the application.
If you still havent heard anything from google after they say they have verified your application I think the only thing you can do is to submit it again and double check that you are using a client that was created under the project that you requested verification for there's really nothing else you can do.
Hi While using Google Calendar in my iOS APP, the screen prompts a warning like as bellow
This app isn't verified by google yet...
only proceed if you know and trust the developer
To avoid this warning I need to submit my iOS App to Google OAuth Verification
I searched in different sites but i didn't get a clear doc to Submit An iOS App for Google OAuth Verification.
Could someone help to provide the steps/guidelines link to Submit An iOS App for Google OAuth Verification.
Thanks in advance...
Go to the google developer console Under credentials
You will find the consent screen tab
At the very bottom of this page you will find a button
Before submiting you should read though the information provided on that page along with the links
OAuth verification
To protect you and your users, your consent screen
and application may need to be verified by Google. Verification is
required if your app is marked as Public and at least one of the
following is true:
Your app uses a sensitive and/or restricted scope
Your app displays an icon on its OAuth consent screen
Your app has a large number of
authorized domains
You have made changes to a previously-verified
OAuth consent screen The verification process may take up to several
weeks, and you will receive email updates as it progresses. Learn more
about verification.
Before your consent screen and application are verified by Google, you
can still test your application with limitations. Learn more about how
your app will behave before it's verified.
We are facing the below screen when trying to authenticate to Google. The app that we are trying to authenticate is used for internal development and we did not publish it to our users.
Any idea why this occurs?
We faced an Unverified App screen before (as below) but now the authentication is disabled.
OAuth Client Verification
Starting July 18, 2017, Google OAuth clients that request certain sensitive OAuth scopes will be subject to review by Google.
OAuth Client Verification
Starting July 18, 2017, Google OAuth clients that request certain sensitive OAuth scopes will be subject to review by Google.
Review is not required if you are only using it under the same account as created the project in Google Developer console. You can read more about this change in this help center article.
This change applies to Google OAuth web clients, including those used by all Apps Script projects. By verifying your app with Google, you can remove the unverified app screen from your authorization flow and give your users confidence that your app is non-malicious.
Once you have applied for verification it takes around a week and it should start working.
I found this thread some time ago when this happened to us in our development project on Google Cloud Platform.
You can use a project for development without verification. No problem on that. But there are some limitations (more information here and here). Basically, we reached the limit of 100 users accessing the application. It was strange because we were testing with few accounts (5-6) until we found that, if you uninstall and install the application again, it counts as a new user. We were testing incremental authorization, so we uninstalled/installed the application a lot of times and we reached the quota.
When you reach this limit, you will see the message "Sign in with Google temporarily disabled for this app" and only users from the organization where the project is hosted can access the application. So we couldn't make test with our accounts from a demo domain or our Gmail accounts.
The only solution available was to pass the OAuth verification form (even if you didn't want to publish the application), but there were problems to do it. For example, it was mandatory to remove http://localhost from valid OAuth URLs. And more problems related with development.
❗ But this has changed recently. I have accessed to OAuth credentials screen in Google Cloud Platform (APIs & Services > Credentials > OAuth consent screen) during this week and now the page it's different. Now you don't need to specify "Authorised JavaScript origins" and "Authorised redirect URIs", you just need to specify your scopes for Google APIs and the Authorised domains. Then, at the bottom of the page you will find the button "Submit Verification" and the process will start. You will also find some information on the right:
About the consent screen
The consent screen tells your users who is requesting access to their data and what kind of data you're asking to
access.
OAuth Developer Verification
To protect you and your users, your
consent screen may need to be verified by Google. Without
verification, your users will see an additional page indicating that
your app is not verified by Google.
Verification is required if
Your application type is public, and You
add a sensitive scope Verification may take several days to complete.
You will receive email updates as it's processed.
Saving without publishing
Even though your consent screen is
unpublished, you can still test your application with users with the
following limitations:
Sensitive scopes are limited to 100 grant requests before verification
is required
Users see an additional page indicating that your app is
not verified by Google.
To include "Authorised Javascript Origins" and Authorised redirect URIs" you need to go to APIs & Services > Credentials and there click on your OAuth 2.0 client ID. There will be a form where you can add them.
In our case it took 1 day to get a response from Google. In the email there were some instructions to pass the verification. We had to reply the email with a video uploaded on YouTube addressing the following points:
How does user sign-up on your app and grants access to the sensitive scopes requested in verification?
OAuth consent screen as seen by end users
How does your application use the requested scopes to provide services to developers?
A test account email and the password for us to test the user sign-up process and validate the project's functionality.
We recorded a video showing points 1, 2 and 3 and sent them a test account for number 4.
After 1 day, we got another response from Google confirming that our project had been verified.
So finally the problem was solved! 🙂
I hope this could help people in the same situation. It was really annoying for us.
I had to go into my Google Apps Script settings and turn on the "Google Apps Script API" setting. Then I tried again, and the script executed correctly without issue.
I had used the script a couple of weeks ago and it worked fine, so something must have happened between then and now that changed it... Not sure what caused that setting to switch.
I'm using google authentication to sign in with firebase.
The authentication process works well and I'm able to create the credentials and authenticate.
My problem is when, after signing out from firebase and google, the user tries to sign in using google again. At this point google will automatically authenticate with the account used previously.
I tried both sign-out and disconnect option from google api but the result is the same.
I partially found what my problem was, here steps to reproduce:
Not signed in with google in app and not signed-in in safari on the device with a google account
Sign in with the application using a google account
Now I am signed-in in app AND in safari as well with the same account
When I sign-out from the application, safari is still authenticated with this user
I'm not able to see the account choice in app until I sign-out the google account from safari on the device
This problem doesn't show up if safari (point 1) was already signed-in with a different google account. In this case I will always have a choice between the two accounts in app.
Is there a way to sign out from the app and always shows the account choice when signing in with google again?
There are many Authentication URI parameters. One of them is "prompt" which could have a "select_account" value. It helped me to resolve the same issue for Auth0-service Google integration. Maybe could be useful for your issue if the SDK allows setting parameters for sign in.
See docs here: https://developers.google.com/identity/protocols/OpenIDConnect#authenticationuriparameters
I am trying to integrate paypal to my web app. I want to use paypal as payment gateway. In the process i am encountering various errors as listed below.
1) I logged into developer.paypal.com. When i click Accounts under Sandbox it lists all sandbox accounts i have. I wanted to delete the unused account but it says "Something went wrong. One or more sandbox accounts could not be deleted. Try again.".
2) I created merchant or business account in developer.paypal.com. I then logged into sandbox.paypal.com using the created business account. In the dashboard page there is Tools at the top. I clicked on it and selected API credentials in order to get the api credentials for paypal integration to my web app. After clicking on it, it redirects me to my official paypal account dashboard page. i.e https://www.paypal.com/myaccount/home
3) Finally another issue i have been facing and of which i have not been able to receive any solution yet is described in detail here. error trying to make sandbox paypal to work with rails?
So seeing all these issues i am wondering whether sandbox account is full of bugs and cannot be trusted for api integration testing. In that case does one recommend testing with real accounts? but that will be expensive because we need to send real money.
I appreciate any help on this dilemma. Thanks!
1) Unfortunately, this is something that tends to happen in their sandbox. You can try again later and it might work...it might not.
2) If this happens you should be able to add "sandbox" back into the URL. So in this case if you change it back to https://www.sandbox.paypal.com/myaccount/home then it should load what you're expecting.
3) Need to see the actual error code that's coming back in the PayPal response to help more on this one.