Custom Port Ignored when Using Socket Mode

[M1kep]

Description

I'm attempting to utilize the custom HTTP routes feature in an application that hosts multiple Slack Bots. For this, I'm attempting to configure the receiver to listen on a specific port for each bot. There are a few issues I'm running into:

1. The SocketModeReceivers start method does not accept a port at all
2. When the App constructor is called, the InstallerOptions are passed to the SocketModeReciver constructor. The problem I run into is that the InstallerOptions being accepted by the App constructor are HTTPReceiverOptions['installerOptions'] which do not contain a Port property. The port property is then used in the SocketModeReceiver constructor to determine what port to listen on.

I'm not really sure what the best method to achieve this would be

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

Filling out the following details about bugs will help us solve your issue sooner.

Reproducible in:

package version:3.7.0

node version: v16.9.1

Typescript Version: 4.4.3

OS version(s): macOS Monterey - 12.0.1 (21A559)

[M1kep]

This also breaks using more than one SocketMode App with the CustomRoutes property with the below error:

Error: listen EADDRINUSE: address already in use :::3000

[srajiang]

Hi @M1kep - Thanks for surfacing this issue. Going to open a separate issue now for getting the port option added to the HTTPReceiverOptions in the next release v3.8

Will respond to #1180 in the thread - that is the workaround that we recommend, but I can see that you are having issues (and I can replicate them).

[seratch]

This issue will be fixed by #1184