-
Notifications
You must be signed in to change notification settings - Fork 1
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
Check Slack classic apps permissions/integration #62
Comments
Opened issue to clarify situation slack-ruby/slack-ruby-bot#278 |
We need migration from RTM usage at all. |
RTM is only available with Classic Apps, not New Apps so you won't be able to upgrade it to the latest granular permissions: We don't have plans to deprecate Classic Apps at this stage (no time frame) so you can still use them for now. However it is possible that this could change (you would receive a warning to then update before this happened though). We recommend moving to Socket Mode if possible: https://api.slack.com/apis/connections/socket You can see a list of events that are supported in Socket Mode (Events API) vs RTM below. Anything not listed as Events API but shows as RTM is not possible with Socket Mode. |
Warning: As of December 4th, 2020 Slack no longer accept resubmissions from apps that are not using granular permissions, or so-called "classic apps". On November 18, 2021 Slack will start delisting apps that have not migrated to use granular permissions. This library implements legacy, real-time support for classic apps. You should not be building a new bot with it and use slack-ruby-bot-server-events instead. For a rudimentary bot you can even start with slack-ruby-bot-server-events-app-mentions. See MIGRATION for migration help.
The text was updated successfully, but these errors were encountered: