Same issue here. Mobile app does local caching and was counting on the
since_id not being included in the result set. Unfortunately, I
haven't been capturing request and response logs.
On Sep 23, 9:40 am, James Teters wrote:
> Hello,
>
> This has just appeared in the last few days. When I perfo
Thanks for reporting this. If there is a way for you to capture
request/response logs when this happens it will help our search team
to track this down. Since it is happening inconsistently it may mean
that one of the servers is acting funny, and the HTTP headers could
help track that down.
-Chad
Same thing here, it started to happen since yesterday. When doing
searches with parameter from:username and since_id, sometimes I got
the tweet with since_id back as well.
It only happens some times, not every time, so I suspect it's a bug
other than API change. Any idea?
On Sep 23, 9:40 am, Jam
