-
Notifications
You must be signed in to change notification settings - Fork 885
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
Failed! missing_scope ERROR #146
Comments
Hello ! Any update on this issue ? ;) |
@allomorphy @ThomasLachaux did any of you solve this? I have the same issue. |
@kindofone @ThomasLachaux @allomorphy, did any of you find an alternative solution? |
@elimcjah I didn’t invest time in trying to solve this. So, nothing on my end 🤷♂️ |
Hi guys, I'm having the same issue here, an I tried adding a new Scope under User Token Scopes I added the scope "Invite members to a workspace and approve or deny invitation requests" and tried to "Reinstall to Workspace", bu I get the nex request by Slack I don't know if this is the real problem, but if so, Slack is asking for an Enterprise plan to do this. Any suggestions to solve this by the maintainers/owners. Is this the way to solve it? Basically same error as @allomorphy |
Looks like that this project is not working anymore for new installs. |
Same here, can't use it for the fresh community |
+1 |
+1 To give the client scope : tried this https call Have tried this quickfix for granting client scope: https://medium.com/@andrewarrow/how-to-get-slack-api-tokens-with-client-scope-e311856ebe9 . |
|
I think this issue does not go away. If you do not have legacy token, then the OATH token is broken for free slack users. Enterprise slack users may enjoy the benefit of this project only. |
Just tried, doesnt work indeed. |
Did not work for me either. I lost the legacy token too. |
Did not work for me either. I can't make the legacy token too. |
Any updates? |
No. This bug is not this application. |
I'm using this as a workaround: |
Having this same issue but getting; Invalid permissions requested when trying to add "admin.apps:read" as a User OAuth scope. Incredibly frustrating? I am the workspace and App admin, so can't understand why I still have the error? |
I'm having the same issue. No previous suggestions seem to help. Anyone know how to fix this? |
Hi Folks, neat App,
I installed fine through downloading and executing the docker container.
Then I accessed with a browser and received the error:
Failed! missing_scope
in the browser.I cannot access more than this as logs from the container:
POST /invite 200 1110.118 ms - 624 GET /css/style.css 304 3.993 ms - - GET /images/bg.jpg 304 1.094 ms - -
In the Oauth & Permissions Page at /oauth? -- which has changed since the manual was written --
I added under User Token Scopes
But when I follow up by pressing Please reinstall your app for these changes to take effect ..
The page reports:
This app can not be installed on this workspace. Apps with this feature are only available to Enterprise customers.
We are on the Slack Standard Plan.
Do I have the wrong Oauth permissions option or id an Enterprise Grid a requirement for programatic inviting of Users
Thanks for your help and any advice.
The text was updated successfully, but these errors were encountered: