Hi!

Skype Web Control Skype web control does not show icons

What could be the problem?

<span class="skype-button bubble " data-bot-id="myid"></span>
<script src="https://swc.cdn.skype.com/sdk/v1/sdk.min.js"></script>

Thanks!

Hi,

I know SFB is still in beta, but are attachments on SFB supported?

I tried sending an attachment to my bot but seems like the webhook didn't even fire. Also, the file transfer on SFB failed for some reason.

I'm looking for mistakes on my end but we log every incoming message, and seems like nothing happens at all when I send an attachment on SFB. On normal skype, it works fine.

Thanks

I have bots working with the Bot Framework v3 and v4 through Web, Skype for Business, MS Teams and Slack. In the Azure Portal, in the Bot service I go to analytics and see usage data but not for Skype for Business. Also when I query for custom events in App Insights Analytics I only see entries for the other channels.
Is there a problem with that channel? Is there something that has to be done in order to enable it? I didn't see any mention about that in the documentation, and interestingly enough the example screenshot contains a lot of channels but not Skype for business, odd being a Microsoft documentation.

Just wanted to make sure everyone saw this announcement for TLS 1.2 enforcement coming on 4.Dec.2018.

https://blog.botframework.com/2018/11/06/announcement-azure-bot-service-enforcing-transport-layer-security-tls-1-2/

The short story is that this will have no effect on the vast majority of your bots or clients. But those running on outdated operating systems or browsers may need to upgrade. This move to a more secure protocol is all about keeping your data safe and is the direction the entire Internet community is going.

More details are in the blog post, including a nice whitepaper about what operating systems will be impacted and what to do about them.

Hi!

You could add to the list of supported channels such as Viber ? :)

Bot Info

• SDK Platform: .NET
• SDK Version: 3.16.0.38344
• Active Channels: MS Teams (paid & free), Skype
• Deployment Environment: Azure Bot Service
• Bot name: blueybot
• App ID: 86a089d9-add4-4b71-9466-afb23474ccec

Issue Description

This issue was originally opened & assigned in previous V3 repo here

My simple bot receives messages & replies with text. I have published it to Microsoft Teams (paid service) & Microsoft Teams FREE using the "upload a custom app" link. The scope in manifest.json is both "team" and "personal". The manifest.json was created in Teams App Studio.

In Teams FREE - When I send a message to the bot in a team using @mention, it does not reply.
In Teams FREE -When I send a message to the bot in a personal 1:1 chat, it does not reply. This had worked a few hours ago, with no app changes made since.

In Microsoft Teams (paid service) the bot works perfectly in both a team channel & 1:1 personal chat.
In Skype, the bot works perfectly also.

The same Manifest.json was upload to Teams FREE and Teams (paid service).

In Azure Portal Bot Channel Registration, no issues are reported for Microsoft Teams channel.

Code Example
No code to share. Regular code that compiles and runs fine in Skype and paid version of MS Teams

Expected Behavior
In Microsoft Teams FREE I expected to receive replies from the bot in both a team channel & 1:1 chat

Actual Results
In Microsoft Teams FREE there are no message received from the bot in a team channel or a 1:1 chat.
Tried remote debugging using VS and no message received by the bot.

Will the "Bot Channels Registration" Azure resource type support deployment/management using Azure Resource Manager templates? This is currently the only component of my bot infrastructure that can't be managed with ARM.

These would be great if added as they make a great UX
we currently use them by sending them as channel specific data

- Media Template
- Email Quick Reply
- Phone Quick Reply
- List Template
- Receipt Template

Thank you

Version

• SDK: .Net Core 2.1
• Deployment Environment: Azure Bot Service
• Microsoft.Bot.Connector Version: 3.15.3

Issue Description

I'am trying to publish my bot. During test ping request I get InternalServerError. The connector client makes POST request on https://dev.botframework.com/v3/conversations/test/activities but instead of json it gets some html.
So app throws Newtonsoft.Json.JsonReaderException:

Unable to deserialize the response. Unexpected character encountered while parsing value: <. Path '', line 0, position 0.

Bot works properly in unpublished Skype and Web Chat channels.

Here's call stack:

