Hey everyone! Recently got my first Android app under my belt after a semi-laborious process, but anything worthwhile usually is. ;) Currently, I'm also working on an iOS app & I'm also updating a previous iOS app. Both apps use the Custom URL plugin to access certain Twitter hashtags. However, the search results no longer display (and they used to). The first time I set up the app, the URL was in the following form "http://www.twitter.com/#physed" for example. This worked just fine. When I test it now, I get a Twitter page with a message saying "Sorry, this page does not exist". I tried changing it to the official search result URL "http://www.twitter.com/search?q=physed/". I didn't get the same error message as before, but I didn't get any results either and instead receive a page of "Trends" on Twitter. Any ideas on how to resolve this issue? This only happens when the URL is for search results - Twitter URL associated to a Twitter account work just fine. Thank you! -Nicholas

Hi Nicholas, Twitter changed their API in July from memory - to just json data. As such it seemed to change/break quite a few things!! On iOS I am currently using the PHP script below to change the json data to an RSS feed and then using the BTM or Red dog RSS plugin. This is the script home https://github.com/thomasyung/twitter-json-to-rss On Android I am using the above script to get the RSS and then outputting it as a jquery mobile list using a bit of PHP - not ideal but it does work. The above script is very easy to setup. I am still waiting for the return of an Android RSS reader .. it will make my life so much easier :))) All the best with it! Cheers Darrel

Hey Darrel! Thanks for sharing! Actually, earlier today, I came up with a very funny alternative, which I still don't understand why it works... It involved using bit.ly (although, perhaps other URL shorteners would work?) No matter what I did at first, it wouldn't work. I tried everything from https://www.twitter.com/#physed, http://www.twitter.com/#physed, or even http: OR https: //www.twitter.com/search?q=physed, and so on and so forth. What worked for me was shortening the following link for example through bit.ly: https://twitter.com/#physed In other words, removing the "www." did the trick. Don't ask why, but it works! Thanks again! -Nicholas

Thanks ... good to know! Perhaps hiding behind a shortened URL means that twitter will serve the content regardless? Interesting ... :)