I am trying to get an oauth 2.0 client id but I am redirected to the oauth consent screen. However the google oauth consent screen is giving me errors when I try to save my application name. I left the other fields blank as I was guided my my tutor to only fill up the application name and email field. I am having issues configuring the oauth consent screen. I keep getting an error that says
“the request failed because changes to one of the field of the resource is not supported.”
Its my first time using google oauth and I did everything my tutor did in the udemy course but I hit the save button, I get this same error all day! Please check my screenshots for more details. Any help will be appreciated..
try a unique name for your app
I had the same issue and it worked for me
It's an ongoing outage issue with Oauth Client Id Creation, you can see the banner here https://status.cloud.google.com/
Outage Banner
Should be fixed soon, hopefully!
If you created an api key before the redirection to the oauth consent screen for the app you want to integrate google sign in with, try adding the api key to the scope for google apis on the consent screen This worked for me.
It was a google server issue. I think their server was down at that particular time I was having the issue because the next day I tried it without doing anything different and it worked seamlessly.
Related
I have created an App in https://developers.facebook.com/apps and I have one Facebook page, in that I have created ads and I got some leads, those leads I can see in Leads Center in respective page.
So I need to retrieve this Leads into my server.
When I run this below API in browser excel file is downloading directly and I can see all my leads in that file https://www.facebook.com/ads/lead_gen/export_csv/?id=XXXXXXXXXXXXX&type=form.
By using my App(which I created in developer) done some setting and I created webhook for user,pages and permission, in permission I can see lead_retrival, ad_reads and I have tested, those tested leads are coming into my server by given webhook URL.
But how can I get my actual leads which is in Lead Center belongs to my page and is there any APIs are available ?
Is APP review necessary to retrieve leads from form or any other option(I tried Zapier but that is not I am looking for).
what I tried:
I am working on my server so I went through with this link PHP cURL to verify Facebook API login access_token on server?, and created all access tokens by my app and I am getting Success. Login is valid
then I did not understand next what I have to do.
Can any one help on it please?
Thanks
Sandeep
I' ve created a new AoG project and then I've enabled API from Google API console. To complete this I have to add informations in OAuth consent screen but I'm having the same error from days: "Failure to save" without explaination about it. I've tried both to add all the informations and only the few required (name and emails) but it still doesn't work. Someone have the same issue? Solutions?
I don't know for sure, but try changing the application name. I was trying to create an OAuth consent screen and it failed many times with the same error as you. I was trying to name the project "Google Play Console" and it failed. I then tried "google-play-console" and it still failed. Then I tried just "play-console" and it succeeded. I think some words are not allowed, like "google".
There was a Google service error, not depending on me. After few days everything was fine!
I have added a collaborator for my Pinterest app, however, when accessing the colaberators account and clicking on the application there is no 'authorise' button or anything similar. The "You still need at least 1 collaborator to authorize your app before you can submit" warning still shows on the collaberators account.
Ant help would be appreciated, thanks!
We had the same problem. You need to at least add two co-workers, one as collaborator and one as tester. These must be different people. And then, after some while (!) the authorize button has appeared.
The co-workers need to accept the invitation as well, of course.
After submitting, it will take some weeks (!) until you get the approval.
I had issue. By reading and following accepted answer, I waited 5 weeks and still submit for review button was not there.
What I did was I authorise my app for code which later I used for getting access token.
Once I successfully authorised my app using below authorisation URL the "Submit for review button " appeared in a second.
Authorisation URL:
https://api.pinterest.com/oauth/?response_type=code&client_id=XXXXXXXXXXXXX&redirect_uri=https://localhost:8000&scope=write_public read_public&state=abcdefg
Use your client_id to authenticate to your app. Once you are done with that you can see the "Submit For review button" after refreshing the browser.
Hope it helps!
for those who have this problem, note that you have to test your application before you could autorize or send to revision,
You need 3 Pinterest account, or 2 friends
register one as developer and another as tester
then, with the secret key and the app id, put it on your client application
after that, test the login,
finnaly go back to your pinterest app and the button for "send to revision" you wiil find it enabled,
Please confirm that you are using same App ID and App secret in your application which is in developer pinterest app.
Here is a quick 2019 year update:
You need two pinterest accounts, they should be following each other
and should be collaborators in the APP.
Have a ssl protected call back url, they only accept https urls.
Finally all collaborators should authorize the app through your
application/site. For this you need to already have the pinterest sdk
integrated in your project.
Now you can submit the app for review.
Our web app allows users to log in via Facebook. Technically, we are using Facebook OAuth2. We have implemented this login process two years ago. It worked fine until 13th November 2015 but since that day it does not. When our server sends the request
https://graph.facebook.com/oauth/access_token
with appropriate parameters (client_id, redirect_uri, client_secret, code), the response from Facebook has HTTP status 400. The response body is a HTML page saying "Sorry, something went wrong".
On 13th November, there was some problem on Facebook probably.
I have found the following message:
http://www.independent.co.uk/life-style/gadgets-and-tech/news/facebook-down-site-breaks-for-many-people-though-not-for-everyone-a6732906.html
However, our server still gets this error response after a week. We have an instance of the system deployed in the production environment and one more instance in the test environment (with different Facebook account, i.e. with different client_id and client_secret). Currently, Facebook login works fine in the test environment. I am not sure if it worked on 13th November.
Do you have any experience with recovery from such problem? Why does Facebook login work in test environment and does not work in the production environment in the same app? Why did the production instance break on a particular day and is still broken a week later?
Thanks for any help.
I had the same issue. I believe that the issue stems from passing in invalid scope in your authentication requests. Try removing the scopes in your authentication request to see if that works.
One more corner case I found in 2022:
In the App Dashboard, if you choose Facebook login for Business, same error happens. It will go away as soon as you select Facebook Login one.
Finally, the issue was resolved by restarting the servlet container (Tomcat 7). However, I have no idea why.
All of this is using exclusively the login button. Not the API serverside and not FB.login(). It would work for me sometimes and sometimes not and I couldn't figure out why. I would open a new window and it may work, or may not - but it seemed like once broken it was broken.
There appears to be an issue when using the Chrome 'Device simulator'.
Looking at the SDK Javascript (that's to say the SDK that the Facebook Login button uses) it checks to see if the device is a 'touch' device and if so it will use the m.facebook.com domain when requesting the oauth token.
This domain fails m.facebook.com:
However if the mobile device mode isn't activated when the page loads then it uses www.facebook.com and succeeds:
So for me the current workaround is:
Assuming you are developing with the console active.
When you need to reload your page press Ctrl + Shift + M to deactivate the mobile device mode.
Refresh the page
Once the button has initialized press Ctrl + Shift + M to reactivate it again.
If you see m.facebook.com then you didn't do it fast enough, or maybe you're using something like Angular with hot reload and you need to manually refresh.
I got an problem after i create and APIs on Google Developer Console and enable the GCM service,
but i want to add an server key at Credential next to APIs on left hand menu.
But it show me You do not have sufficient permissions to view this page.
Below are the image:
Is that any config i need to add?
I did follow what You do not have sufficient permissions to view this page to clear cache and use incognito mode to login, but still not work.
EDIT
Some time i relogin it work back, when i click to another side and click back it show the error again, and my solution is go to Credential than use top right corner account to logout and relogin , let it redirect you back to Credential, than it work. So is there any solution to fixed it permanently without relogin?
Thanks
It because of you have logged in multiple devices. so u have to log out from all devices. to do this go to gmail.com and log in using your email and password. and scroll down . you can see Details link . Click that link.
it will open new window. there u click
Sign out all other web sessions. than clear history. than do login and try . it will open without showing error.
I got the same problem. After following the below steps it got solved. This may help you as well.
Click on Apis under Api & auth
Click on "Google Play Game Services".
Enable the service.
Optional: enable "Google Play Developer API" as well. Most of the time it will enable by default.
I am facing the same issues.
Try using another browser like firefox - sometimes it works.
but after awhile, same error pops up.
Having the same issue as with you regardless what api i enable.. have tried all the suggestion posted earlier. but none of them worked, but when i tried to change my i.p.. using a vpn. and tried to access it.it worked, i can create or view my api now,tested it with other gmail account to confirm and started from scratch. to my surprise i didnt encounter that issue im having for hours.. no idea why my i.p is being rejected when accessing the credentials area..
I've resolve my issue, it's about the ISP you are using. I tried 3 ISP's and 1 of them got a success all the time, I don't have any permission error.