Closed johnnymatthews closed 6 years ago
Same here.
It looks like this happens when the slack token is invalid... I get it when I run this command:
SLACK_TOKEN=aksdhfuahsduf node main.js
Are you guys using legacy tokens? Here's a token you can look at and test with: xoxp-254112160503-252950188691-252375361712-6cbf56aada30951a9d310a5f23d032a0
You generate a legacy token here:
https://api.slack.com/custom-integrations/legacy-tokens
DON'T POST YOUR TOKEN HERE. They give anyone who has it access to your slack account. The one I posted is one I use for testing.
Aaaah, I see where I went wrong. I included the square brackets when exporting the token. I've just submitted a pull request to change the README.md
around a bit to make things a bit clearer.
The export command should be:
export SLACK_TOKEN='your-slack-token-here'
Try that @umbonia.
I second that.
Thanks for clearing this up @mohnjatthews! The instructions have been updated in #58.
After installing and running
node main.js
the application opens for about half a second, but then closes without any error message output.Error_log.txt
contains the stringError: invalid_auth
. There is nothing else in the log file.I've tried reassigning my Slack Token but there was no change in this apps behavour.
This issue was raised previously, but then was closed on the same day by @GitHamo: https://github.com/evanyeung/terminal-slack/issues/48. I don't know if he was able to find a solution.