I am getting this:

    [request] => /1/statuses/update.json
    [error] => Status is a duplicate.

On Nov 30, 12:09 am, Abraham Williams <4bra...@gmail.com> wrote:
> What does $connection->http_code return after calling $connection->post when
> you get the duplicate error message?
>
> Abraham
> -------------
> Abraham Williams | Hacker Advocate | abrah.am
> @abraham <https://twitter.com/abraham> | github.com/abraham | blog.abrah.am
> This email is: [ ] shareable [x] ask first [ ] private.
>
> On Mon, Nov 29, 2010 at 23:58, EastSideDev <eastside...@gmail.com> wrote:
> > I double-checked my code, and I'm only calling statuses/update once:
>
> >        $connection = new TwitterOAuth($ctck, $ctcks, $ot,$ots);
> >        $opResult = $connection->post('statuses/update',
> > array('status' => $statusUpdate), TRUE);
> >        if (!$opResult['id']) {
> >            $msgText .= $opResult['error']." ";
> >        }
>
> > This is code that was working fine, until recently (no changes).
>
> > On Nov 29, 10:00 pm, Abraham Williams <4bra...@gmail.com> wrote:
> > > It sound to me like your code might be making the same API request twice.
> > > This would result in the status getting posted and the error message you
> > end
> > > up with.
>
> > > If you are commonly creating statuses with the same text it might just
> > seem
> > > like a new status is getting posted when they are not.
>
> > > Abraham
> > > -------------
> > > Abraham Williams | Hacker Advocate | abrah.am
> > > @abraham <https://twitter.com/abraham> | github.com/abraham |
> > blog.abrah.am
> > > This email is: [ ] shareable [x] ask first [ ] private.
>
> > > On Mon, Nov 29, 2010 at 20:18, EastSideDev <eastside...@gmail.com>
> > wrote:
> > > > I have an application that uses oAuth to post a tweet on behalf of a
> > > > user. I noticed today that when I do a status update, I'm getting a
> > > > "Status is a duplicate" error message, when in fact the status posted
> > > > correctly.
>
> > > > I have not changed my code, and I am using the Twitter oAuth library
> > > > (same code been working fine since June). Are we experiencing some API
> > > > issues?
>
> > > > --
> > > > Twitter developer documentation and resources:
> >http://dev.twitter.com/doc
> > > > API updates via Twitter:http://twitter.com/twitterapi
> > > > Issues/Enhancements Tracker:
> > > >http://code.google.com/p/twitter-api/issues/list
> > > > Change your membership to this group:
> > > >http://groups.google.com/group/twitter-development-talk
>
> > --
> > Twitter developer documentation and resources:http://dev.twitter.com/doc
> > API updates via Twitter:http://twitter.com/twitterapi
> > Issues/Enhancements Tracker:
> >http://code.google.com/p/twitter-api/issues/list
> > Change your membership to this group:
> >http://groups.google.com/group/twitter-development-talk

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Reply via email to