Calling stream.destroy() does not emit any events about twitter-lite HOT 5 CLOSED

I'm running into the same problem. When I use stream.destroy() and wait 30 seconds to reconnect I seem to get an error 420 on the third connection without fail, but if I stop and restart the stream from the command line, it seems to work just fine.

from twitter-lite.

Anyone get further with this?

from twitter-lite.

@roowilliams @danstronoid @ImTheDeveloper So this may not be the reason, but have you both looked at https://developer.twitter.com/en/docs/tweets/filter-realtime/guides/connecting? In the Reconnecting section, the docs state that after receiving HTTP 420 errors you should do the following:

Back off exponentially for HTTP 420 errors. Start with a 1 minute wait and double each attempt. Note that every HTTP 420 received increases the time you must wait until rate limiting will no longer will be in effect for your account.

The first thing I would try and do is follow their recommendation for backing off exponentially, since it seems like you all have only tried to wait ~30 seconds.

Alternatively, the errors may be arising from the fact you're clients are just being rate-limited by Twitter (see the Rate limiting section in that same link).

In any event, please let me know if this helps!

from twitter-lite.

I'm going to close this issue for now. If anyone is still experiencing it, please feel free to reach out and I'll re-open.

from twitter-lite.

I'm facing this issue again, has anyone found the solution ?

from twitter-lite.