Custom receiver not respected when when using Socket Mode

Description

Hey friends,

I’m working on a Bolt app which uses the Adding Custom HTTP routes feature:

const { App, ExpressReceiver } = require("@slack/bolt")

const receiver = new ExpressReceiver({/* ... */})
receiver.router.get("/", (req, res) => res.send('Hello world'))

const app = new App({receiver, /* ... */})

I’m personally using this feature to serve a OAuth login flow over HTTP that works together with the Slack app to log folks into another service.

Recently, I became aware of Socket Mode, which is helpful in working around having a public webhook in my development environment.

Enabling socketMode in the App quietly discards my custom receiver.

My request is two part-er:

1. 🐛 BUG: It would be great if the App raised an error if you set socketMode and pass a customer receiver if the behaviour is to discard the receiver.
2. ⚡ ENHANCEMENT: I’m not entirely sure how this would work, but I’d like to a) use socketMode and b) add custom HTTP routes

What type of issue is this? (place an x in one of the [ ])

• bug
• enhancement (feature request)
• question
• documentation related
• example code related
• testing related
• discussion

Requirements (place an x in each of the [ ])

• I’ve read and understood the Contributing guidelines and have done my best effort to follow them.
• I’ve read and agree to the Code of Conduct.
• I’ve searched for any related issues and avoided creating a duplicate issue.

---

Bug Report

Steps to reproduce:

1. Create an App, add a custom receiver with HTTP routes
2. Enable socketMode on your app
3. Navigate to your HTTP routes

Expected result:

The custom HTTP routes are accessible.

Actual result:

The custom HTTP routes are NOT accessible.

---

ps. Bolt was very straight forward to get started with and socketMode seems quite innovative and awesome! Thanks for your hard work on this. ❤️ ❤️ ❤️

[majidmade]

Hi friends,

I have a use case that’s likely very similar to others’ – I want to use socket mode, but need to expose some custom routes (/version, /health, /metrics) for various operational reasons.

This worked for me; sharing here in case it helps someone else. (Honestly, I’m a little surprised this worked, so YMMV.)

Create receiver:

const receiver = new ExpressReceiver({
  signingSecret: process.env.SLACK_SIGNING_SECRET
});

Create app:

const app = new App({
  token: process.env.SLACK_BOT_TOKEN,
  signingSecret: process.env.SLACK_SIGNING_SECRET,
  socketMode: true,
  appToken: process.env.SLACK_APP_TOKEN
});

Note that I did not pass the receiver into the app.

Now just start them independently:

await app.start(PORT);
await receiver.start(PORT);

¯\(ツ)/¯

This feels hacky, so I’m still +1’ing the original issue. In the interim, though, hope this is useful to someone!

[misscoded]

Support for custom HTTP routes has been introduced and will be available with the release of 3.7.0. 🙂

With #1068 and #866 now both resolved, we’re going to close this issue. Thank you to all those that participated, from upvoting to providing details around use cases! 🙏🏼