Description
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:
Got tokens
Logged in
Uh oh! Error: Login error: could not get emoji upload crumb for https://[my-subdomain].slack.com
(node:11208) UnhandledPromiseRejectionWarning: Error: Login error: could not get emoji upload crumb for https://[my-subdomain].slack.com
at Slack.emoji ([my-path]\npm\node_modules\emojipacks\lib\slack.js:162:34)
at Slack.emoji.next (<anonymous>)
at onFulfilled ([my-path]\\npm\node_modules\emojipacks\node_modules\co\index.js:65:19)
at process._tickCallback (internal/process/next_tick.js:68:7)
(node:11208) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:11208) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
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?