dutchcoders / dutchcoders/slackarchive
Missing scope error: But scopes present on Slack
- Dominant language
- Go
- Stars
- 301
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Description
This is another issue I'm seeing: I keep getting a missing scope from slack:
```
slackarchive-bot_1 | 2019/02/17 20:49:26 Syncing latest channel messages: C1U1G6PGR
slackarchive-bot_1 | nlopes/slack2019/02/17 20:49:26 misc.go:74: parseResponseBody: {"ok":false,"error":"missing_scope","needed":"channels:history","provided":"identify,bot:basic"}
```
However the scopes are actually present:

I did of course try to reinstall the app. I even tried to recreate the bot. I also tried to include both tokens (not just the xoxb but also the xoxp) in the slackarchive-bot yaml file, because this was mentioned here that it needs both tokens: https://github.com/dutchcoders/slackarchive/issues/24#issuecomment-457973582
But then I get a different error (that it can't connect to the RTM):
```
slackarchive-bot_1 | nlopes/slack2019/02/17 21:01:02 misc.go:74: parseResponseBody: {"ok":false,"error":"missing_scope","needed":"rtm:stream","provided":"identify,bot,channels:history,channels:read,team:read,users:read"}
slackarchive-bot_1 | nlopes/slack2019/02/17 21:01:02 websocket_managed_conn.go:140: Failed to start or connect to RTM: missing_scope
```
This is how I added both:
```
tokens:
- xoxb-xxx
- xoxp-xxx
```
So it looks like the scopes are correctly set (as they do show in the second example) but for some reason are not applying to the bot I've created. Sorry for my ignorance here, I've never used the Slack API at all. I did read all the relevant issue topics (the last one on this post is really relevant: https://github.com/dutchcoders/slackarchive/issues/24#issuecomment-457973582 - and probably should be part of the readme, as well as the elasticsearch info). But I still can't get it to work.
By the way is there an IRC channel to discuss about slackarchive? Or a slack perhaps?
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.