-
Notifications
You must be signed in to change notification settings - Fork 42
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
Error: Bad token #38
Comments
Here's what I do but it's not ideal, I have a problem of tweet stream stopping for a while. I think it might be getting throttled because I am reconnecting every time after these bad token errors.
|
The problem is twitter is now sending parts of tweets on different chunks. Some time ago they sent full tweets on every chunk. I'll fix it for the next version. |
@danzajdband Any news? :) |
I'll review it at weekend. Sorry for the delay. On Fri, May 16, 2014 at 4:53 AM, Fabrizio Codello
Dan Zajdband |
when the new version is coming plz ? |
Yeah. when? :P |
haha. I'll forget about this. If it's still persisting I'll take a look but help is welcomed. |
Hi,
sometimes I have these errors on the stream and the app stops to retrieve tweets from the streaming API, the process is still running though.
https://gist.github.com/Fabryz/3f244dd3f47a3423ed06
I think that the problem may rely in:
Is there a way to just skip this kind of event and let the stream go on? Without having to use the reconnection
The text was updated successfully, but these errors were encountered: