This sounds like the same issue many of us have been reporting where we get back HTML data instead of the expected JSON or XML response... I expect if you added logging to collect the raw response you would find it looks like the responses detailed in the tickets below... We get a similar "parsing" error from our app when this HTML response comes back from twitter. As you are also running on a mobile device it will be hard for you to generate the information twitter is requesting to correct this problem.. If you find a way to collect all the information they are asking for, please share it with us so that we can all provide as much data as they need.
http://code.google.com/p/twitter-api/issues/detail?id=1014 http://code.google.com/p/twitter-api/issues/detail?id=1015 http://code.google.com/p/twitter-api/issues/detail?id=968 Twitter team has been asking for the IP address connection from, the account(s) used, a curl(1) -vvv trace, and a tcpdump of the failure to be sent to [email protected]. --Naveen A. On Sep 9, 12:02 pm, Craig Hockenberry <[email protected]> wrote: > We're seeing a weird error occur with the API in the past few days: > every so often, users will get malformed JSON data. From our app, the > following message is displayed: > > <http://files.iconfactory.net/craig/bugs/TwitterYAJL.jpg> > > That error occurs when the JSON data can't be parsed. > > I'd like to create an issue on Google Code, but this problem is > extremely intermittent. Personally, I only saw it a few times when I > was using the Search API. By the time I was able to debug the data > being returned by the connection, the results had returned to normal. > > Without any debugging info, the problem felt like I was temporarily on > a server that producing bad data. After a few refreshes, I found my > way to a server that produced good data. > > I'd like to know if anyone else has been seeing malformed JSON or if > there's any way to reliably reproduce the bad results. > > Thanks! > > -ch
