-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Heroku Deployment: missing_scope #380
Comments
I am encountering this problem as well. If it matters, I set up my api token with a bot user's (which I gave admin privs) oath token. In my logs I'm getting
|
Creating a legacy token fixed this issue. Perhaps this should be added to the documentation? Worrisome is that legacy tokens will at some point be deprecated, breaking all instances. |
I share the same concern as @chao-mu - Would be good to see this resolved to support Slack Apps |
@chao-mu - I'm planning to dig back into this over the weekend. Which legacy token fixed your issue? A legacy slack token? And any chance you can share a docs link for getting this legacy token? |
It looks as though @twbs managed to get this up and running and is using it on their homepage as their default way to onboard new people into Slack. This workflow is awesome, I'd really love to replicate it for my projects. @chao-mu and @chickendiver - If one of you wouldn't mind explaining to me which legacy token to use, I'd really appreciate it. As you can probably tell, I'm an extreme beginner, so any help would be greatly appreciated. |
We are actually hitting this for months. |
The Heroku deployment builds perfectly and it looks as though it's going to work, however when a user enters their email and passes the recaptcha, once they click the "send invite" button they get a "missing scope" error:
Navigating to the
/invite
url shows the following error:Cannot GET /invite
The text was updated successfully, but these errors were encountered: