privatenumber/snap-tweet

Produced image/snap doesn't show replies, RT's and likes... instead shows "Read 10.1k replies"

Zcehtro opened this issue · 4 comments

Bug description

What did you do? (Provide code in next section)
Took a snap of a tweet of one of the built-in examples. @jack's tweet #20.

What did you expect to happen?
For the snap to appear as in the READ.ME on the git page.

What happened instead?
The program executes correctly on the CLI.
But, in the produced snap, instead of there showing an


separator and then the replies, rt's and likes.. there's a button that says Read XX replies.

Do you have an error stack-trace?
Don't know what this is, but I'll get it if it can be explained to me :)

Reproduction

Provide one of the following:

  1. snap-tweet https://twitter.com/jack/status/20
  2. ??
  3. Sharing snap instead:

snap-tweet-jack-20
FYI I am not logged in to twitter on the browser, but I doubt that has any effect.

Environment

  • snap-tweet version: snap-tweet/1.2.1 win32-x64 node-v16.14.0
  • Operating System: Microsoft Windows 10 Home 10.0.19044 N/A Build 19044
  • Node version: v16.14.0
  • Package manager (npm/yarn/pnpm) and version: npm 8.5.0

Same issue as in #19 I suppose.

Thanks for the issue. It should work fine now:

npx snap-tweet https://twitter.com/jack/status/20

snap-tweet-jack-20

FYI the issue with Node v17 is also fixed if you want to go back to using it.

BTW, interesting that your image is significantly lower quality than mine, and the corners are black instead of transparent. I wonder what could be affecting that.

The black borders are because I was opening it in irfanview.
Irfanview uses by default a black background but doesn't handle transparency well when saving new images.
I assume therefore the tweet border is transparent.

Regarding the resolution of the image, I haven't got a clue... 🤨

You know... something happened now and I can't take a snap.
I'll open a new ticket... 😶

Something was happening that I couldn't take a snap, the program froze every time, stuck in the CLI with the message like taking a snap but it never changed. Somehow it resolved itself.. Maybe I needed to reopen the shell for installation changes to take effect... who knows.