Ram

@emiledufour, Looks like I was not able to repro from my end. #### Environment * azure-cli 2.39.0 * core 2.39.0 * OS: Windows 11 * Windows Terminal: Powershell # After...

investigating

Hey @JuanAr I'm able to reproduce this issue where if we call the method `TeamsInfo.GetMemberAsync(...)` from the Root bot to EchoSkillBot. It throws `The skill encountered an error or bug.`...

Hi @JuanAr. Same behavior occurs for C# sample [80.skills-simple-bot-to-bot](https://github.com/microsoft/BotBuilder-Samples/tree/main/samples/csharp_dotnetcore/80.skills-simple-bot-to-bot) as well. The below code **only** resolves for DotNet C# sample. In RootBot.cs file, update the `SendToSkill` method with the following...

Perhaps translating the above code to Javascript might fix JS sample [80.skills-simple-bot-to-bot](https://github.com/microsoft/BotBuilder-Samples/tree/main/samples/javascript_nodejs/80.skills-simple-bot-to-bot) in respect with Alexa channel?

Hi @erquirogasw, Looks like the skill is still not working in Alexa channel using [SimpleHostBot](https://github.com/microsoft/BotFramework-FunctionalTests/tree/main/Bots/JavaScript/SimpleHostBot) as rootbot and [EchoSkillBot](https://github.com/microsoft/BotFramework-FunctionalTests/tree/main/Bots/JavaScript/EchoSkillBot) as skill bot. Also, in Alexa, I noticed the suggestion choices...

Hi @erquirogasw, Thank you so much. Indeed I made code changes I did not realize. Shame on me. Using a fresh [SimpleHostBot](https://github.com/microsoft/BotFramework-FunctionalTests/tree/main/Bots/JavaScript/SimpleHostBot) as rootbot and [EchoSkillBot](https://github.com/microsoft/BotFramework-FunctionalTests/tree/main/Bots/JavaScript/EchoSkillBot) as skill bot works...

Thanks, @johnmiroki, I'm investigating this.

Hi @johnmiroki, Thanks for raising this issue, I was able to repro. Looks like when sending [People Picker](https://docs.microsoft.com/en-us/microsoftteams/platform/task-modules-and-cards/cards/people-picker?tabs=desktop) in Adaptive Cards, the following error message is thrown: ``` [INFO ]...

Thank you @johnmiroki, we are working on this fix for the next patch release.