-
Notifications
You must be signed in to change notification settings - Fork 105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
channel-slack RTMClient does not start #939
Comments
Hi |
Looking at the Event and RTM API, I'm guessing we could maybe port directly from RTM to Events. I'm willing to dig into it and learn enough to make a patch, I just won't be able to touch it for a couple weeks or so. |
I confirm the issue is happening. Thanks for reporting. The solution would be to support both the RTM api (for legacy Slack apps) and the Events (for Bot Granular Permissions apps). Removing support for the RTM api from Botpress would introduce breaking changes to existing Botpress installations. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Fixed |
Describe the bug
Slack is deprecating RTM bot permissions. This link currently works but won't past 2020-02-21
Slack: Create new legacy RTM app
On a banner at the top of the newly created app page:
When configuring Slack integration with granular permissions (container (10).log)
, container startup fails with the following error (also attached). Digging in, this seems to be related to how Slack is setting up App integrations, where new apps by default do not use the RTM permissions.
To Reproduce
Steps to reproduce the behavior:
channel-slack
modulechannel-slack.json
for the bot, using tutorial in the Botpress Slack integrationExpected behavior
Botpress starts and greeter bot responds in Slack.
Screenshots
From the container orchestration logs:

Warning from the Slack admin page:

Counterpoint: creating a legacy bot to show difference:

After configuring as tutorial suggests:

And here's the bot on my Slack channel:

Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: