Open nivethan-mdsol opened 4 years ago
rampatra
commented
4 years ago Looks like a missing scope issue. Can you pl verify if you added the necessary scopes?
Also, when you said you have been using slackbot for a year, did you mean you have been using jbot for a year? If yes, what version have you been using?
nivethan-mdsol
commented
4 years ago I'm using version: JBot v 4.1.1-SNAPSHOT Detailed info: A year back, I created Bot under custom integration. (Browse Apps -> Custom Integrations ->Bots)
Steps:
but this custom bot cannot be Publicly distributed.
So I created a Slack App, which eventually gives me the Bot User OAuth Access Token. when i used this Token, am getting prev. mentioned error:
2020-04-18 04:48:33.529 ERROR 51155 --- [ main] m.r.jbot.core.slack.SlackService : Error fetching im channels for the bot: . . . 2020-04-18 04:48:33.542 ERROR 51155 --- [ main] me.ramswaroop.jbot.core.slack.Bot : No web socket url returned by Slack.
The main reason for this issue is that RTM is not connecting which should get us to Connecting to WebSocket at wss://cerberus-xxxx.lb.slack-msgs.com/websocket/xxxxx I was going through the recent changes in Slack directory, turns out they are deprecating the scopes which are used for Classic Bot(scope:bot) which helps to connect to RTM. So i couldn't find the scope:bot neither in Bot Token Scopes nor User Token Scopes. I tried different latest available scopes which has rtm conjunction, but still error.
Purpose of this Bot: When someone invites this bot to any channel or DMs the keyword: Lesson this bot will Post a Software testing related quotes everytime, to educate the s/w testers like daily quotes and +few other capabilities with different contents. (Not using command and slackIncomingWebhookUrl features.)
nivethan-mdsol
commented
4 years ago @rampatra " New Slack apps may not use any Real Time Messaging API method. Create a classic app and use the V1 Oauth flow to use RTM. " Ref: https://api.slack.com/rtm
gonzoe
commented
4 years ago @rampatra
Bump.
I've only had a few mins across multiple days to look at this. Any insights into what needs to happen to remove the need for RTM from JBot? I assume JBot will not function as a classic app.
Elfilali-Taoufiq
commented
4 years ago hello @rampatra , any update dor this issue please, i'm facing the same error
gonzoe
commented
4 years ago If you create a new classic app from scratch here, you can get JBot to work. I could not figure out a way to convert an existing app. Its not an ideal solution if you're trying to build a bot that will pass a security review without lots of hand-waving, but you can get something working until this gets resolved.
Elfilali-Taoufiq
commented
4 years ago thank you @gonzoe for the help, but a classic app doesn't work for me, Jbot can't connect to slack, it give me the error : _
No web socket url returned by Slack.
_
gonzoe
commented
4 years ago If you change any of the scopes, your classic app appears to get promoted automatically to a new app. The Slack docs are not super clear on this. You need to create the classic app and install it without changing the scopes.
Elfilali-Taoufiq
commented
4 years ago for the installation the application must have scopes, so i added some scopes i order to install it for one time but it stiil give me the error
is there some spescifics scopes that i should add ?
garyarobinson
commented
4 years ago Look at the url the RestTemplate is hitting;
public String getImListApi() {
return this.slackApi + "/im.list?token={token}&limit={limit}&next_cursor={cursor}";
}The endpoint is returning a deprecated response
{
"ok": false,
"error": "method_deprecated",
"response_metadata": {
"messages": [
"[ERROR] This method is retired and can no longer be used. Please use conversations.list or users.conversations instead. Learn more: https:\/\/api.slack.com\/changelog\/2020-01-deprecating-antecedents-to-the-conversations-api."
]
}
}That response is getting transformed into what it thinks is the expected response and is throwing a runtime exception.
To reproduce this error go to https://api.slack.com/methods/im.list/test and provide a valid classic bot token.
rampatra
commented
4 years ago @garyarobinson but this API should work until Feb 2021. See here:
This method is deprecated. It will stop functioning in February 2021 and will not work with newly created apps after June 10th, 2020.
Or, if a developer has created an app after June 10th then it won't work.
Anyway, I will try to update the API endpoint if I get some time this weekend. PRs are always welcome.
Hi @rampatra Been using slackbot for an year. There is a recent change happened Slack directory w.r.t RTM api.
When i try to run, am getting below error:
ERROR
Following are Scopes: Bot Token Scopes app_mentions:read channels:history channels:join channels:read chat:write groups:history im:history mpim:history
User Token Scopes: channels:history channels:read channels:write chat:write files:read groups:history groups:read groups:write Note: I tried change the very minimal scopes and re-installed, still facing same error.