I have created a message extension with the custom web form, it fails to send any data back to the bot on microsoftTeams.tasks.submitTask. It just closes the form, and the bot submit action method does not receive any data. No issues with other clients like web, windows, or mac. Any way to debug or look into log files on the mobile?
Event tried with this sample code for message extension and used the compiled TaskModule.zip package, it's also not working in the Teams iOS application.
try sending only one parameter into submitTask.You could do something like this.
microsoftTeams.tasks.submitTask(yourObj);
Related
We have a published app in the Teams App Store.
Our app supports task module.
It worked just fine but about a month ago we started to receive reports from our costumers that when they are trying to open a task module, teams app just freezes.
This is how i understand task module requests work, in 4 steps:
1. User clicks on the button with data {"msteams": {"type": "task/fetch"}}`,
2. Teams sends request with this data to the bot.
3. Bot handles the data.
4. Bot replies with the appropriate url to render.
So we tested what happens when we click on the task/fetch button.
First of all we saw an error in the teams console:
TaskModuleLaunchService: launchTaskModuleByInvoke failed: "could not find app definition for app 00000000-0000-0000-0000-000000000000" where *00000000-0000-0000-0000-000000000000* is out appID.
And we don't receive any requests from the teams on the bot's side. So basically we have an issue on the step #1.
Unfortunately, we couldn't reproduce this on our devices, using the same card with the exact same button.
How can we fix this? Any help would be appreciated.
Thanks in advance.
I open a web/html dialog from an adaptive card with the task/fetch Action.Submit.
Once the user is done with the work in the web dialog, I call microsoftTeams.tasks.submitTask with a resulting javascript object.
This works perfectly fine in the web and the desktop client. The dialog is closed and the bot on the server is triggered with the resulting object.
However in the IOS app, only the dialog is closed but the bot is never notified.
I have tried all variations of the submitTask (with botId or appId as second parameter or without second parameter). Nothing is successful on the IOS app.
Is there anything I can do to further debug that behaviour? Or is this a known bug?
I'm opening (using OpenUrl) an external webpage I control. During loading of this web page, from the server I wish to close the teams modal either directly, or by invoking the teams client to resend message with a parameter, so the bot can respond with a close response (which I have working).
I'm able to do other tasks from an external service, like posting messages to existing or new chats. But when I try to set the activity type to invoke, I get BadRequest response.
Task Module modal dialog can be closed using microsoftTeams.tasks.submitTask() which is part of Microsoft Teams JavaScript client SDK. This will closed the Task Module and submit the data back to Bot.
Please take a look at Task Module sample to see how it's called from client code.
ISSUE:
Today my chat bot stopped working and started giving the following error. No changes were made on my end when this started happening.
I could not find any error in console log. Then I tested the bot with Emulator and in Azure Portal's Test in Webchat feature and the bot worked fine. This bot is using webchat (iframe embed) as well as DirectLine channel. The DirectLine channel works fine it is only the webchat that is not working.
So to test my theory that I am getting the error because of webchat getting updated by Microsoft. I used the embed code in Azure Portal to use the latest webchat and the webchat channel started working.
BRIEF HISTORY:
To modify the UI of the webchat I used this method to modify the UI of the IFrame of my bot. This method requires to download the source of IFrame, create an HTML page and use that page as a source of your IFRAME in your website (you can see the customization in the image).
Now that I started getting the issue I mentioned above, I tried to do the same thing with the latest version of webchat but it is not working. The webchat is not sending messages and I cannot find what CSS file this new version of webchat is using.
WHAT I NEED GUIDANCE ON:
Either a way to continue using the old webchat with the proper UI
OR
How to update the UI of this new webchat version?
I can't advise on fixing the iframe version, but this already wasn't officially supported, and with the latest webchat update Microsoft is moving more to recommending botframework-webchat (directline) to format the UI. A good place to start is the branding sample.
That sample doesn't spell out the options in the code, but if you take a look at the default options file, that should give you everything you need to customize the chat the way you want.
What this does not do is set up the header that used to be present in ootb webchat (and which I see you customized in your example). Now the best way is to do this in html/css, and you probably can just reuse what you did for your custom option. I just created an additional DIV, set it to height: 40px;, then set the webchat DIV to height: calc(100% - 40px);. Anyone who's good with HTML can probably come up with better than this, essentially you just build your page however you want at that point and the webchat implementation just controls the chat area itself (essentially send box and response/bubble area). I also added a custom button to my header.
<div id="chatbotTitle"><h3 style="padding-left:10px;">OEM CSC Support Bot</h3><button class="btn" id="transcriptButton">Email Transcript</button></div>
<div id="webchat" role="main"></div>
The error you are receiving is not a web chat issue. It is an issue in your bot that is being reported via web chat because that is the client being used.
Usually, this error is referring to an incoming activity that your bot doesn't know how to handle (i.e. your bot logic). For example, you have a waterfall step in your main dialog that, depending on the user's response, opens a component dialog. That dialog gets user information (name, age, etc.) that, when complete, returns to the main dialog. However, the next step isn't prepared as perhaps the user exited that dialog prematurely or didn't answer all the questions as expected.
Whatever the case may be, because it isn't setup to handle the incoming activity, it isn't returning the dialog's turn status. You will need to debug your code, stepping thru it, to see which "step" is the root cause.
For me, I have experienced this when I set up Web Chat to send an event back to my bot. My bot didn't know what to do with the incoming event-type activity and would produce that error.
Hope of help!
I'm creating my first Microsoft Teams extension. For now I'm just trying to get the basic plumbing for a messaging extension working. I'm trying to build an extension which will allow a user to search for content in my service and then return a card into their compose window in personal and Teams chats.
I've tried to follow the basic guide ( https://learn.microsoft.com/en-us/microsoftteams/platform/messaging-extensions/how-to/create-messaging-extension ) for creating a messaging extension using App Studio. I've setup a bot as it describes, and I have built a dummy echobot endpoint for the bot (using Ruby). I am able to "chat" with my bot directly in the Teams client and it is able to respond.
My messaging extension defines an action based command with a taskInfo with a web view URL to render and a fetchTask set to false. I've written a basic static HTML page for this and included the teams-js library. The web view loads and the teams-js library initialization callback is called. I have a submit button which calls microsoftTeams.tasks.submitTask which as I understand it, should be calling my bot with a "composeExtension/submitAction" message to which I would respond with the card. (Based on https://learn.microsoft.com/en-us/microsoftteams/platform/messaging-extensions/how-to/action-commands/respond-to-task-module-submit?tabs=json )
I've tried installing my extension in Teams through the "Upload a custom app" option both as a "for me and my teams" and "for " but still have the following issues.
When I open my extension in the Teams client from the compose area and click this submit button in my iframe content, the submit I get a "Unable to reach app. Please try again" error displayed. In the dev console, I can see that the response to the "invoke" http post is {"errorCode":404,"message":"V3 agent not found."}
No traffic is actually sent to my bot during any of this process.
I saw this older post - Compose extension is throwing error : V3 agent not found . The https://dev.botframework.com/bots/ it refers to seems to be outdated, but in the Azure "Bot Channels Registration" console, I have gone to Channels and added "Microsoft Teams" (which I believe is the new equivalent).
Has anyone seen this happen and figured out what was going on? Much thanks!
Here is sample code for composeExtension/submitAction for Bot SDK V3. Make sure you pass the bot id and command text in taskInfo object.
case "composeExtension/submitAction":
string commandid = JsonConvert.DeserializeObject<Models.TaskModuleSubmitData<string>>(activityValue).commandId;
taskInfo = GetTaskInfo(commandid);
taskEnvelope = new Models.TaskEnvelope
{
Task = new Models.Task()
{
Type = Models.TaskType.Continue,
TaskInfo = taskInfo
}
};
return Request.CreateResponse(HttpStatusCode.OK, taskEnvelope);
Hilton had the right answer.
I had grabbed the Subscription ID from the Bot Channels Registration page instead of the App ID from the Azure Active Directory -> Apps Registration page and used that in the messaging extension manifest as the "botId" in the composeExtensions array. After fixing that I'm now getting messages submitted to my bot backend.