SlackAPI icon indicating copy to clipboard operation
SlackAPI copied to clipboard

How do I resolve a missing_scope error

Open BermudaLamb opened this issue 2 years ago • 4 comments

I'm running the example TestingSlackAPI. My command api set up is giving me xoxb token, not an xoxp token. I'm getting the response back missing_scope. How do I resolve this?

BermudaLamb avatar Dec 01 '21 18:12 BermudaLamb

It depends on the missing scope. This is an error from the slack API itself, not from this client. Take a careful look at the OAuth scopes granted to the application.

bakester14 avatar Dec 07 '21 23:12 bakester14

Hi! I have a similar problem:

I'm building a very simple Slack client embedded into my app. For that, it needs to act on behalf of the user. Therefore, I've created a modern app that has lots of different scopes available (see in the screenshot).

Now, while I can easily post content using SlackTaskClient, I cannot perform lookups for channels and so on.

image

After looking through different docs I've learned about the ConnectAsync() method.

However, it tells me my app is missing rtm:stream scope.

image

Now, this is the scope that is given to old bot apps which take bot token as an input, not the user's one.

What should then I do to let my app to act on behalf of my user?

danielkornev avatar Feb 20 '22 17:02 danielkornev

Aha, so it seems like the problem is this: https://api.slack.com/changelog/2021-10-rtm-start-to-stop

Apps created after November 2021 won't work with rtm.start API. 🤔

danielkornev avatar Feb 20 '22 20:02 danielkornev

Aha, so the thing is, one can use Conversations instead of Channels. Seems like this PR would make this library's usage much simpler: https://github.com/Inumedia/SlackAPI/pull/274

danielkornev avatar Feb 20 '22 22:02 danielkornev