You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently, we upgraded Bolt-JS in our Slack app to version 3.21.4. Since then, we've been encountering the following error:
/ticketing-system/node_modules/path-to-regexp/dist/index.js:136
throw new TypeError(`Unexpected ${nextType} at ${index}, expected ${type}: ${DEBUG_URL}`);
^
TypeError: Unexpected ? at 36, expected END: https://git.new/pathToRegexpError
at Iter.consume (ticketing-system/node_modules/path-to-regexp/dist/index.js:136:15)
at consume (ticketing-system/node_modules/path-to-regexp/dist/index.js:193:16)
at parse (ticketing-system/node_modules/path-to-regexp/dist/index.js:197:20)
at ticketing-system/node_modules/path-to-regexp/dist/index.js:308:74
at Array.map (<anonymous>)
at pathToRegexp (ticketing-system/node_modules/path-to-regexp/dist/index.js:308:25)
at match (ticketing-system/node_modules/path-to-regexp/dist/index.js:278:30)
at Server.<anonymous> ticketing-system/node_modules/@slack/bolt/dist/receivers/SocketModeReceiver.js:104:71)
at Server.emit (node:events:515:28)
at parserOnIncoming (node:_http_server:1143:12)
Do you have any suggestions for fixing this from our side, or should we downgrade to a previous version until the issue is resolved?
Thank you!
The text was updated successfully, but these errors were encountered:
If you could help us reproduce the problem, that would be helpful to understand what is happening.
It seems the stack trace points to code that runs in the default error handler in the Socket Mode receiver.
Can you share your App configuration, and steps on how to reproduce? What event triggers this error? Do you have any handlers defined in your for the particular event?
Hey,
Recently, we upgraded Bolt-JS in our Slack app to version 3.21.4. Since then, we've been encountering the following error:
Do you have any suggestions for fixing this from our side, or should we downgrade to a previous version until the issue is resolved?
Thank you!
The text was updated successfully, but these errors were encountered: