*Update: Twitter have announced that they’ll actively begin working towards resolving the issue in April ’15. We’ll be sure to keep you updated with any developments.*
We recently noticed that search requests using our geolocation filter were returning around 0-20 search results, rather than the usual 50 or 100.
Having investigated this issue further and spoken with other developers, we have found that unfortunately there is an issue with Twitter’s API returning location-based results. This means that when you setup a geolocation search, or view the results of an alert you have previously setup, only a few results are being returned, even when there are more available. Understandably, some of our users are concerned about this affecting the results that they see and the number of tweets that they can respond to.
The latest response we have received from Twitter personnel on fixing this issue is as below:
As we said, we have resolved part of the issue, but the fallback to profile location for geo searches has not yet been finalised. This is part of a significant set of changes on the search backend, so it may take some time for the second part of the issue to be resolved. Unfortunately we need to set an expectation of weeks rather than days before a full solution is likely to be in place. We are very sorry for the inconvenience this is causing. This is obviously a very frustrating situation for you all in our developer community, but there’s only a limited rate at which we can get this particular issue finalised as there are more parts in motion than may be apparent. Thank you so much for your patience and understanding!
We will stay in contact with them and try to have the issue resolved as soon as possible but unfortunately, until they fix this issue with the API our results are tied to what is being returned.
Apologies for any inconvenience our users may experience in this time and as soon as we have a further update we will be sure to update you.
The Twilert team