Skip to content
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

Open
gtallen1187 opened this issue Aug 17, 2018 · 7 comments
Open

Heroku Deployment: missing_scope #380

gtallen1187 opened this issue Aug 17, 2018 · 7 comments

Comments

@gtallen1187
Copy link

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:

image

Navigating to the /invite url shows the following error:

Cannot GET /invite

@chao-mu
Copy link

chao-mu commented Nov 26, 2018

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


2018-11-26T02:37:47.468451+00:00 app[web.1]: Mon Nov 26 2018 02:37:47 GMT+0000 (UTC) – Error: Too Many Requests
2018-11-26T02:37:47.468455+00:00 app[web.1]:     at Request.callback (/app/node_modules/superagent/lib/node/index.js:686:11)
2018-11-26T02:37:47.468457+00:00 app[web.1]:     at /app/node_modules/superagent/lib/node/index.js:868:18
2018-11-26T02:37:47.468459+00:00 app[web.1]:     at IncomingMessage.<anonymous> (/app/node_modules/superagent/lib/node/parsers/json.js:16:7)
2018-11-26T02:37:47.468461+00:00 app[web.1]:     at emitNone (events.js:91:20)
2018-11-26T02:37:47.468463+00:00 app[web.1]:     at IncomingMessage.emit (events.js:185:7)
2018-11-26T02:37:47.468464+00:00 app[web.1]:     at endReadableNT (_stream_readable.js:974:12)
2018-11-26T02:37:47.468466+00:00 app[web.1]:     at _combinedTickCallback (internal/process/next_tick.js:80:11)
2018-11-26T02:37:47.468467+00:00 app[web.1]:     at process._tickCallback (internal/process/next_tick.js:104:9)

@chao-mu
Copy link

chao-mu commented Nov 26, 2018

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.

@chickendiver
Copy link

I share the same concern as @chao-mu - Would be good to see this resolved to support Slack Apps

@gtallen1187
Copy link
Author

@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?

@gtallen1187
Copy link
Author

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.

@chickendiver
Copy link

chickendiver commented Feb 23, 2019 via email

@XhmikosR
Copy link

We are actually hitting this for months.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants