We recently added a QnA Maker Bot to MS Teams and got it to Deploy on the Azurewebsites.net/api. Unfortunately in MS Teams when you direct message the bot it is not responding at all. We checked the logs and are not getting any errors either. Any Idea where we need to check next?
Thank you,
M
I had exactly this problem, and it was because I was trying to hit the bot directly rather than creating a Teams App first. You will need to install App Studio from the Apps blade on the left if you haven't already.
Open up App Studio and click on Manifest editor tab
Click Create a new app
Fill our all of the required information for App details
Generate/create an App ID. This is NOT the same as your Bot's App ID
Click on Bots tab under Capabilities and add your bot
Install app for testing in specific Teams or Chats
Submit is for if you want to publish to your company's App Store. If you download the package you could import it in Step 2 instead of creating a new app. Or use it as a template to do future apps offline instead of using App Studio for the whole process.
Once I set up the bot in this way, it started responding to me. I tried with another app after doing this for one and confirmed that I would NOT get a response from a bot unless I had set it up with a manifest through App Studio.
Related
I have a Teams bot (.Net Core 3.1 + Bot SDK 4.0) and I call task module from it to render my React app. A React app is a SPA located at the same App Service as a bot. It works fine at the local stand and at the developer's stand, but at the customer's test stand, after calling the task module, a problem arises.
At desktop windows app there is happening nothing at first time, after the second click of the button to open the task module, an error appears at the bottom of the adaptive card:
There is an error in the Developer Tools:
I also tried to open this task module in popup application mode, it returns an error window:
In the Developer Tools, in this case, I have the following errors:
When I try to open my React app from the browser or use it as a tab for my bot, it works fine. What should be the problem with opening it as a task module? Maybe I need to do some extra steps in the Microsoft Teams admin center?
I found a way to solve the problem. I installed the bot through a local upload of the manifest, but then I found out that it was also added to the list of applications for our organization (at Teams admin center), and apparently there was some kind of collision between them. After I uninstalled the application from my desktop Teams and installed it from the application pool - the error disappeared.
I have a question regarding installation of messaging extension app. Actually I assumed that I can upload my app to teams admin center "teams apps" and afterwards it is ready to use for all teams and all team members. I already did this steps with an app showing a custom tab and everything worked fine.
Across the documentation I only found information on how to sideload apps. That is working but only for the logged in user, not for other team members. Thats why I think app package seems to be ok.
So, what is the correct way to install an app containing a messaging extension to my teams so that all team members can use it? Does app manifest need to provide some special content?
Thanks for your help!
Yes, Admin has the privilege to install an app from the admin center by assigning custom policy to users. Please have a look at this document.
I've been working on a Microsoft Teams app, and have been using the conversationUpdate message type that should be triggered whenever the app (or a user) is added to a team to send a welcome message. I am using the upload a custom app feature that Microsoft Teams has to upload the app.
For some reason, when I add the app to the team I want it on, the conversationUpdate message has never fired for me on the first attempt. No error message or warning of any type. It doesn't work until I go to the team I just added the app to, click the ellipses for the team and go to manage team, click apps, and remove the app I just added, then add the app again to the team. Only then do I get the correct conversationUpdate message that I can use to send out a welcome message.
I've tested out various bots written by Microsoft in their BotBuilder samples here: https://github.com/microsoft/BotBuilder-Samples/tree/main/samples/javascript_nodejs and have gotten the same result as my custom bot. I don't know why this error occurs and if it is isolated to an app uploaded with the upload a custom app feature.
Does anybody have insight as to why this is happening and if it happens on the Microsoft Teams App catalog as well?
I eventually figured out what the issue was. It would work the very first time I added the bot to a Team, but when I removed it, I was removing it from the Apps -> Built for your org only and not also removing it from the individual Team I had added it to. For some reason, when I did it this way, the first time I added the bot back in it would not trigger the conversationUpdate activity. Presumably because it thought that it was added to that Team still. Not sure exactly why, but that's what is happening.
I am trying to build a Teams tab using an SPFx web part for a demo.
On my inital app the Sync to teams button in the app catalog was failing with this console error being returned...
https://{TENANT}/sites/AppCatalog/_api/web/tenantappcatalog/SyncSolutionToTeams 400
After running into this problem I started again and this time followed the below tutorial step by step but on my tenant the Sync to Teams button is disabled (This step is near in the end in the Making the web part available in Microsoft Teams section)
https://learn.microsoft.com/en-us/sharepoint/dev/spfx/web-parts/get-started/using-web-part-as-ms-teams-tab
I then tried to follow the alternative method of side-loading the app by creating a manifest manually using this tutorial...
https://learn.microsoft.com/en-us/sharepoint/dev/spfx/web-parts/guidance/creating-team-manifest-manually-for-webpart
This resuted in the installation succeeding as far as the setup tab screen (this provides a preview of your tab in a model popup before adding the tab to a channel)
The result was "Sorry, something went wrong" (This was the end result of side-loading both my customised web part another freshly yo sharepoint generated scaffold.
Really stuck on whether there's a tenant issue or maybe some node package or SPFx version issue.
Any thoughts would be greatly appreciated.
I received a same error from console which led me to this article.
In this case, the app was already synced to Teams store. If that's the case, you should find and remove it by opening Teams -> Apps -> Built for [tenantname]. After removing it here, I am able to successfully sync my app once more.
I'm using SPFx 1.8.1 version and added TeamsTab in supportedHosts manifest file. Deployed in tenant app catalog and tried to Sync to Teams. Then I'm getting same issue of SyncSolutionToTeams with 400 error. Please find the attached screenshot from console windwow.
The error occurs if the app is still in the Teams catalog. It doesn't override it and instead throws the error. This is a known bug and we will look to fix it in the future. For now, please try either manually updating the app from Teams (not from the SharePoint app catalog) or to delete the Teams app and then to resync from SharePoint.
In my case this error occurs when I changed title in webpart manifest file (webpart.manifest.json). When I rejected the change, it works. Probably there was some inconsistency in project files.
I've used app studio from MS Teams to creat a manifest for a Bot App. I've uploaded the full color picture as well as trasparent outlone. However the icon is not displaying at the chat window. Only the default icon is visivle.
Any ideas, how can I solve the issue? Thanks a lot!
Is your bot sideloaded or uploaded to your organization's private app store? In those cases, the image used for the bot in the chat window is taken from the bot registration in Bot Framework. (This is a known issue that we're tracking.)
To change your bot's icon:
If you registered your bot using App Studio:
Go to https://dev.botframework.com/bots and sign in with the same account you use in Teams
Select your bot, then go to Settings
Click on "Upload custom icon"
If you registered your app using the Azure portal:
Go to the Bot Service or Bot Channels Registration resource in Azure
Go to Settings
Upload a custom icon
As #Adrian Solis answer is indeed correct, I just wanted to add that it can also be related to caching issues. If you are changing icons and want to check if everything is working as expected, you can delete your browsers cache or the cache of the Microsoft Teams Windows App.
The Microsoft Teams Windows App has the following cache folders. Just stop the app, delete everything in this folders and start it again.
%appdata%\Microsoft\teams\application cache\cache\
%appdata%\Microsoft\teams\blob_storage\
%appdata%\Microsoft\teams\Cache\
%appdata%\Microsoft\teams\databases\
%appdata%\Microsoft\teams\GPUcache\
%appdata%\Microsoft\teams\IndexedDB\
%appdata%\Microsoft\teams\Local Storage\
%appdata%\Microsoft\teams\tmp\