[twitter-dev] Re: Statuses/destroy is returning 400 even though tweet is deleted sucessfully

2009-08-29 Thread darasion
I have the same problem right now. Exactly as above all. On Aug 28, 5:03 am, Naveen Ayyagari knig...@gmail.com wrote: I am seeing this issue as well. Users are reporting it very frequently   now... At first I thought it was a bug in the client, but it happens every   time I try to delete a

[twitter-dev] Re: Statuses/destroy is returning 400 even though tweet is deleted sucessfully

2009-08-27 Thread Naveen Ayyagari
I am seeing this issue as well. Users are reporting it very frequently now... At first I thought it was a bug in the client, but it happens every time I try to delete a status right now, and it has become one of the highest reported bugs in out app. Twitter reports 400 with the JSON

[twitter-dev] Re: Statuses/destroy is returning 400 even though tweet is deleted sucessfully

2009-08-26 Thread Tom Nichols
+1 - I am experiencing the same problem. I'm running Twitter API requests as part of a unit test for my code (HTTPBuilder- http://groovy.codehaus.org/modules/http-builder/). This has always worked fine up until a couple weeks ago. Looks like there is a bug report here:

[twitter-dev] Re: Statuses/destroy is returning 400 even though tweet is deleted sucessfully

2009-08-19 Thread srikanth reddy
yes i too encountered this (both status/destroy and direct_messages/destroy are giving 400 error but the status gets deleted successfully. The response text says something like somehow we could not delete this tweet. On Wed, Aug 19, 2009 at 3:38 PM, deepikagupta deepikaggu...@gmail.comwrote: