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
Usage of rtm.start
may break in September
#866
Comments
I suspect that I have encountered issues with the changes described above, as connecting via
|
If it helps, the response to
It looks like another couple of API calls are required to get the channel and user lists. I'm happy to test/debug anything. |
Now that the preview for the changes to |
Just to say, I was bitten by this also. It looks like #857 includes the necessary bits to fix this already potentially. |
This has now been fixed with the 2.9.0 release. |
Maybe this can be removed as a pinned issue? |
Ah, yes, thanks. I unpinned it now. |
Hello from Slack developer relations.
It looks like you're still using the
rtm.start
method to negotiate websocket URLs for connecting to the RTM API. On September 20, 2022 the response tortm.start
will change to that ofrtm.connect
-- without all the extra info about channels, users, and the workspace you've come to expect fromrtm.start
. You may want to get ahead of that date and verify you can still connect and use the Web API to retrieve current state information instead.There will be a short preview of this behavior on September 13, 2022 but you can test it out today. More info about this deprecation announced back in October 2021 can be found here: https://api.slack.com/changelog/2021-10-rtm-start-to-stop
The text was updated successfully, but these errors were encountered: