Repository navigation
rtm.start depreciated starting 2022/09/20 #304
Description
Activity
Hi,
maybe its just me, but I cannot get the /api/rtm.start method working at all.
It requires the scope "rtm.stream" and I cannot add this scope to my user token?It looks like this lib no longer works. Any chance of a hotfix?
Reacted by GlenAlso hoping for this ^ . Didn't realize it was using rtm.start (api changed yesterday) - but it indeed appears to.
I'm not opposed to accepting a PR that would resolve this, but I don't personally have any reason to fix it. I've also got a lot of things happening in my personal life, so this library isn't a priority for me at this time.
If you do not need the Slack Real Time Messaging API specifically, I'd suggest switching over to soxtoby/SlackNet.
Also:
1- You probably shouldn't be using a socket-based API if the Web API serves your purposes.
2- You probably should be using the new Socket Mode API if you really need to keep track of events through sockets.I think I have some success on getting it to work "somehow".
All you needed to do is to comment out the body of
SlackAPI.SlackClient.ConnectedhereThe symptom is that this method is throwing a
NullReferenceExceptionwhen accessingloginDetails.userand the rest go south.The cause is that
rtm.startwill no longer provide those values (assuming it did, I can't validate because the documentation no longer show the fields before the deprecation), so access them will fail.Apparently, commenting out the body will lead to the fact that these properties are no longer initialized, so there might be downstream errors.
But something is better than nothing. Now I got the messages from the
onMessagemethod.To test this, make sure you create a classic slack app, the new granular permission version do not support rtm.
Long term, I agree with @Vedattt, socket mode is the way to go. I don't know if I want to take the dependency on aspnet.core though, for me personally, the whole point of using a slack frontend is to avoid having to manage a listening socket myself.
It looks like the rtm.start API method is depreciated in september of 2022, and will start returning a shortened response identical to rtm.connect. Are there plans to update the SlackClient to move over to rtm.connect and handle the new truncated response?