Closed sharontf closed 6 years ago
Same here. My bot works with Web Chat and Skype, but not with MS Teams. From ngrok I see that no traffic is reaching my endpoint when I'm sending messages from MS Teams. The issue was present both before I migrated to Azure and updated my Node.JS Bot Framework from 3.9.0 to 3.13.1, as well as after I did both.
BTW, I actually had the same issue with Skype earlier today, but then a couple of hours ago it suddenly started to work. Web Chat has been working fine all the time.
@sharontf for reference are you using .NET or Node.js template?
here's the general checklist for loading your bot into MS Teams:
Quick MS Teams bot deployment checklist:
Recommended reading:
I'm in the same boat and have done all of these things. I'm using a .NET bot based on the AdaptiveCards template.
It didn't work all day Friday and then all of a sudden it started to. I then came back Monday and it wasn't working at all. It does work via web chat. I am using ngrok and the bot calls are not even getting to ngrok. I can't find any errors in Azure or teams though- is there somewhere I should look?
I decided to try and create a brand new bot via Azure Portal. Updated my manifest.json and reuploaded to Teams. Once again, everything fine via webchat, through Teams I sideload the app and it doesn't answer me in the channel or receive any calls at all.
Is there a place I can go in either Teams or Azure to debug this?
It suddenly started to work for me approximately an hour ago.
The only thing I changed is I enabled the sideloading for Apps in O365 earlier in the day. It did not work immediately after that, and I am experimenting with the 1:1 type of chatbot without actually uploading the zip file to Teams, so I'm not sure that the sideloading switch was the thing that resolved it.
My bot still does not work.
You can test this with no code at all, by just creating a bot through one of the templates and then deploying it to Teams Channel.
Same problem here. My MS Teams bot hosted on Azure Bot Service does not deliver the messages to the endpoint. Whereas other bots, which luckily I did not migrate to Azure Bot Service work perfectly fine.
Hi, I have a bot deployed in Azure and has a valid Microsoft App Id and Password , and connected the bot it into Teams and the manifest file follows, but I am not getting reply from bots in teams { "$schema": "https://statics.teams.microsoft.com/sdk/v1.2/manifest/MicrosoftTeams.schema.json", "manifestVersion": "1.2", "version": "1.0.0", "id": "280b5919-7217-4072-ba52-adaa8e4f8b72", "packageName": "com.contoso.helloworld", "developer": { "name": "Contoso", "websiteUrl": "https://www.microsoft.com", "privacyUrl": "https://www.microsoft.com/privacy", "termsOfUseUrl": "https://www.microsoft.com/termsofuse" }, "name": { "short": "BottestHti", "full": "To test sample bot in Azure" }, "description": { "short": "Hello World App for Microsoft Teams", "full": "This sample app provides a very simple app for Microsoft Teams. You can extend this to add more content and capabilities." }, "icons": { "outline": "contoso20x20.png", "color": "round.png" }, "accentColor": "#60A18E", "staticTabs": [{ "entityId": "com.contoso.helloworld.hellotab", "name": "Hello Tab", "contentUrl": "https://bottesthti.azurewebsites.net/", "scopes": [ "personal" ] }], "configurableTabs": [{ "configurationUrl": "https://bottesthti.azurewebsites.net/about", "canUpdateConfiguration": true, "scopes": [ "team" ] }], "bots": [{ "botId": "280b5919-7217-4072-ba52-adaa8e4f8b72", "needsChannelSelector": false, "isNotificationOnly": false, "scopes": [ "team", "personal" ] }], "composeExtensions": [{ "botId": "280b5919-7217-4072-ba52-adaa8e4f8b72", "scopes": [ "personal", "team" ], "commands": [{ "id": "getRandomText", "description": "Gets some random text and images that you can insert in messages for fun.", "title": "Get some random text for fun", "initialRun": true, "parameters": [{ "name": "cardTitle", "description": "Card title to use", "title": "Card title" }] }] }], "permissions": [], "validDomains": [] }
Issue is still on. In my case adjusting "messaging endpoint" from Azure Portal helped https://github.com/Microsoft/BotBuilder/issues/4010
Thank you for opening an issue against the Bot Framework SDK v3. As part of the Bot Framework v4 release, we’ve moved all v3 work to a new repo located at https://github.com/microsoft/botbuilder-v3. We will continue to support and offer maintenance updates to v3 via this new repo.
From now on, https://github.com/microsoft/botbuilder repo will be used as hub, with pointers to all the different SDK languages, tools and samples repos.
As part of this restructuring, we are closing all tickets in this repo.
For defects or feature requests, please create a new issue in the new Bot Framework v3 repo found here: https://github.com/microsoft/botbuilder-v3/issues
For Azure Bot Service Channel specific defects or feature requests (e.g. Facebook, Twilio, Teams, Slack, etc.), please create a new issue in the new Bot Framework Channel repo found here: https://github.com/microsoft/botframework-services/issues
For product behavior, how-to, or general understanding questions, please use Stackoverflow. https://stackoverflow.com/search?q=bot+framework
Thank you.
The Bot Framework Team
Bot Info
Issue Description
Bot works fine on Test in Web Chat on Azure, but does not work when deployed to a Teams Channel. I had an almost identical bot on the old Bot Framework before the update, and this new bot is not working. ## Code ExampleUsing C#
Reproduction Steps
Expected Behavior
Actual Results
Is there any way to create a bot using the old format temporarily, just so I can get this bot up and running? And then change to the new format in March?