No listeners executed; falling back to catch-all about botframework-hubot

[willwen]

I guess no one else has this problem :(

[MatSFT]

Hey Will. Sorry this issue slipped my mind. I'll take a look at it today. Are you by any chance copying and pasting the message into teams or typing it out directly?

[willwen]

Hi Matt, thanks for getting back, I am typing it out directly every time

[MatSFT]

The rosie2 part is because the adapter replaces the mentioned bot name in teams with the hubot name the all of the regexes have been registered with. Let me try to reproduce the issue locally and see if I can get a fix out.

[willwen]

okay, thanks a bunch, if you have trouble reproducing the bug, then just confirm with me that you have no problems, and i'll register another bot from scratch.
I am assuming since the adapter does a name replace, the BotFramework name DOES NOT have to match the local hubot name

[MatSFT]

You are correct in that the bot framework name does not need to match. Looking at your issue now.

[MatSFT]

This seems to be working for me.

[MatSFT]

I set up the bot using yo hubot and chose botframework as the adapter.

Then I updated the example.coffee script to uncomment the badger script.

Here is a zip of my bot: HubotBot.zip

[willwen]

Okay, I guess I messed up somewhere, and I'll start again tomorrow. I'll update on my progress then.

[MatSFT]

make sure you're running the latest hubot-botframework package

[willwen]

Ok, it works for me now too:

Somethings that I noticed that I did differently was:
1)

    "hubot-botframework": "^0.10.0",
vs 
    "hubot-botframework": "^0.10.1",

and
2)
I also used npm link rather than static files in node_modules/

In the above image you can see my version, the symbolic link (8/29/2017) vs your new version (9/26/2017)

See if you have the same error if you use a symbolic link as per described:
https://hubot.github.com/docs/adapters/development/

[MatSFT]

The version might actually do the trick. There were quite a few large changes in the teams code between v 0.10.0 and 0.10.1

[MatSFT]

Oh I see. You probably grabbed the code because we hadn't published the latest version. you should be okay with just grabbing the npm package instead of pulling the code and doing a symbolic link. Not sure of any reason why you would want the symbolic link.

[MatSFT]

I'm going to go ahead and close this issue since it is working for you now.