Background: I am using two features from slack API: slash commands and interactions. I have a service that handles both when Slack API redirects.
The problem is:
slash commands are accepted and redirected by slack to my service with no issues:
I can see it in the log coming in
It is handled by the service (shows the modal which the user is about to interact with)
interactions are rejected; Slack API simply gives back 403 to the end-user (shown in the same modal). I know the request is not redirected because my logs don't show it.
Again: slash commands just work with no problems, but interactions don't, even though they are configured with the same Request URL.
I searched for this problem in slack and tried looking in all the configurations in the slack API, but I couldn't find anything useful.
I have tried using a different Request URL (by appending /interactions) but with no avail; slack API still blocks it from my service.
I've been using for member in guild.members (or ctx.guild.members) since creatting my bot this spring and its worked no problem. Then one day, it only lists the bot itself.
Did we get a new version of discord.py or something?
Discord.py 1.5.0+ requires you to enable "Intents". In order to get a member list of a server, you will need to enable the server member intent in the discord developer portal (Click your bot application, and go to the bot tab), take a look at this link: https://discordpy.readthedocs.io/en/latest/intents.html#privileged-intents if you can't seem to find it. After you have done that, you need to do this in your code too.
For the code part, i think it's easier if you take a look at the discord.py docs yourself.
I have made a simple bot for Google Chat, which has been working perfectly fine for the past couple of weeks. I tried to make a change to the API configuration for Hangouts Chat, and am greeted by this error.
I have tried making different changes to the API, and receive the error every time. Even simple things such as disabling the bot status gives me the same issue.
I tried re-making the project from scratch, as well as trying a different account on the same domain. The issue persists.
I have my bot registered in dev.botframework.com. It is published, up and running well. I'm trying to integrate it on Microsoft Teams. For that, I need to create a manifest, which I'm doing using App Studio. When I arrive to the part of configuring the the bot endpoint on App Studio, App Studio says that I need to add teamsappstudio#microsoft.com to my bot, admin textbox in order for it to find my bot. Here's what it says that I should do:
So, I added teamsappstudio#microsoft.com to my bot as an admin as AppStudio says that I should do, but when I click "Setup" in the last part, it shows me the error: "We couldn't access your bot. Make sure you've added "teamsappstudio#microsoft.com" as an admin and try again".
I don't know what else to do!!
Help me with this one guys.
Thank you!
The of Teams App Studio that's live now has a bug - sometimes the email address we extract from your authentication token has uppercase characters. We assumed they were all lowercase but it's likely yours are not. We are changing the logic to ignore case so in a week or two it should work properly.
Sorry for the confusion and hassle.
I started using Microsoft Bot Framework and followed step by step all tutorials.
I has been able to register a new bot and to deploy it working good with emulator, but except it nothing else works.
Test connection to your bot chat do not works despite I get answer from emulator and from all connected channels, that where created and registered properly I always get an Unauthorized response or something like that, anyway no response, so nothing works.
I tried with Twilio, Web Chat, Telegram (Skype auth is pending) getting always the same response.
As it seems I strictly followed the tutorials, is there something else to do or to be approved? Or just the service is still not working at 100% as too young?
Thanks
If you are using HTTP you need to disable basic auth because the connector won't send your appSecret in the clear.
The solution is to make sure you register as HTTPS, or if you need to use HTTP then disable the basic auth.
Took me a while to get it working locally too. Oddly for me it only works when those 'secret' fields are empty, as mentioned and running in debug.
Running without debugging seems to always result in a 401
Hi I was facing same problem to work bot locally in v3. I just made everything blank in web.config and it is working.
I solved the problem.
It was related to https. It's not well explained into tutorial but when you create and publish a service in Azure it is created as http://XXXXXXX.azurewebsites.net as shocased into tutorial, but it will not work as your service must run in https.
I so used https://startssl.com to create a free ssl certificate then turned on SSL into my Azure service so everything started working.
I've cleaned up the getting started with the following; hopefully it will make it clearer for the next person who uses it:
Click the “Register a Bot” button and fill out the form. Many of the fields on this form can be changed later. Use a the endpoint generated from your Azure deployment, and don’t forget that when using the Bot Application template you’ll need to extend the URL you pasted in with the path to the endpoint at /API/Messages. You should also prefix your URL with HTTPS instead of HTTP; Azure will take care of providing HTTPS support on your bot. Save your changes by hitting “Create” at the bottom of the form.
Make sure you are using HTTPS. BotFramework will not work with basic auth so tokens are not passed in the clear.
See: http://docs.botframework.com/connector/calling-api/
Make sure that you republish your bot service after registering and getting the app Id and password. If you fail to do this you will get Unauthorized. The steps are 100% clear on this and I hit this for a minute.