I'm following this guid to setup a hangouts bot, https://developers.google.com/hangouts/chat/how-tos/bots-publish
On step 4, when I go to the configuration tab on the API I keep getting this error:
The API "chat.googleapis.com" doesn't exist or you don't
have permission to access it
In the permissions section there are 2 accounts. Myself and the service account that I just made. Both are set as owners.
Did I miss a step? The doc I'm following seems to say I should be able to edit the configuration now.
This may be an issue with multiple accounts. Try using an Incognito window and logging in through there. If this is the problem, you may want to file a bug through the issue tracker.
Related
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.
We have a simple hangouts bot that has been working fine for several months. Starting yesterday 1 or 2 users indicated that they were receiving an error message when talking to the bot indicating that: 'Your administrator prevented you from talking to bots in direct messages'. Over the past 24-hours more and more people reported that the issue started happening to them until it was everyone. When it happened to me earlier today I messaged the bot 2 times about 5-minutes apart, it worked the first time then the second time I got the administrator prevented message.
I tested the #meet and #drive bot's and they both still appear to work.
I have confirmed that none of the settings on the bot have changed, most importantly that the 'Bot works in direct messages' option is still checked.
I have talked to our IT administrator who says that no settings have changed in our GSuite setup.
Looking through the documentation I can't find any mention of an issue or setting that would cause the above error. Is anyone aware of what could be causing the above.
Google Support statement
(...) if your domain currently applies a whitelist to restrict the set of G Suite Marketplace apps that users can install, existing internal bots may stop working. In order to appear and continue to function for users, the developers of these bots need to publish the bots to the domain as you can see on link. (...)
Solution
As said Jordansan this issue is related to the domain administration and to security enhancements. You may still use up to 5 email addresses to do your tests. Once you want your bot public, you will need to list it on the G Suite Marketplace.
To do so follow this guide Listing your bot on G Suite Marketplace. An extract is provided below :
G Suite Marketplace publication steps
This section tells you the specific steps you need to perform to publish your bot on G Suite Marketplace. The general steps are:
Create an OAuth client ID, if your project doesn't already have one.
Add the G Suite Marketplace SDK to your project and populate its configuration tab.
Populate the SDK's publish tab and submit.
The detailed steps for each of these are described in the following paragraphs.
For security reasons most organizations have (and should have) whitelisting enabled, which will prevent non white-listed marketplace apps to be enabled within the organization.
To deploy your bot you'll need to contact your GCP responsible and ask him to whitelist your bot.
Temporary solutions
What you can do is make the bot accessible to everyone in your organization. Assuming that the bot can be published.
If the bot shouldn't be public, you may implement your own connector to filter incoming queries and allow only selected email addresses. However the bot will still appear to everyone on the search screen, and everyone will be able to message it.
It's possible that your domain makes use of a new feature which requires bots to be whitelisted. This was introduced in a recent update. Previously, the admin setting was binary in that you could allow either all bots or none. Now any second party bots must be whitelisted if the administrator settings for that domain requires whitelisting.
You can find more information here: https://support.google.com/a/answer/6089179
I opened a ticket here: https://issuetracker.google.com/issues/137266964
Edit: We got this working by following the steps listed here: https://developers.google.com/hangouts/chat/how-tos/gsm-list and our GSuite admin white-listed the Bot for internal use. This eliminates the 5 user limitation and keep the current security settings in place for all other bots & GSuite Applications
I am attempting to add a project owner within Google Developer Console under Permissions. The original project was created with a domain user (Google Apps for Work) and I can add other domain users but cannot add external users (other gmail or different Google Apps domain user).
I receive a 504 error in the Console logs and a message saying "The server has timed out while trying to process your request."
Has anyone seen or resolved this issue? Or perhaps know of a way to contact Google support regarding this?
UPDATE:
I realized that the this happens for two of our projects and both projects have a prefix on the project ID: carrotcreates.com:xxxxxxxx
I am not sure if this is linked but carrotcreates.com is the primary domain for our Google Apps account.
Thanks!
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.
Got the following exception when calling api (/me) using the latest PHP SDK.
OAuthException: Cannot call API on behalf of this user.
The same exception appears for some facebook account only. Any clue?
I found the source of the problem (on our site, at least). In Facebook's developer console (https://developers.facebook.com/apps), our app was showing an invalid privacy policy. Due to this, Facebook had automatically placed our app into Sandbox Mode.
Updating our privacy policy and (more notably) removing our app from Sandbox Mode caused this error to cease.
Other users seem to have had some success with removing regional (country-specific) restrictions on who can and cannot log in to their app (https://groups.google.com/forum/#!topic/django-social-auth/XaE5dFXEqhA)
Additionally, #Igy's questions sound reasonable and might lead to finding a solution as well.
Best of luck! :)
Is that user's access token still valid? Has the user blocked you? Can you navigate to the user's profile manually? (i.e their profile might be unavailable)