Forum Widgets
Latest Discussions
"Manifest parsing has failed." in Developer Portal
I am using the Developer Portal app in Teams. I got "Manifest parsing has failed." error when click "Preview in Teams" button. AlsoI got "App does not have the required permissions for this operation." error after click "x" button. I have no validation error in the manifest file. How can I fix it?Mgmt.AppCatalog.LOBApp.Upload.BadRequest.UnknownTeamsAppManifestExceptionType error has occured
I cannot upload custom app into organization becauseMgmt.AppCatalog.LOBApp.Upload.BadRequest.UnknownTeamsAppManifestExceptionType error has occured. What I tried: I tried to upload same app to other tenant but got same error. I tried to upload other appbut got same error. What happened?Image inserted in incoming webhook is not working for new Teams version.
I am trying to insert an image into anincoming webhook using adaptive card and message card. But it is not displaying in the new Microsoft Teams version (23217.806.2340.1703.). But this is working on Old Teams version 1.6.00.24078 (64-bit). I am using below sample code to display this card. { "type": "message", "attachments": [ { "contentType": "application/vnd.microsoft.card.adaptive", "contentUrl": null, "content": { "$schema": "http://adaptivecards.io/schemas/adaptive-card.json", "type": "AdaptiveCard", "version": "1.5", "body": [ { "type": "TextBlock", "text": "For Samples and Templates, see [https://adaptivecards.io/samples](https://adaptivecards.io/samples)" }, { "type": "Image", "url": "https://adaptivecards.io/content/cats/1.png" } ] } } ] } Please reply if you have any solution to this issue or have any suggestions. Thanks,
Graph API: create a PSTN call and invite a PSTN participant
Hello everybody, We are using the MS Graph API within a C# project. After successful creating a PSTN call from our bot like described here https://docs.microsoft.com/en-us/graph/api/application-post-calls?view=graph-rest-1.0&tabs=http#example-7-create-peer-to-peer-pstn-call-with-service-hosted-media we run into the next problem: We want to invite another PSTN participant to this existing call like described here: https://docs.microsoft.com/en-us/graph/api/participant-invite?view=graph-rest-1.0&tabs=http#example-4-invite-one-pstn-participant-to-an-existing-group-call. But we receive following event: { "value": [ { "changeType": "Deleted", "resourceUrl": "/communications/calls/981f6100-cb65-42d9-af3c-1390c68cac8b/operations/5fedb136-cff9-446d-a8bc-4166db960e19", "resource": "/app/calls/981f6100-cb65-42d9-af3c-1390c68cac8b/operations/5fedb136-cff9-446d-a8bc-4166db960e19", "resourceData": { "@odata.type": "#microsoft.graph.inviteParticipantsOperation", "participants": [ { "@odata.type": "#microsoft.graph.invitationParticipantInfo", "identity": { "@odata.type": "#microsoft.graph.identitySet", "phone": { "@odata.type": "#microsoft.graph.identity", "id": "+49175********" } } } ], "status": "failed", "resultInfo": { "@odata.type": "#microsoft.graph.resultInfo", "code": 403, "subcode": 9999, "message": "addParticipants failed for participant 4:+49175******. Underlying reason: Call does not contain the metadata required for making this PSTN dial out.. DiagCode: 403#10151" }, "id": "5fedb136-cff9-446d-a8bc-4166db960e19" }, "@odata.type": "#microsoft.graph.commsNotification" } ], "@odata.type": "#microsoft.graph.commsNotifications" } Any idea why we can not invite another PSTN participant to an existing call from the bot to a PSTN number? Thanks. Regards Gerd
Images in Adaptive Cards in New Teams Client not showing
Hello Community, I've encountered an issue with Teams Webhook Connector where images in Adaptive Cards are not displaying correctly in the New Teams Client, although they work as expected in the classic version. Our clients have reported that while messages are visible, the images fail to appear. This problem does not occur in the classic Teams client or when viewed in a browser, which I presume is utilizing the classic client as well. To clarify, I'm using the latest Adaptive Cards version (v1.5) compatible with Teams, and this issue is consistent across both Windows and Apple versions of the New Teams Client. Unfortunately, there seems to be no information available about this compatibility issue in the Adaptive Cards documentation or designer tool. Below is a simple Adaptive Card JSON that illustrates the problem: { "type": "AdaptiveCard", "body": [ { "type": "TextBlock", "size": "Medium", "weight": "Bolder", "text": "This is a headline" }, { "type": "Image", "url": "https://img.cdn-pictorem.com/uploads/collection/D/DN4DFF8JRC/900_Nature-Art_colorful--paintings.jpg", "width": "300px" } ], "$schema": "http://adaptivecards.io/schemas/adaptive-card.json", "version": "1.5" } For visual reference, here is how the card renders in both clients: Classic Teams Client: New Teams Client: I have not found a workaround yet and would greatly appreciate guidance on how to resolve this issue. Any suggestions or updates regarding the new client's support for Adaptive Cards would be very helpful. Thank you. Best regards
Images sent by chat bot not shown after Teams update
We have a chat bot that can send plots of measurement data as attachments. Since a Teams update today of my Windows client app (to 1.4.00.22976), the pictures are not shown anymore. The outline is still visible. Adaptive cards that contain e.g. tables work fine, the problem is only with images. Another error that appears since today is displayed in the login card, see below. The login clearly works, since the bot can use delegated authority to access data from our SharePoint. But it always complains about being unable to reach the app. The bot works perfectly fine using the web client, my mobile, or a colleagues' computer (with the old Teams version), so I'm thinking it must be the client app. The chat bot is sideloaded using a zip file (upload custom app), it is a development version. The relevant domains (*.botframework.com for authentication, *.azurewebsites.net for the bot webserver) are added to the validDomains attribute in the manifest. Picture missing: Login error:
Root bot, skill bot and scaling
Hi, We need help with scaling. Problem statement: With 2 instances of root bot running, a skill bot invocation is unable to return results reliably to the root bot. With 1 instance of the root bot and 1 instance of the skill bot, everything works as expected. We configured the root bot with "Scale Out" and "Manual Scale" to set the instance count to 2. When we repeat the interaction, we see that the skill response is not getting returned reliably. In a successful scenario where the user's skill response is routed back to the root bot that the user interacted with, the user gets the skill results. In a failed scenario, the user's skill response was routed to the root bot instance that the user did not interact with. Hence, the results are lost. How do we ensure that the skill results are returned to the correct root bot instance? We reviewed the "Skills overview" documentation athttps://docs.microsoft.com/en-us/azure/bot-service/skills-conceptual?view=azure-bot-service-4.0,but it does not mention anything about scaling and persistence. We had thought that the lack of persistence could be due to the bots' conversation state. However, our root bot is currently storing all conversation states in DB. Since both instances are using the same DB connection string, they should have access to the same conversation states in the DB. Thank You
