Open jeffutter opened 8 years ago
When I've had this issue in the past it means that Slack has changed their API and the response is no longer parsing with Aeson. When this happens usually I can update slack-api to the latest version and it will work again. Otherwise, I would have to dig in and figure out what isn't parsing properly.
I think I want to eventually move off slack-api because it relies on a reliable slack API and they don't version their API at all so it changes.
Sent from my iPhone
On Jul 14, 2016, at 9:35 AM, Jeffery Utter notifications@github.com wrote:
I'm getting this error when trying to start fomobot. The full output is a huge json blob followed by: fomobot: user error (When parsing the record Preferences of type Web.Slack.Types.Preferences.Preferences the key show_member_presence was not present.)
I am starting fomobot locally, running bin/setup, bin/build, and bin/run after setting my slack key and redis urls in .env
Am I missing something here? it sounds like perhaps my bot user doesn't have some permission it needs. However, I don't see anywhere in the slack interface to change that.
Am I missing something?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
FWIW I manually bumped the slack-api dep to 0.9 and I get the same error shrug
I've continually had issues with that library. I've actually forked it and just removed that entire json processing part since I don't use it for a different project. I've been busy recently so I haven't had much time to give FOMObot what it deserves. I'll try and get this working this week though.
I'm getting this error when trying to start fomobot. The full output is a huge json blob followed by:
fomobot: user error (When parsing the record Preferences of type Web.Slack.Types.Preferences.Preferences the key show_member_presence was not present.)
I am starting fomobot locally, running
bin/setup
,bin/build
, andbin/run
after setting my slack key and redis urls in .envAm I missing something here? it sounds like perhaps my bot user doesn't have some permission it needs. However, I don't see anywhere in the slack interface to change that.
Am I missing something?