Heroku Deployment: missing_scope

Question

Heroku Deployment: missing_scope

gtallen1187 opened this issue 6 years ago · comments

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

Autumn Green · Answer 1 · Mon Nov 26 2018 10:36:17 GMT+0800 (China Standard Time)

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)

Autumn Green · Answer 2 · Mon Nov 26 2018 10:50:24 GMT+0800 (China Standard Time)

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.

Bradley · Answer 3 · Wed Feb 06 2019 11:34:13 GMT+0800 (China Standard Time)

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

Greg Allen · Answer 4 · Thu Feb 21 2019 07:50:54 GMT+0800 (China Standard Time)

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

Greg Allen · Answer 5 · Sat Feb 23 2019 14:48:42 GMT+0800 (China Standard Time)

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.

Bradley · Answer 6 · Sat Feb 23 2019 15:11:36 GMT+0800 (China Standard Time)

Totally. Check out this link <https://mailtrack.io/trace/link/1d0752e920c4fb7703d1dfefe5d5561b875696c3?url=https%3A%2F%2Fapi.slack.com%2Fcustom-integrations%2Flegacy-tokens&userId=697669&signature=5eae29a92efc3dc5>, then select "Create Token" on whichever Slack team you want to use. Be aware that these tokens will likely be deprecated, thereby breaking your sign-up form when it happens.

…

On Fri, Feb 22, 2019 at 11:49 PM Greg Allen ***@***.***> wrote: It looks as though @twbs <https://github.com/twbs> managed to get this up and running and is using it on their homepage <https://mailtrack.io/trace/link/94f83a9c18450ace1d71002b6099950ec01f32a4?url=https%3A%2F%2Fgetbootstrap.com&userId=697669&signature=66fd8cfa54667034> 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 <https://github.com/chao-mu> and @chickendiver <https://github.com/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. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <https://mailtrack.io/trace/link/1d3f31d2da62e6f419ba134939f1d7e722feabce?url=https%3A%2F%2Fgithub.com%2Frauchg%2Fslackin%2Fissues%2F380%23issuecomment-466623044&userId=697669&signature=17f9b48ce078d6c5>, or mute the thread <https://mailtrack.io/trace/link/b7a1022ec3b913da9f9eac9b724fabe62c39131f?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAGDPKntLV4-7eloxxsJuiunmQYhURY1Dks5vQORvgaJpZM4WA89C&userId=697669&signature=997ceddca8134ff5> .

XhmikosR · Answer 7 · Sat Oct 19 2019 14:45:20 GMT+0800 (China Standard Time)

We are actually hitting this for months.