Started crashing today

[ANPez]

Started crashing today

[irae]

I was having the same problem. I was using tiny-care-terminal without Twitter API Keys. I never bothered to setup, even though I knew it was the better idea.

Now, I followed the steps on readme and created myself the 4 keys needed, added to my .bashrc and everything is working again.

I would guess this is related to latest Twitter API changes. A nice summary was put up by expert twitter app developers here: http://apps-of-a-feather.com/

[mojoaxel]

Strangely enough, it doesn't crash for me today, either. I didn't change anything.

I suspect that it was some kind of emoji in a tweet or another tweet-specific problem. If you still encounter that problem please have a look at the tweeter accounts you subscribed to. Thx!

[slaughtr]

I've been getting the same for a few days. I think it may be related to upgrading to npm 6, but I'm not sure. It looks to be the blessed module, which hasn't seen any updates in 2 years :(

[notwaldorf]

Hmm, I'm on npm 6 and node 8ish (but < 8.11) and it looks ok 🤔.
I published a new version of tiny-care-terminal (1.4.1) which has a bunch of changes -- mind giving that a try?

[Tardog]

I've got the same issue, even with tiny-care-terminal 1.4.1. :(

My stack trace looks a lot like the one above, only with slightly different line numbers (tiny-care-terminal/node_modules/blessed/lib/program.js:416:23 instead of 418:15).

Node: v10.1.0
npm: 5.6.0
Shell: fish
Terminal: gnome-terminal
OS: Ubuntu 18.04

[ANPez]

Still having the same issue with 1.4.1

[mojoaxel]

I cannot reproduce this.

[Tardog]

I was about to try the solution posted by @irae, but backed off when Twitter demanded I add my mobile phone number to my account before creating an app. There are too many privacy concerns.

@mojoaxel Do you need more information to reproduce the crash?

/edit:
Strangely enough, it doesn't crash for me today, either. I didn't change anything.

[ANPez]

Strangely enough, it doesn't crash for me today, either. I didn't change anything.

Same here. Today started working again without a problem.

[Tardog]

I suspect that it was some kind of emoji in a tweet or another tweet-specific problem.

Yes, make sense. Thank you!

[notwaldorf]

Closing since it got resolved!

[mojoaxel]

I really would love to see the tweet that causes this problem 😡
Keep your eyes open!