`invalid_service` error in slack slash commands
See original GitHub issueDescription
Describe your issue here.
What type of issue is this? (place an x
in one of the [ ]
)
- bug
- enhancement (feature request)
- question
- documentation related
- testing related
- discussion
Requirements (place an x
in each of the [ ]
)
- I’ve read and understood the Contributing guidelines and have done my best effort to follow them.
- I’ve read and agree to the Code of Conduct.
- I’ve searched for any related issues and avoided creating a duplicate issue.
Bug Report
Filling out the following details about bugs will help us solve your issue sooner.
Packages:
Select all that apply:
-
@slack/web-api
-
@slack/events-api
-
@slack/interactive-messages
-
@slack/rtm-api
-
@slack/webhooks
- I don’t know
Reproducible in:
package version: Not Applicable
node version: 12.x
OS version(s): Windows 10
Steps to reproduce:
- Create a slack app and create a new slash command, add url, details, etc.
- Reinstall the app on development workspace
- Open slack client, type the slack command (which is visible in the popup meaning it has synced)
Expected result:
Slack accepts the command and hits my provided url using HTTP POST verb along with payload
Actual result:
Slackbot returns a silly error “failed with the error invalid_service
”. My endpoint doesn;t receive any hit from slack.
P.S. Sometimes the command is there in the popup but its details like description, etc are gone as shown in screenshot # 2. Then, I reinstall the app and it comes back as shown in screenshot # 3.
I’ve googled a lot about this problem searched YouTube but didn’t find any clue about whats wrong with it. Please help me I’m working on a project and deadline is really near 😞 I’ve spent a whole day meddling with it but to no avail.
Attachments:
Logs, screenshots, screencast, sample project, funny gif, etc.
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (2 by maintainers)
Thank you @seratch, revoking all tokens and reinstalling the app has solved my problem 😄. I’m closing this issue now. Thanks once again. 👍
Is there a fix for this issue? We keep running into this every so often and it’s very frustrating to revoke and reissue tokens and redeploy the app