Skip to content
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

Missing tweets and no error raised by client when using searchStream #53

Open
blombern opened this issue Nov 8, 2022 · 0 comments
Open

Comments

@blombern
Copy link

blombern commented Nov 8, 2022

I'm using searchStream to receive tweets that happen a handful times a day. I seem to be unable to achieve this reliably. All the filter rules are simply tweets by specific users.

Expected behavior

I would expect to either receive the tweets, or an error to indicate a dropped connection or similar.

Actual behavior

I receive no tweets and no errors. It seems to deliver tweets sometimes, but once it misses one it seems to stay that way.

Steps to reproduce the behavior

Create a searchStream with a rule like from:username -is:retweet -is:reply where username tweets a few times a day. Keep connection open, wait until it stops delivering tweets.

Maybe I'm wrong to assume that I should be able to get every new tweet by a user while the connection is open?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant