-
Notifications
You must be signed in to change notification settings - Fork 315
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Auto slack uploader fails #284
Comments
Yeah, looks like an emojipacks issue to me. I'm up for a warning in the README. Slack has no API for uploading emoji, only listing them, so there's not really a better option except for browser automation/emulation. I'm open to ideas though! |
Ah, well that's a great shame. I'll have a little look into it and see what our alternatives could be. I agree that in the meantime a warning in the README would be a good idea. |
Looking through, it seems most (if not all) batch slack emoji auto uploaders are broken as of Slack's latest update to the emoji uploading/managing UI. However, I did find a working chrome extension that allows for a slightly more manual way of batch uploading emojis. You drag and drop all the emoji files into this extension's UI and it will batch upload them all automatically. Extension can be found here: https://chrome.google.com/webstore/detail/neutral-face-emoji-tools/anchoacphlfbdomdlomnbbfhcmcdmjej |
Looks good to me, mind adding a quick PR with a warning and a link to the Chrome extension? |
No problem, will do as soon as I can. |
Not sure if this has already been mentioned, already known or if it is specifically a problem with emojipacks (it probably is but I felt it was worth mentioning it here).
I followed the instructions to start the auto upload:
First I ran
yarn install
Then
yarn build
which initially had test failure problems but that seems to have been fixed.Then I ran
emojipacks
I entered my slack details and the absolute path to the
parrotparty.yaml
file.Then I get this error:
This most probably has something to do with emojipacks and it seems many people have voiced their errors there too. It seems that what this issue is about is the most likely culprit. Not sure if/when that will be fixed or how long.
So I guess this is more of a notification to anyone wanting to run the auto uploader that it may not currently be working. Are there any alternatives we could look into in the meantime or even as a permanent solution/replacement?
The text was updated successfully, but these errors were encountered: