On Aug 27, 11:16 am, Matt Harris thematthar...@twitter.com wrote:
To allow us to track the issue and to make sure it gets fixed can you
file a bug report on our issues list:
http://code.google.com/p/twitter-api/issues/list
http://code.google.com/p/twitter-api/issues/detail?id=1827
-- R
--
Thanks! I'll get this looked at.
Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Aug 27, 2010, at 5:27, Richard Barnett richard.d.barn...@gmail.com wrote:
On Aug 27, 11:16 am, Matt Harris thematthar...@twitter.com wrote:
To allow us to track the issue and to make
Thanks for finding this one. It's definitely not great this happens.
To allow us to track the issue and to make sure it gets fixed can you
file a bug report on our issues list:
http://code.google.com/p/twitter-api/issues/list
thanks,
Matt
On Wed, Aug 25, 2010 at 9:55 PM, Richard Barnett
I would second the request. Not necessarily for every possible error
message, but at least for the structure of error messages.
Currently, the documentation shows one example of an XML error
response and seems a bit non-committal that this is the canonical
structure of an error response (using
