-
Notifications
You must be signed in to change notification settings - Fork 243
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
How do I resolve a missing_scope error #285
Comments
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. |
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. After looking through different docs I've learned about the ConnectAsync() method. However, it tells me my app is missing rtm:stream scope. 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? |
Aha, so it seems like the problem is this: Apps created after November 2021 won't work with rtm.start API. 🤔 |
Aha, so the thing is, one can use Conversations instead of Channels. Seems like this PR would make this library's usage much simpler: |
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?
The text was updated successfully, but these errors were encountered: