Mat Stankiewicz
Mat Stankiewicz
Please review this if you folks have a chance: https://github.com/Microsoft/BotFramework-Hubot/pull/44
Hi, could you try setting this environment variable before you launch your bot and see if you get any additional error messages? NODE_DEBUG=botbuilder
No, you are definitely receiving the message and sending it back so it doesn't look like that is an issue. I recently ran and setup a new hubot with my...
Did you pull the hubot-botframework adapter from NPM? These changes shouldn't be in the latest version 0.10.1.
Gotcha! Instead of master pull from the release tag and you should be good to go https://github.com/Microsoft/BotFramework-Hubot/tree/v0.10.1
It definitely will but if you apply the botbuilder version fix to that code, you will not be facing this weird issue above. But yes, until we push a new...
I want to keep this open since there is still a bug somewhere in the next version of the teams adapter we want to ship here.
Yes, but I'm not sure that this adapter has the correct plumbing to do so. I think we made these changes before Teams provided the email address.
Right here: https://github.com/Microsoft/BotFramework-Hubot/blob/8d0cf959ff651f49cb4454c26cae968bd092f3a0/src/msteams-middleware.coffee#L110 I believe one of the values that the user object has now is an email address, some name qualities, and the AAD object id
The only other option would be to call the roster api upon message receipt: https://docs.microsoft.com/en-us/microsoftteams/platform/concepts/bots/bots-context#fetching-the-team-roster