Issue saving informations in OAuth consent screen - google-oauth

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!

Related

Botframework v4 - Facebook Channel - Operation returned an invalid status code 'Forbidden`

Last year I developed a chatbot with Microsoft Bot Framework that I integrated in the Facebook Messenger of a page. Everything worked fine until 16th of December (last successful log). The page is not used by a lot of people therefore the application might have worked also longer than that.
Today I tried to use the chatbot again and I did not get any response. In the Logs I just found the error message "Operation returned an invalid status code 'Forbidden`".
After a bit of Debugging I found out that the problem is sending messages back to the Facebook Messenger.
context.SendActivityAsync(...)
I did not change any configuration within my Azure Bot Channel registration recently. I am aware of the privacy changes within the Facebook API, but as I already struggle with sending a simple text response like "Hi" I assume that cannot be the problem. Also the permission scheme has changed for Facebook apps. I have the permission for "pages_messaging". Do I need another permission now? Or did I miss another change in the Facebook API?
Technical Details:
Facebook API Version v6 (tried also v9 but no change in behavior)
Chatbot based on .Net Core 2.1
Bot Builder SDK v 4.11
Any hints what I did wrong or where I can look for further information is much appreciated.
Edit: I tried to add a new page to my Facebook App and get following message:
There is a hint that a permission is missing, but I cannot find out which one I require. As I only send responses to FAQ's and if required handover to the customer service inbox I just requested the "pages_messaging" permission. Do I require any other permission now?
I found the problem. For everyone that might have the same problem:
In our case the administrator that added the Facebook pages to the application was removed from the admin permission list of the pages. After re-adding the admin permissions for the pages the bot started working again.

Issue with OAUTH consent screen

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.

How to implement Google authentication using Xamarin.Forms?

I am developing a login feature in that user can login into the application using the Google account and get user profile detail. For that, I am creating a project in google developers and it's verified by me.
I try with this reference here but when I try with this that is give me the error of "Disallowed user agent" and gives me the error of the open in safari or chrome when I try with the iPhone(iOS devices).
I also go through some other references like "Xamarin. Auth" but it doesn't work for me. When I set a redirection URL with clientId:/oauth2redirect or the Package Name(Bundle Identifier):/oauth2redirect . It gives me an exception of Not valid redirect Uri.
I also try to add JSON and p12 file on respective device-specific projects and set bundle resource but it doesn't work me.
If anyone has solution to this without using WebView than help me.
You can try this plugin from CroosGeeks
https://github.com/CrossGeeks/GoogleClientPlugin
Here is the sample app:
https://github.com/CrossGeeks/GoogleClientPlugin/tree/master/GoogleClient/GoogleClientSample
This is not using the WebView. The documentation is also quite good.

Google Developer Console's credential side permission

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.

Google Apps Marketplace SDK Invalid credentials (missing or invalid oAuth token)

I am trying to publish an application in Google Apps Marketplace. To publish I need to upload the icons while I am trying to click the select button it is showing the error Invalid credentials (missing or invalid oAuth token)
This is happening to me as well, so I tried testing it with different users on different environments and browsers, all with the same result. I believe this is a Google infrastructure problem, not anything you are doing wrong.
Perhaps one day someone at Google might realize there's a problem and it will mysteriously begin to work again. Hard to tell, since they refuse to offer any reasonable support.
If perhaps anyone from Google happens across this thread, pushing the select button opens a modal and my javascript console contains the following error (before several other errors):
Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('https://docs.google.com') does not match the recipient window's origin ('https://code.google.com').