Skip to content

Facebook Adapter on Composer 2.1.x doesn't trigger middleware components #8716

Open

Description

We have a Composer Bot running on 2.1.1 with several custom components installed for example for logging messages to our main system and other purposes.

We had Facebook Messenger connected via the Azure Channel and this worked fine, as well as in Emulator and in our custom Twilio Adapter.

Now we aimed to use the Facebook Adapter instead of the Azure Channel. Installing in Composer was easy and bot is running but none of our custom middleware components are triggerd. The OnTurnAsync methods of those components are just not executed when messages are sent or received via the Facebook Adapter.

Version

Version: 2.1.1
Electron: 8.2.4
Chrome: 80.0.3987.165
NodeJS: 12.13.0
V8: 8.0.426.27-electron.0

To Reproduce

Steps to reproduce the behavior:

  1. Create or use a sample bot with Composer 2.1.x
  2. Create a custom middleware component as descendant of IMiddleWare with an an OnTurnAsync method
  3. Publish middleware component locally
  4. Install middleware component in Composer
  5. Install and configure Facebook Adapter in Composer connections settings (we used an ngrok tunnel for the webhook)
  6. Run the bot once in Composer and stop it (not sure if needed)
  7. Open bot in Visual Studio and open code of middleware
  8. Put a breakpoint on your custom OnTurnAsync method in middleware component code
  9. Start bot in Visual Studio
  10. Send messages from Emulator - breakpoint is triggered
  11. Send messages from Facebook - breakpoint is not triggered

Expected behavior

OnTurnAsync of each installed component should be executed similar as when messages are routed via the default route.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

Labels

BacklogBacklog items - not in current milestoneBot ServicesRequired for internal Azure reporting. Do not delete. Do not change color.ExemptFromDailyDRIReportType: BugSomething isn't workingcustomer-replied-toRequired for internal reporting. Do not delete.customer-reportedRequired for internal Azure reporting. Do not delete.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions