Search/tweets v1.1 ignoring max_id


#1

I was using the version 1 of the tweet search and was working properly. I just migrated to the version 1.1 with Oauth, and it is not working properly. It is ignoring the “max_id” variable, and so there is duplication of results.

Here is what my search array looks like:
‘max_id’=>‘LAST_ID’, ‘count’ => ‘100’, ‘result_type’ => ‘recent’, ‘q’ => ‘SEARCH TERM’

According to the documentation, setting a “max_id” should bring up all tweets made previous to the “LAST_ID” tweet specified.

However this is not what is happening. It is ignoring “max_id” and just giving me the most recent.

I even tried leaving off the “result_type” but I still get the same result.

Here is a search that I did for “Bible”… (I am truncating this down to the first and last result)

Search 1, (No Max ID)

tweet id: 322407976528932864 (Thu Apr 11 17:57:06 +0000 2013)

tweet id: 322407376839905280 (Thu Apr 11 17:54:43 +0000 2013)

Search 2 (shortly thereafter), (Max ID = 322407376839905280)

tweet id: 322408173019488256 (Thu Apr 11 17:57:53 +0000 2013)

tweet id: 322408553266683904 (Thu Apr 11 17:59:23 +0000 2013)

Any ideas?

Thanks,


#2

Just to clarify, what I posted was not in numerical order, I just showed the results in the order they where returned. For the Max ID, I took the lowest ID returned.