Microsoft.Rest.SerializationException:
   at Microsoft.Bot.Connector.Conversations+<SendToConversationWithHttpMessagesAsync>d__7.MoveNext (Microsoft.Bot.Connector, Version=3.15.3.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Private.CoreLib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Private.CoreLib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at Microsoft.Bot.Connector.ConversationsExtensions+<SendToConversationAsync>d__5.MoveNext (Microsoft.Bot.Connector, Version=3.15.3.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Private.CoreLib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Private.CoreLib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at SoftServe.ThinkIterateDeliver.BotServiceApp.BL.Implementation.ActivityDispatcher+<ProcessActivity>d__4.MoveNext (SoftServe.ThinkIterateDeliver.BotServiceApp.BL, Version=1.0.0.0, Culture=neutral, PublicKeyToken=nullSoftServe.ThinkIterateDeliver.BotServiceApp.BL, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null: C:\Build\Agent_06\11\s\SoftServe.ThinkIterateDeliver.BotServiceApp.BL\Implementation\ActivityDispatcher.csSoftServe.ThinkIterateDeliver.BotServiceApp.BL, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null: 54)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Private.CoreLib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Private.CoreLib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at SoftServe.ThinkIterateDeliver.BotServiceApp.Web.Controllers.Api.InteractionController+<ProcessMessage>d__2.MoveNext (SoftServe.ThinkIterateDeliver.BotServiceApp.Web, Version=1.0.0.1, Culture=neutral, PublicKeyToken=nullSoftServe.ThinkIterateDeliver.BotServiceApp.Web, Version=1.0.0.1, Culture=neutral, PublicKeyToken=null: C:\Build\Agent_06\11\s\SoftServe.ThinkIterateDeliver.BotServiceApp.Web\Controllers\Api\InteractionController.csSoftServe.ThinkIterateDeliver.BotServiceApp.Web, Version=1.0.0.1, Culture=neutral, PublicKeyToken=null: 35)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Private.CoreLib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Private.CoreLib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter1.GetResult (System.Private.CoreLib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at Microsoft.AspNetCore.Mvc.Internal.ActionMethodExecutor+TaskOfIActionResultExecutor+<Execute>d__0.MoveNext (Microsoft.AspNetCore.Mvc.Core, Version=2.1.3.0, Culture=neutral, PublicKeyToken=adb9793829ddae60)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Private.CoreLib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Private.CoreLib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Threading.Tasks.ValueTask1.get_Result (System.Private.CoreLib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.ValueTaskAwaiter1.GetResult (System.Private.CoreLib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker+<InvokeActionMethodAsync>d__12.MoveNext (Microsoft.AspNetCore.Mvc.Core, Version=2.1.3.0, Culture=neutral, PublicKeyToken=adb9793829ddae60)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Private.CoreLib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Private.CoreLib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult (System.Private.CoreLib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker+<InvokeNextActionFilterAsync>d__10.MoveNext (Microsoft.AspNetCore.Mvc.Core, Version=2.1.3.0, Culture=neutral, PublicKeyToken=adb9793829ddae60)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Rethrow (Microsoft.AspNetCore.Mvc.Core, Version=2.1.3.0, Culture=neutral, PublicKeyToken=adb9793829ddae60)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Next (Microsoft.AspNetCore.Mvc.Core, Version=2.1.3.0, Culture=neutral, PublicKeyToken=adb9793829ddae60)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker+<InvokeInnerFilterAsync>d__13.MoveNext (Microsoft.AspNetCore.Mvc.Core, Version=2.1.3.0, Culture=neutral, PublicKeyToken=adb9793829ddae60)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Private.CoreLib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Private.CoreLib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult (System.Private.CoreLib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker+<InvokeNextExceptionFilterAsync>d__24.MoveNext (Microsoft.AspNetCore.Mvc.Core, Version=2.1.3.0, Culture=neutral, PublicKeyToken=adb9793829ddae60)
Inner exception Newtonsoft.Json.JsonReaderException handled at Microsoft.Bot.Connector.Conversations+<SendToConversationWithHttpMessagesAsync>d__7.MoveNext:
   at Newtonsoft.Json.JsonTextReader.ParseValue (Newtonsoft.Json, Version=11.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed)
   at Newtonsoft.Json.JsonTextReader.Read (Newtonsoft.Json, Version=11.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed)
   at Newtonsoft.Json.JsonReader.ReadForType (Newtonsoft.Json, Version=11.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed)
   at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize (Newtonsoft.Json, Version=11.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed)
   at Newtonsoft.Json.JsonSerializer.DeserializeInternal (Newtonsoft.Json, Version=11.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed)
   at Microsoft.Rest.Serialization.SafeJsonConvert.DeserializeObject (Microsoft.Rest.ClientRuntime, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35)

I keep getting directline errors once a while multiple times during the day....

e.g.
getaddrinfo ENOTFOUND directline.botframework.com directline.botframework.com:443

and
some errors like below
https://directline.botframework.com/v3/conversations/I02GjBASIPz4DOmNQeTxKL/activities/I02GjBASIPz4DOmNQeTxKL|0000000' failed: [503] Service Unavailable

https://directline.botframework.com/v3/conversations/6lg94qXdQbv6WOaUTf42YO/activities/6lg94qXdQbv6WOaUTf42YO|0000000' failed: [500] Internal Server Error

https://directline.botframework.com/v3/conversations/HBVeZlhbpVx1B1cjKD5QXS/activities/HBVeZlhbpVx1B1cjKD5QXS|0000000' failed: [502] Bad Gateway
Any reason why ? it stops our webchat conversation flow....

Appid: 3b2bea4a-c6ac-4e54-a926-cbee6a1c1d2a
One common thing for all errors is that activitiy id is always ending with |0000000

We are using QnA maker to expose FAQs in our bot. For cases where we don't have a very high-scoring match, we present the user with the top 5 nearest questions as buttons, so they can choose their answer (if they confirm the answer, we use that to further train the QnA model).

The issue is, the text in buttons does not wrap, it gets truncated. This means that on mobile and even sometimes on Teams desktop, the user can be confused as they don't have the full question text for each question candidate.

We have tried other options, eg (i) using adaptive cards and selectAction to make the question candidates look like links. Trouble is, they don't look like buttons so users get confused; (ii) Using a carousel with a card for each question candidate. Again, in usability testing, users got confused.

Bottom line - in this scenario where we want to user to choose from a set of FAQs, users like choosing from a vertical stack of buttons, and so we really need to be able to wrap text and show the full question.

In fact, my question would be, why do we truncate text in buttons as the default? By truncating it makes the button useless as we lose information.

This issue is to ask if we can activate text wrapping for buttons, ideally in all cards, but our immediate need is for adaptive cards.

SDK: nodejs
Channels: Teams desktop+mobile; Webchat (though we can use CSS to wrap text in that channel)

From @fj4870 on October 2, 2018 3:42

Unable to register Microsoft bot framework Email channel as getting following error "Unable to save. Unable to validate the given credentials" while saving email id and password.

I have tried using different emails including Office 365, @outlook.com etc but none of them working. Has anyone run into the same problem?

Copied from original issue: microsoft/botframework-sdk#5085

Description

Currently I am using Enterprise Bot Template v4 SDK C# for developing the bot. I am using Cosmos DB for user state management. Everything works fine with enterprise bot template , but when configure the bot on MS Teams channel , at that point of time Bot fails to write the state data to Cosmos DB and gives an error

What is actually happening..
Cosmos DB(document DB) handles every individual row/data uniquely by "id" column. Cosmos DB is having a limitation of the length of the "Id" which is 255 characters.
Now, when bot tries to store the user state for MS Teams channel in cosmos db , at that point of time Enterprise bot template/ bot framework v4 automatically creates an unique id which has length more than 255 characters. So this gives an exception in code.

Please someone look into this issue as this is a blocking issue for ms teams.

As a workaround of this issue i managed to store the state in blob storage and deployed my bot.

Exception call stack

Description

Currently I am using Enterprise Bot Template v4 SDK C# for developing the bot. I am using Cosmos DB for user state management. Everything works fine with enterprise bot template , but when configure the bot on MS Teams channel , at that point of time Bot fails to write the state data to Cosmos DB and gives an error

What is actually happening..
Cosmos DB(document DB) handles every individual row/data uniquely by "id" column. Cosmos DB is having a limitation of the length of the "Id" which is 255 characters.
Now, when bot tries to store the user state for MS Teams channel in cosmos db , at that point of time Enterprise bot template/ bot framework v4 automatically creates an unique id which has length more than 255 characters. So this gives an exception in code.

Please someone look into this issue as this is a blocking issue for ms teams.

As a workaround of this issue i managed to store the state in blob storage and deployed my bot.

Error Call Stack

Message: {"Errors":["The input name 'msteams2fconversations2fa:1de_GDChOYejATRlAuinJGMmbe2YZQ3SdEB7EPvQ_WOIUSTuU64GB5HP9BX8ol2oo1WPck-s-RpJWbMo3X9fayx-OFmyF3LnBgs7jDYj79WniZvCMqbZZy8M5RPLh2MXm2fusers2f29:1RNNKZBhoBQm0hQVbvY5NwyFWEsXABeNQUxZEHPwUYkjfn_whINgbuk6cnw21K1zFSF_ozHXBkBRJfXTLfMgbXA' is invalid. Ensure to provide a unique non-empty string less than '255' characters."]}
ActivityId: ad22f7b1-1572-406f-9440-b77f328239a0, Request URI: /apps/c8f5225c-4725-4992-9a92-6dd3f3d1510b/services/82820cba-3446-437f-8667-0a3eac3be57f/partitions/db603d54-4640-4e74-a0bc-aa19ce2198a3/replicas/131862185541974409p/, RequestStats:
RequestStartTime: 2018-11-29T12:08:33.5809299Z, Number of regions attempted: 1
, SDK: Microsoft.Azure.Documents.Common/2.1.0.0, Windows/10.0.17134 documentdb-netcore-sdk/1.9.1

Bot Info

• SDK Platform: NodeJs
• SDK Version: v3 Latest
• Active Channels: Facebook, DirectLine, WebChat
• Plan: S1 (Paid)
• Deployment Environment: Azure Bot Service
• Bot name: est1-hum-azf-bot-dev-02

Issue Description

The issue which is happening is that whenever a message is sent to the bot from Facebook messenger, it seems to be received by the Azure Function on the backend but then nothing happens. Whereas, if this is tried via Webchat or Emulator, it works fine.

It stopped responding suddenly and it was working earlier fine. Any idea what could be wrong? We haven't touched any configuration as well when it stopped responding.

Skype image attachment not working after upgrading bot framework but it is working in emulator

Below is the code we are using and this code works well earlier but after upgraded BOT version we are getting error on last line i.e. " ImageUploaded = connector.HttpClient.GetByteArrayAsync(attachment.ContentUrl).Result;"
Content URL Image not converting into byte

 using (HttpClient httpClient = new HttpClient())
  {
  // Skype & MS Teams attachment URLs are secured by a JwtToken, so we need to pass the token from our bot.
  if ((message.ChannelId.Equals("skype", StringComparison.InvariantCultureIgnoreCase) || message.ChannelId.Equals("msteams", StringComparison.InvariantCultureIgnoreCase))) //&& new Uri(attachment.ContentUrl).Host.EndsWith("skype.com")
  //if(attachment.ContentUrl.StartsWith("https:"))
  {
    var token = await new MicrosoftAppCredentials().GetTokenAsync();
    //httpClient.DefaultRequestHeaders.Authorization = new AuthenticationHeaderValue("Bearer", token);
                                
    httpClient.DefaultRequestHeaders.Authorization = new AuthenticationHeaderValue("Bearer", token);
    httpClient.DefaultRequestHeaders.Accept.Add(new MediaTypeWithQualityHeaderValue("application/octet-stream"));
  }
  else
  {
    httpClient.DefaultRequestHeaders.Accept.Add(new MediaTypeWithQualityHeaderValue(attachment.ContentType));
  }

  var responseMessage = await httpClient.GetAsync(attachment.ContentUrl);
  expense.ImageType = message.Attachments[0].ContentType;
  var connector = new ConnectorClient(new Uri(message.ServiceUrl));
  expense.ImageContentURL = attachment.ContentUrl;

                        
  ImageUploaded = connector.HttpClient.GetByteArrayAsync(attachment.ContentUrl).Result;
}

Running v4 node.js bot, we have deployed to a teams channel. If a user starts a new private direct chat with the bot (ie "Message bot"), everything works really well, things are stable.

However, if the user starts a chat with the bot in a team by using the handle (eg @otto), it starts a thread, and works well for 2 interactions, then becomes unresponsive.

So for example:

1. User goes to the group with the chatbot
2. User types "@otto hi"
3. New thread is started in the Teams window, bot responds
4. In the "Reply" on the thread, user asks an FAQ question
5. Bot responds
6. User types another question, nothing happens. Bot logs show no traffic

Looking at the teams UI (see attached), it seems that when the user enters something, the input is automatically prefixed with the bot handle @otto the first time, but after that this doesn't happen, so the input is ignored and the user thinks the bot has frozen.

If in a 'Reply' thread with the chatbot, the user should not have to remember to prefix all replies with the handle, from a user's perspective they are already chatting with the bot. This issue hit every single one of our users, who thought the bot had 'frozen'.

How can we resolve this please, makes using the bot in teams difficult?

Is there any chance WhatsApp channel being implemented in bot framework since WhatsApp announced API?

Can we get Webex Teams Channel anytime soon?

Version

v4.1.5

Describe the bug

When using SuggestedActions as below, there is differing behaviour between the emulator/web chat and facebook messenger.

var opts = new PromptOptions
{
    Prompt = new Activity
    {
        Type = ActivityTypes.Message,
        Text = "Choose from one of the following options",
        TextFormat = TextFormatTypes.Plain,
        SuggestedActions = new SuggestedActions
        {
            Actions = new List<CardAction>
            {
                new CardAction
                {
                    Type = ActionTypes.PostBack,
                    Title = "Really really long button title",
                    Value = "Value1"
                },
                new CardAction
                {
                    Type = ActionTypes.PostBack,
                    Title = "Extra extra long button title",
                    Value = "Value2"
                }
            }
        }
    }
};

return await stepContext.PromptAsync(ButtonOptionPrompt, opts, cancellationToken);

I've written a small test app which replies back to the user with the value of the suggested action selected. When using the emulator or the test web client, the value is returned correctly. When using Facebook Messenger, the Title is returned as in the screenshots below. Added to this, only the title with the ellipsis is returned.

private static async Task<bool> ValidateButtonAsync(PromptValidatorContext<string> promptContext, CancellationToken cancellationToken)
{
    await promptContext.Context.SendActivityAsync($"The value of the button you selected is: {promptContext.Recognized.Value}", cancellationToken: cancellationToken);

    return true;
}

Expected behaviour

Facebook messenger should return the Value of the card action back to the bot framework.

Screenshots

Web Chat

Facebook Messenger

cc @darrenj @suneetnangia

[bug]

In Cortana Bot Skills, the current timeout of a cortana skill waiting for the bot's response is 10 seconds.

We are integrating automation tools like ServiceNow for ticket creation based on user's query in the bot where the ticket creation takes a minute and return back for the bot to respond the user about the ticket details.

Is there any way to increase this timeout value? Is this configurable? Need help on this.

Thanks in Advance.

If no, is there please suggest recommended workaround. I read through related issues which were closed since V4 came out. However, I don't see any recommended solution which can work at scale.

At the moment it is very unclear what the possibilities of Teams bots are and how you can sideload a bot. Without uploading the app package (manifest), not all Teams specific functionality is supported. However functionality like OAuthCards and File Uploads is also unsupported, which is unclear for developers at the moment.

When a bot has been added through one of these methods, it will not be addressable in channel conversations. Nor can you take advantage of other Microsoft Teams app capabilities like tabs or messaging extensions. (source)

Is your feature request related to a problem? Please describe.:

• Channel Registration page is not detailed enough
• Messaging - Learn more points to https://dev.skype.com/bots instead of Teams documentation

Describe the solution you'd like:

• Add more information about packaging a bot for testing purposes (not only publishing)
• Add links to Teams specific documentation
• Change Skype link to Teams specific documentation

Related:
https://github.com/Microsoft/AI/pull/410
microsoft/BotFramework-WebChat#1667

Versions

Not an SDK issue. This bug relates to Azure.

Describe the bug

In the Azure web portal, when you attempt to search for resources using the search term "bot", it's very unclear to average developers which of the results to choose. Not only are there WebApp bots and registration bots, but there are a lot of other resource types mixed in there.

To Reproduce

Steps to reproduce the behavior:

1. Go to the Azure web portal
2. Create a new resource
3. Search for "bot"
4. Trouble yourself over which resource type to choose.

Expected behavior

A clearer, more concise list of resource types.

Screenshots

If applicable, add screenshots to help explain your problem.

Additional context

Add any other context about the problem here.

[bug]

We have recently enabled Traffic Manager to sit between the Azure Bot Service channel registration and our bot. When we did this, our web chat component immediately starts failing. I believe we are seeing Authentication Exceptions in the process. The exact message is: "POST to xxxxxxx failed: Bad certificate Bad certificate The remote certificate is invalid according to the validation procedure.". And it seems the bad cert exception is occurring when we hit the traffic manager. Any ideas on how we can fix this?

Bot Info

• SDK Platform: .NET
• SDK Version: 3.15.2.2
• Active Channels: Web Chat
• Deployment Environment: Azure Bot Service, Azure App Service, local development with Emulator

Issue Description

When running the sample code for Oath login https://github.com/Microsoft/BotBuilder/tree/master/CSharp/Samples/AadV2Bot the bot is able to render a sign card in the emulator but not in web chat. Running the web chat in Edge or Chrome renders the following when sign in is requested "[File of type 'application/vnd.microsoft.card.oauth']"

Code Example

https://github.com/Microsoft/BotBuilder/tree/master/CSharp/Samples/AadV2Bot

Reproduction Steps

1. Deploy https://github.com/Microsoft/BotBuilder/tree/master/CSharp/Samples/AadV2Bot on Azure
2. Enable Web Chat Channel
3. Enter in "me" command

Expected Behavior

Expect to see the Sign in card which allows a user to authenticate against the graph API

Actual Results

Since the card is rendered an attachment the browser (Edge, Chrome) display "[File of type 'application/vnd.microsoft.card.oauth']" . In the emulator it works as intended.

When building carousels in the Bot Builder SDK there is no native support for implementing Facebook Messenger Webviews through the use of messenger_extensions.

If order to create a button that makes use of the Facebook web view feature we have to start using anonymous objects, such as:

var attachment = new
{
    type = "template",
    payload = new
    {
        template_type = "button",
        text = "Your 🍕 is on it's way!",
        buttons = new[]
        {
            new
            {
                type = "web_url",
                url = "https://www.somedomain/url",
                title = "👁️ View Details",
                webview_height_ratio = "compact",
                messenger_extensions = true,
            },
        },
    },
};

When building a message like this is stops working on all over channels making local development and testing impossible without branching the logic based on the channel. This pretty much removes any benefit of having a channel agnostic approach to thins.

Whereas a carousel that works on all channels is created like this:

List<Attachment> props = new List<Attachment>();
foreach (var responseProperty in response.Listing)
{
    var cardAttachement = new HeroCard(
        responseProperty.DisplayableAddress,
        responseProperty.Price.ToDisplayPrice(),
        images: new CardImage[]
        {
            new CardImage(url: imageurl)
        },
        buttons: new CardAction[]
        {
            new CardAction(ActionTypes.OpenUrl, "👁️ View Details", value: $"https://www.somedomain/url"),
            new CardAction(ActionTypes.Call, "📲 Call Us", value: "tel:+4434524527"),
            new CardAction(ActionTypes.PostBack, "📅 Arrange Viewing", value: $""),
        }).ToAttachment();

    props.Add(cardAttachement);
}

var activity = MessageFactory.Carousel(props);

But this doesn't support (as far as I can tell) making use of Facebook messenger extensions.

Describe the solution you'd like
I would like to continue to use the built in support for carousels with the ability to create buttons that do support messenger extensions. This way we do not have to branch the logic and we have access to the full spectrum of features available via the messenger channel whilst maintaining operability with the other channels and most importantly local development testing with the Bot Framework emulator.

[enhancement]

Hi, the @AzureSupport twitter account (signed by RS) told me to create an issue here.

The documentation says:

Any response that specifies an HTTP status code in the 4xx range or 5xx range will include an ErrorResponse object in the body of the response

I set up a Skype For Business account and my endpoint is now receiving messages. When I try to respond a message, I'm getting a HTTP 400 error for some reason. The body of the answer should clarify what I'm doing wrong, but instead I get this:

<html>
    <head>
        <title>Runtime Error</title>
        <meta name="viewport" content="width=device-width" />
        <style>
         body {font-family:"Verdana";font-weight:normal;font-size: .7em;color:black;} 
         p {font-family:"Verdana";font-weight:normal;color:black;margin-top: -5px}
         b {font-family:"Verdana";font-weight:bold;color:black;margin-top: -5px}
         H1 { font-family:"Verdana";font-weight:normal;font-size:18pt;color:red }
         H2 { font-family:"Verdana";font-weight:normal;font-size:14pt;color:maroon }
         pre {font-family:"Consolas","Lucida Console",Monospace;font-size:11pt;margin:0;padding:0.5em;line-height:14pt}
         .marker {font-weight: bold; color: black;text-decoration: none;}
         .version {color: gray;}
         .error {margin-bottom: 10px;}
         .expandable { text-decoration:underline; font-weight:bold; color:navy; cursor:hand; }
         @media screen and (max-width: 639px) {
          pre { width: 440px; overflow: auto; white-space: pre-wrap; word-wrap: break-word; }
         }
         @media screen and (max-width: 479px) {
          pre { width: 280px; }
         }
        </style>
    </head>

    <body bgcolor="white">

            <span><H1>Server Error in '/PlatformService' Application.<hr width=100% size=1 color=silver></H1>

            <h2> <i>Runtime Error</i> </h2></span>

            <font face="Arial, Helvetica, Geneva, SunSans-Regular, sans-serif ">

            <b> Description: </b>An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
            <br><br>

            <b>Details:</b> To enable the details of this specific error message to be viewable on remote machines, please create a &lt;customErrors&gt; tag within a &quot;web.config&quot; configuration file located in the root directory of the current web application. This &lt;customErrors&gt; tag should then have its &quot;mode&quot; attribute set to &quot;Off&quot;.<br><br>

            <table width=100% bgcolor="#ffffcc">
               <tr>
                  <td>
                      <code><pre>

&lt;!-- Web.Config Configuration File --&gt;

&lt;configuration&gt;
    &lt;system.web&gt;
        &lt;customErrors mode=&quot;Off&quot;/&gt;
    &lt;/system.web&gt;
&lt;/configuration&gt;</pre></code>

                  </td>
               </tr>
            </table>

            <br>

            <b>Notes:</b> The current error page you are seeing can be replaced by a custom error page by modifying the &quot;defaultRedirect&quot; attribute of the application&#39;s &lt;customErrors&gt; configuration tag to point to a custom error page URL.<br><br>

            <table width=100% bgcolor="#ffffcc">
               <tr>
                  <td>
                      <code><pre>

&lt;!-- Web.Config Configuration File --&gt;

&lt;configuration&gt;
    &lt;system.web&gt;
        &lt;customErrors mode=&quot;RemoteOnly&quot; defaultRedirect=&quot;mycustompage.htm&quot;/&gt;
    &lt;/system.web&gt;
&lt;/configuration&gt;</pre></code>

                  </td>
               </tr>
            </table>

            <br>

    </body>
</html>

Not very helpful I'd say.

The issue is, we have a working integration with Webchat and Skype, and they are working correctly. Actually the code for Skype and Skype For Business is 100% the same. I believe this should work. We're using Directline API 3.

Soon I'll be able to get the actual HTTP payload I'm sending, we're also in the process of debugging this. I'll also share my token with the person on Twitter.

I know current version does not support cards. Is there a workaround?

Encounter some bug on facebook channel with multiple pageId add/remove:

Scenario:

1. I had only one pageId on Facebook channel.
2. Then added another new pageId into channel.
3. Remove this new added pageId from Facebook channel, and restart the bot it will hit:

BotFrameworkAdapter.processActivity(): 500 ERROR - Error: The bot referenced by the 'from' field is unrecognized
(node:16644) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 3): Error: The bot referenced by the 'from' field is unrecognized
(node:16644) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

If I added back the remove pageId back everything works normally.
Is this a bug on bot adapter? I'm using v4 botbuilder@preview package.

Operation returned an invalid status code 'BadRequest'

Version

4.1.5

Describe the bug

exceptionMessage": "Operation returned an invalid status code 'BadRequest'",
"stackTrace": " at Microsoft.Bot.Connector.Conversations.ReplyToActivityWithHttpMessagesAsync(String conversationId, String activityId, Activity activity, Dictionary`2 customHeaders, CancellationToken cancellationToken)
at Microsoft.Bot.Connector.ConversationsExtensions.ReplyToActivityAsync(IConversations operations, String conversationId, String activityId, Activity activity, CancellationToken cancellationToken)
at Microsoft.Bot.Builder.BotFrameworkAdapter.SendActivitiesAsync(ITurnContext turnContext, Activity[] activities, CancellationToken cancellationToken)
at Microsoft.Bot.Builder.TurnContext.<>c__DisplayClass22_0.<g__SendActivitiesThroughAdapter|1>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---

To Reproduce

var activity = ChoiceFactory.SuggestedAction(options.Choices, options.Prompt.Text, options.Prompt.Speak);
await turnContext.SendActivityAsync(activity, cancellationToken);

Expected behavior

Should not throw.

Additional context

This only happens sometimes on facebook channel, I cannot reproduce it in a stable manner.

[bug]

I believe a similar issue happens to Cortana channel as well sometimes.

I keep getting directline errors once a while multiple times during the day....

e.g.
getaddrinfo ENOTFOUND directline.botframework.com directline.botframework.com:443

and
some errors like below
https://directline.botframework.com/v3/conversations/I02GjBASIPz4DOmNQeTxKL/activities/I02GjBASIPz4DOmNQeTxKL|0000000' failed: [503] Service Unavailable

https://directline.botframework.com/v3/conversations/6lg94qXdQbv6WOaUTf42YO/activities/6lg94qXdQbv6WOaUTf42YO|0000000' failed: [500] Internal Server Error

https://directline.botframework.com/v3/conversations/HBVeZlhbpVx1B1cjKD5QXS/activities/HBVeZlhbpVx1B1cjKD5QXS|0000000' failed: [502] Bad Gateway
Any reason why ? it stops our webchat conversation flow....

Appid: 3b2bea4a-c6ac-4e54-a926-cbee6a1c1d2a

One common thing for all errors is that activitiy id is always ending with |0000000

Bot Info

• SDK Platform: Node.js
• Active Channels: Skype
• Deployment Environment: Azure Bot Service - portal.azure.com

Issue Description

Cant change the settings endpoint, error received:

{"readyState":4,"responseText":"{"error":{"code":"InvalidBotData","message":"OwnerIds: OwnerIds must contain at least one email address. "}}","responseJSON":{"error":{"code":"InvalidBotData","message":"OwnerIds: OwnerIds must contain at least one email address. "}},"status":400,"statusText":"Bad Request"}

Reproduction Steps

1. Login to - https://portal.azure.com
2. Go to the resource - bot
3. Settings tab
4. Change Configuration Messaging endpoint
5. Save

Expected Behavior

Messaging endpoint save successfully.

Actual Results

Nothing happened.

Bot handle is "AstridBot"
appId is c77c3dd6-7278-4f4b-92fc-f3642cb7f29c

From @patrickianco on October 25, 2018 3:54

Copied from original issue: microsoft/botframework-sdk#5118

Hello,
Does Directline support two people chatting with a bot in the middle to facilitate the conversation?

We have a working integration with Skype and directline.

However, I created a new bot today and now I'm getting this:

{"error":{"code":"BadArgument","message":"Failed to decrypt conversation id"}}

Other bots are working as normal. What does this error mean?

If I change the Messaging endpoint to a different one outside the domain azurewebsites, the application settings could not longer being accessed:

How do we send a "stop typing" activity?
If it is not possible, what will it take to make it possible?

This is particularly necessary when the framework is being used for live agent escalation.

I don't know if this should be posted under this repository or BotBuilder but I suspect it's a directline issue.

I use the SendConversationHistoryAsync method of the BotBuilder to load the previous user conversation history into a webchat control (thus using directline). No problems occur unless the activity contains an attachment (a HeroCard for example). If so, the C# code crashes with an InternalServerError exception.

In addition, if I use the SendActivityAsync method, the activity is sent just fine over to the webchat.

Here's why I'm doing: I'm developing a web backend for the bot, within it a webchat control allows the admin to view a previous conversation. Therefore i'm sending the channelId and the conversationIdentifier in the channelData within the conversationUpdate event. When received, I'll do the following to send the history:

var connectorClient = turnContext.TurnState.Get<ConnectorClient>(typeof(IConnectorClient).FullName);
var pagedTranscript = await TranscriptStore.GetTranscriptActivitiesAsync(channelId, conversationIdentifier);
var activities = pagedTranscript.Items.Where(a => a.Type == ActivityTypes.Message).Select(ia => (Activity)ia).ToList();
foreach (var activity in activities)
{
    // I'm changing this because I'm sending the history of another conversation to this one
    activity.Conversation = turnContext.Activity.Conversation;
    // Removing the attachments here allows the activity to be received, if it has any attachments, the code crashes after a period of time and the activity isn't sent
    // PROBLEM HERE
    activity.Attachments = null;
}
var transcript = new Microsoft.Bot.Schema.Transcript(activities);
//await turnContext.SendActivitiesAsync(activities.ToArray());
var response = await connectorClient.Conversations.SendConversationHistoryWithHttpMessagesAsync(turnContext.Activity.Conversation.Id, transcript, cancellationToken: cancellationToken);

Any help would be appreciated. Thank you.

Hi,

Around 3:30 PM EST today, we notice that directline.botframework.com SSL/TLS handshake failed.
I don't see any status issue at https://azure.microsoft.com/en-us/status/ on Azure Bot.

Could someone from Microsoft please comment what is going on?
Please also note that the issue appears to occur on our servers in US-EAST and US-Central, not US-WEST.

Below is the curl output in US-EAST.

curl -v https://directline.botframework.com
* Rebuilt URL to: https://directline.botframework.com/
*   Trying 40.121.91.199...
* Connected to directline.botframework.com (40.121.91.199) port 443 (#0)
* Server aborted the SSL handshake
* Closing connection 0
curl: (35) Server aborted the SSL handshake`

Appear to be okay in US-WEST.

curl -v https://directline.botframework.com
* Rebuilt URL to: https://directline.botframework.com/
*   Trying 40.121.91.199...
* Connected to directline.botframework.com (40.121.91.199) port 443 (#0)
* TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
* Server certificate: *.botframework.com
* Server certificate: Microsoft IT TLS CA 2
* Server certificate: Baltimore CyberTrust Root
> GET / HTTP/1.1
> Host: directline.botframework.com
> User-Agent: curl/7.43.0
> Accept: */*
> 
< HTTP/1.1 302 Found
< Cache-Control: private
< Content-Length: 146
< Content-Type: text/html; charset=utf-8
< Location: https://dev.botframework.com/
< Server: Microsoft-IIS/10.0
< X-AspNetMvc-Version: 5.2
< Strict-Transport-Security: max-age=31536000
< Date: Fri, 02 Nov 2018 00:58:02 GMT
...
..
.

The blade options in Azure are different when working with a Bot Channel Registration vs a Web App Bot. For example you can quickly & easily get to the application settings in the latter while it doesn't exist in the former. It's not apparent to end users that a Web App Bot spins up two separate entities in Azure and then provides a "lens" over them both (hence the App Settings being available here).

I have a bot already implemented and deployed in skype for business, the bot works OK but the status in Skype for business is "unkown" , how to make it available ?

Adding support for these methods in WebChat will bring support for these methods to the emulator, which is important to allow developers to truly test their applications which may rely on these methods!

According to @compulim this would involve a few lines here:

https://github.com/Microsoft/BotFramework-WebChat/blob/master/packages/core/src/reducers/activities.js#L83

I'm using version 3.19.1.44133, which works fine with Skype and Web Chat. I just created a bot on Telegram and I'm getting an HTTP 500 status error. It appears to be a 'NotFound' error from the Microsoft.Bot.Connector? Here is the detailed error message:

[{"parsedStack":[{"assembly":"Microsoft.Bot.Connector, Version=3.19.1.44133, Culture=neutral, PublicKeyToken=31bf3856ad364e35","method":"Microsoft.Bot.Connector.Conversations+d__10.MoveNext","level":0,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess","level":1,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification","level":2,"line":0},{"assembly":"Microsoft.Bot.Connector, Version=3.19.1.44133, Culture=neutral, PublicKeyToken=31bf3856ad364e35","method":"Microsoft.Bot.Connector.ConversationsExtensions+d__11.MoveNext","level":3,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess","level":4,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification","level":5,"line":0},{"assembly":"Microsoft.Bot.Builder, Version=3.19.1.44133, Culture=neutral, PublicKeyToken=31bf3856ad364e35","method":"Microsoft.Bot.Builder.Dialogs.Internals.AlwaysSendDirect_BotToUser+d__4.MoveNext","level":6,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess","level":7,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification","level":8,"line":0},{"assembly":"Microsoft.Bot.Builder, Version=3.19.1.44133, Culture=neutral, PublicKeyToken=31bf3856ad364e35","method":"Microsoft.Bot.Builder.Dialogs.Internals.InputHintQueue+d__4.MoveNext","level":9,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess","level":10,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification","level":11,"line":0},{"assembly":"Microsoft.Bot.Builder, Version=3.19.1.44133, Culture=neutral, PublicKeyToken=31bf3856ad364e35","method":"Microsoft.Bot.Builder.Dialogs.Internals.AutoInputHint_BotToUser+d__3.MoveNext","level":12,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess","level":13,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification","level":14,"line":0},{"assembly":"Microsoft.Bot.Builder, Version=3.19.1.44133, Culture=neutral, PublicKeyToken=31bf3856ad364e35","method":"Microsoft.Bot.Builder.Dialogs.Internals.MapToChannelData_BotToUser+d__3.MoveNext","level":15,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess","level":16,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification","level":17,"line":0},{"assembly":"Microsoft.Bot.Builder, Version=3.19.1.44133, Culture=neutral, PublicKeyToken=31bf3856ad364e35","method":"Microsoft.Bot.Builder.Dialogs.Internals.LogBotToUser+d__4.MoveNext","level":18,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess","level":19,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification","level":20,"line":0},{"assembly":"Microsoft.Bot.Builder, Version=3.19.1.44133, Culture=neutral, PublicKeyToken=31bf3856ad364e35","method":"Microsoft.Bot.Builder.Dialogs.Internals.DialogContext+d__12.MoveNext","level":21,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess","level":22,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification","level":23,"line":0},{"assembly":"Microsoft.Bot.Builder, Version=3.19.1.44133, Culture=neutral, PublicKeyToken=31bf3856ad364e35","method":"Microsoft.Bot.Builder.Dialogs.Extensions+d__14.MoveNext","level":24,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess","level":25,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification","level":26,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd","level":27,"line":0},{"assembly":"Bot Application1, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null","method":"RiBot.MessagesController+RiDialog+d__1.MoveNext","level":28,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess","level":29,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification","level":30,"line":0},{"assembly":"Microsoft.Bot.Builder, Version=3.19.1.44133, Culture=neutral, PublicKeyToken=31bf3856ad364e35","method":"Microsoft.Bot.Builder.Dialogs.Internals.DialogTask+ThunkResume1+<Rest>d__5.MoveNext","level":31,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess","level":32,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification","level":33,"line":0},{"assembly":"Microsoft.Bot.Builder, Version=3.19.1.44133, Culture=neutral, PublicKeyToken=31bf3856ad364e35","method":"Microsoft.Bot.Builder.Internals.Fibers.Wait2+<Microsoft-Bot-Builder-Internals-Fibers-IWait-PollAsync>d__19.MoveNext","level":34,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess","level":35,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification","level":36,"line":0},{"assembly":"Microsoft.Bot.Builder, Version=3.19.1.44133, Culture=neutral, PublicKeyToken=31bf3856ad364e35","method":"Microsoft.Bot.Builder.Internals.Fibers.Frame1+<Microsoft-Bot-Builder-Internals-Fibers-IFrameLoop<C>-PollAsync>d__9.MoveNext","level":37,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess","level":38,"line":0},{"assembly":"Microsoft.Bot.Builder, Version=3.19.1.44133, Culture=neutral, PublicKeyToken=31bf3856ad364e35","method":"Microsoft.Bot.Builder.Internals.Fibers.Fiber1+<Microsoft-Bot-Builder-Internals-Fibers-IFiberLoop-PollAsync>d__16.MoveNext","level":39,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw","level":40,"line":0},{"assembly":"Microsoft.Bot.Builder, Version=3.19.1.44133, Culture=neutral, PublicKeyToken=31bf3856ad364e35","method":"Microsoft.Bot.Builder.Internals.Fibers.Wait2.Microsoft.Bot.Builder.Internals.Fibers.IAwaiter<T>.GetResult","level":41,"line":0},{"assembly":"Microsoft.Bot.Builder, Version=3.19.1.44133, Culture=neutral, PublicKeyToken=31bf3856ad364e35","method":"Microsoft.Bot.Builder.Dialogs.Chain+LoopDialog1+d__3.MoveNext","level":42,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess","level":43,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification","level":44,"line":0},{"assembly":"Microsoft.Bot.Builder, Version=3.19.1.44133, Culture=neutral, PublicKeyToken=31bf3856ad364e35","method":"Microsoft.Bot.Builder.Dialogs.Internals.DialogTask+ThunkResume1+<Rest>d__5.MoveNext","level":45,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess","level":46,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification","level":47,"line":0},{"assembly":"Microsoft.Bot.Builder, Version=3.19.1.44133, Culture=neutral, PublicKeyToken=31bf3856ad364e35","method":"Microsoft.Bot.Builder.Internals.Fibers.Wait2+<Microsoft-Bot-Builder-Internals-Fibers-IWait-PollAsync>d__19.MoveNext","level":48,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess","level":49,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification","level":50,"line":0},{"assembly":"Microsoft.Bot.Builder, Version=3.19.1.44133, Culture=neutral, PublicKeyToken=31bf3856ad364e35","method":"Microsoft.Bot.Builder.Internals.Fibers.Frame1+<Microsoft-Bot-Builder-Internals-Fibers-IFrameLoop<C>-PollAsync>d__9.MoveNext","level":51,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess","level":52,"line":0},{"assembly":"Microsoft.Bot.Builder, Version=3.19.1.44133, Culture=neutral, PublicKeyToken=31bf3856ad364e35","method":"Microsoft.Bot.Builder.Internals.Fibers.Fiber1+<Microsoft-Bot-Builder-Internals-Fibers-IFiberLoop-PollAsync>d__16.MoveNext","level":53,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess","level":54,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification","level":55,"line":0},{"assembly":"Microsoft.Bot.Builder, Version=3.19.1.44133, Culture=neutral, PublicKeyToken=31bf3856ad364e35","method":"Microsoft.Bot.Builder.Dialogs.Internals.DialogTask+d__23.MoveNext","level":56,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess","level":57,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification","level":58,"line":0},{"assembly":"Microsoft.Bot.Builder, Version=3.19.1.44133, Culture=neutral, PublicKeyToken=31bf3856ad364e35","method":"Microsoft.Bot.Builder.Dialogs.Internals.ReactiveDialogTask+d__3.MoveNext","level":59,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess","level":60,"line":0},{"assembly":"Microsoft.Bot.Builder, Version=3.19.1.44133, Culture=neutral, PublicKeyToken=31bf3856ad364e35","method":"Microsoft.Bot.Builder.Dialogs.Internals.ScoringEventLoop1+<Microsoft-Bot-Builder-Base-IEventLoop-PollAsync>d__5.MoveNext","level":61,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess","level":62,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification","level":63,"line":0},{"assembly":"Microsoft.Bot.Builder, Version=3.19.1.44133, Culture=neutral, PublicKeyToken=31bf3856ad364e35","method":"Microsoft.Bot.Builder.Dialogs.Internals.EventLoopDialogTask+<Microsoft-Bot-Builder-Dialogs-Internals-IPostToBot-PostAsync>d__3.MoveNext","level":64,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess","level":65,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification","level":66,"line":0},{"assembly":"Microsoft.Bot.Builder, Version=3.19.1.44133, Culture=neutral, PublicKeyToken=31bf3856ad364e35","method":"Microsoft.Bot.Builder.Dialogs.Internals.SetAmbientThreadCulture+<Microsoft-Bot-Builder-Dialogs-Internals-IPostToBot-PostAsync>d__3.MoveNext","level":67,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess","level":68,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification","level":69,"line":0},{"assembly":"Microsoft.Bot.Builder, Version=3.19.1.44133, Culture=neutral, PublicKeyToken=31bf3856ad364e35","method":"Microsoft.Bot.Builder.Dialogs.Internals.QueueDrainingDialogTask+<Microsoft-Bot-Builder-Dialogs-Internals-IPostToBot-PostAsync>d__4.MoveNext","level":70,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess","level":71,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification","level":72,"line":0},{"assembly":"Microsoft.Bot.Builder, Version=3.19.1.44133, Culture=neutral, PublicKeyToken=31bf3856ad364e35","method":"Microsoft.Bot.Builder.Dialogs.Internals.PersistentDialogTask+<Microsoft-Bot-Builder-Dialogs-Internals-IPostToBot-PostAsync>d__3.MoveNext","level":73,"line":0},{"assembly":"Microsoft.Bot.Builder, Version=3.19.1.44133, Culture=neutral, PublicKeyToken=31bf3856ad364e35","method":"Microsoft.Bot.Builder.Dialogs.Internals.PersistentDialogTask+<Microsoft-Bot-Builder-Dialogs-Internals-IPostToBot-PostAsync>d__3.MoveNext","level":74,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess","level":75,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification","level":76,"line":0},{"assembly":"Microsoft.Bot.Builder, Version=3.19.1.44133, Culture=neutral, PublicKeyToken=31bf3856ad364e35","method":"Microsoft.Bot.Builder.Dialogs.Internals.ExceptionTranslationDialogTask+<Microsoft-Bot-Builder-Dialogs-Internals-IPostToBot-PostAsync>d__2.MoveNext","level":77,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess","level":78,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification","level":79,"line":0},{"assembly":"Microsoft.Bot.Builder, Version=3.19.1.44133, Culture=neutral, PublicKeyToken=31bf3856ad364e35","method":"Microsoft.Bot.Builder.Dialogs.Internals.SerializeByConversation+<Microsoft-Bot-Builder-Dialogs-Internals-IPostToBot-PostAsync>d__4.MoveNext","level":80,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess","level":81,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification","level":82,"line":0},{"assembly":"Bot Application1, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null","method":"RiBot.ErrorHandling.PostUnhandledExceptionToUserOverrideTask+<PostAsync>d__5.MoveNext","level":83,"line":0},{"assembly":"Bot Application1, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null","method":"RiBot.ErrorHandling.PostUnhandledExceptionToUserOverrideTask+<PostAsync>d__5.MoveNext","level":84,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess","level":85,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification","level":86,"line":0},{"assembly":"Microsoft.Bot.Builder, Version=3.19.1.44133, Culture=neutral, PublicKeyToken=31bf3856ad364e35","method":"Microsoft.Bot.Builder.Dialogs.Internals.LogPostToBot+<Microsoft-Bot-Builder-Dialogs-Internals-IPostToBot-PostAsync>d__3.MoveNext","level":87,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess","level":88,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification","level":89,"line":0},{"assembly":"Microsoft.Bot.Builder.Autofac, Version=3.19.1.44133, Culture=neutral, PublicKeyToken=31bf3856ad364e35","method":"Microsoft.Bot.Builder.Dialogs.Conversation+<SendAsync>d__11.MoveNext","level":90,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess","level":91,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification","level":92,"line":0},{"assembly":"Microsoft.Bot.Builder.Autofac, Version=3.19.1.44133, Culture=neutral, PublicKeyToken=31bf3856ad364e35","method":"Microsoft.Bot.Builder.Dialogs.Conversation+<SendAsync>d__6.MoveNext","level":93,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess","level":94,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification","level":95,"line":0},{"assembly":"Bot Application1, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null","method":"RiBot.MessagesController+<Post>d__3.MoveNext","level":96,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess","level":97,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification","level":98,"line":0},{"assembly":"System.Web.Http, Version=5.2.3.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35","method":"System.Threading.Tasks.TaskHelpersExtensions+<CastToObject>d__31.MoveNext","level":99,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess","level":100,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification","level":101,"line":0},{"assembly":"System.Web.Http, Version=5.2.3.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35","method":"System.Web.Http.Controllers.ApiControllerActionInvoker+d__0.MoveNext","level":102,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess","level":103,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification","level":104,"line":0},{"assembly":"System.Web.Http, Version=5.2.3.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35","method":"System.Web.Http.Filters.ActionFilterAttribute+d__5.MoveNext","level":105,"line":0},{"assembly":"System.Web.Http, Version=5.2.3.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35","method":"System.Web.Http.Filters.ActionFilterAttribute+d__5.MoveNext","level":106,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess","level":107,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification","level":108,"line":0},{"assembly":"System.Web.Http, Version=5.2.3.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35","method":"System.Web.Http.Filters.ActionFilterAttribute+d__0.MoveNext","level":109,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess","level":110,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification","level":111,"line":0},{"assembly":"System.Web.Http, Version=5.2.3.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35","method":"System.Web.Http.Controllers.ActionFilterResult+d__2.MoveNext","level":112,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess","level":113,"line":0},{"assembly":"mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification","level":114,"line":0},{"assembly":"System.Web.Http, Version=5.2.3.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35","method":"System.Web.Http.Dispatcher.HttpControllerDispatcher+d__1.MoveNext","level":115,"line":0}],"outerId":"0","message":"Operation returned an invalid status code 'NotFound'","type":"Microsoft.Bot.Connector.ErrorResponseException","id":"36241063"}]

Whenever I try to change any settings for Facebook Channel, I get the following error

Unable to save. Failed to validate Facebook credentials: [190 This Page access token belongs to a Page that is not accessible.] ID: |RAdKS.fzWAE.2e4645aa_

We are facing the above issue all of a sudden from today morning. Our bot is working fine for the past one year and from today we are getting this error. "This Page access token belongs to a Page that is not accessible"

From @patrickianco on October 25, 2018 3:54

Copied from original issue: microsoft/botframework-sdk#5118

I created a bot that uses the suggested actions functionality. It works as expected in the emulator and in web chat. In Teams the suggested actions do not show up. I deployed the suggested actions sample bot and observed the same behaviour.

Hi,

I created multiple bot channel registration resources and only one Application Insights resource for analytics. When I create an AppInsights API key and configure it for all the bot channel registrations. I see the data across all the bot resources. It seems like when analytics reads the data it doesn't filter it out by the BotId and hence displays me the same data for all the bot channel resources.

If you create a Bot Channels Registration resource through the Azure portal and leave the default of "Auto create App ID and password", it never shows you the generated ID and password. You can find the ID under Settings -> Microsoft App ID, but to get a password, you have to go into the app registration and regenerate a new password. This is a confusing experience.

We have added Skype for Business as new channel for our bot and somehow it is not displaying the hero card. Same hero card works in MS teams channel. We tried to change hero card to thumbnail card as well, but still no luck.

Not unlike this issue, I created a bot with Twilio and never got the greeting from my bot (which should happen at Conversation Update).

While I understand why this isn't possible in the traditional sense, I thinks it's reasonable to expect the bot fire conversationUpdate on the first message it sees from a user (like Webchat today).