Single-channel config resulting in "Not a permitted channel" about slackin HOT 14 CLOSED

Updated to the latest commit on master today and this is still an issue :-/

from slackin.

I bothered people at Slack about this issue and they said:

I also must mention that Slackin uses an unpublished/undocumented/private API method to perform the invite itself, and we're unable to support it for public use (supported methods are listed at http://api.slack.com/methods).

Did they silently change the API that slackin was using and that's why it doesn't work anymore?

from slackin.

From the readme:

Important: if you use Slackin in single-channel mode, you'll only be able to invite as many external accounts as paying members you have times 5. If you are not getting invite emails, this might be the reason. Workaround: sign up for a free org, and set up Slackin to point to it (all channels will be visible).

from slackin.

Thanks Matt, I verified that is not the case. I am far under the limit for single-channel guests and I can invite them through the web panel.

from slackin.

Hi, I have the same issue. If I specify multiple channels (resulting in a dropdown menu in the frontend) it works just fine, but with only one channel it fails.

As a workaround I just specified "channelname," which leads to an empty option in the dropdown. It seems to work then.

from slackin.

I also had this problem - @lutoma's solution is working for now. Would be great to get rid of the empty dropdown option though.

from slackin.

Same issue here with a single channel.

Running slackin TEAM-ID TOKEN-ID --channels 'CHANNELNAME,' --port $PORT works fine but still displays a dropdown to the user.

from slackin.

This looks to me like this bug was introduced by this commit: e35a05b.

The form handler still expects channel to be provided in the POST payload, but the <select> is only rendered if the channel list contains more than one item.

from slackin.

Seeing this issue as well. Happy to deploy master once #152 is merged.

@lutoma Thanks for the workaround!

from slackin.

@carmstrong Yay, #152 has been merged!

from slackin.

#152 has been merged!

🍻 And 0.8.3! We can stop using our fork now! :)

from slackin.

I'm still seeing this on the Heroku app. Was #152 set to resolve it there also?

from slackin.

I'm still seeing this on the Heroku app.

Are you launching 0.8.3? The badge in the README is still using 0.8.2. Use this link:
https://heroku.com/deploy?template=https://github.com/rauchg/slackin/tree/0.8.3

from slackin.

@txsteven @carmstrong fixed the Badge. Let me know if it works!

from slackin.