[twitter-dev] Re: oAuth reporting a status update error when none exists
This is how I knew that the post worked: I went to the account and the
post was there. I deleted it, and tried again, and the post was there
as well, and the same happened every time I deleted and re-tested.
The error message is courtesy of the oAuth class lib, and I'm passing
it as is. I posted the code earlier in this thread, but he it is
again:
$connection = new TwitterOAuth($ctck, $ctcks, $ot,$ots);
$opResult = $connection-post('statuses/update',
array('status' = $statusUpdate), TRUE);
if (!$opResult['id']) {
$msgText .= $opResult['error']. ;
}
On Nov 30, 5:54 pm, Matt Harris thematthar...@twitter.com wrote:
Hi,
So the 403 duplicate status means the message you are sending is the same as
the last message in the users timeline.
When you say the post is posting correctly, how are you validating that this
has happened?
Also, can you show an example request that you are making, for example:
http://api.twitter.com/1/statuses/update.json
POST: status=my text
Values from a real request would be helpful to identify what could be
causing us to think the update is a duplicate.
Best,
@themattharris
Developer Advocate, Twitterhttp://twitter.com/themattharris
On Tue, Nov 30, 2010 at 5:34 PM, EastSideDev eastside...@gmail.com wrote:
I am not doing any duplicates. I tested the app on a brand new Twitter
account, and did only a single status update. The update was actually
done, but I am still receiving the error message. I implemented
temporary fix (ignore the error code), but that's an ugly solution.
On Nov 30, 5:26 pm, Bess bess...@gmail.com wrote:
I am afraid Twitter has added this error - don't allow any duplicate
tweet at least from Twitter API. I have to add random text to bypass
this 403 error.
On Nov 30, 11:11 am, EastSideDev eastside...@gmail.com wrote:
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:
Re: [twitter-dev] Re: oAuth reporting a status update error when none exists
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
[twitter-dev] Re: oAuth reporting a status update error when none exists
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
[twitter-dev] Re: oAuth reporting a status update error when none exists
I am afraid Twitter has added this error - don't allow any duplicate
tweet at least from Twitter API. I have to add random text to bypass
this 403 error.
On Nov 30, 11:11 am, EastSideDev eastside...@gmail.com wrote:
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
[twitter-dev] Re: oAuth reporting a status update error when none exists
I am not doing any duplicates. I tested the app on a brand new Twitter
account, and did only a single status update. The update was actually
done, but I am still receiving the error message. I implemented
temporary fix (ignore the error code), but that's an ugly solution.
On Nov 30, 5:26 pm, Bess bess...@gmail.com wrote:
I am afraid Twitter has added this error - don't allow any duplicate
tweet at least from Twitter API. I have to add random text to bypass
this 403 error.
On Nov 30, 11:11 am, EastSideDev eastside...@gmail.com wrote:
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
Re: [twitter-dev] Re: oAuth reporting a status update error when none exists
Hi,
So the 403 duplicate status means the message you are sending is the same as
the last message in the users timeline.
When you say the post is posting correctly, how are you validating that this
has happened?
Also, can you show an example request that you are making, for example:
http://api.twitter.com/1/statuses/update.json
POST: status=my text
Values from a real request would be helpful to identify what could be
causing us to think the update is a duplicate.
Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Tue, Nov 30, 2010 at 5:34 PM, EastSideDev eastside...@gmail.com wrote:
I am not doing any duplicates. I tested the app on a brand new Twitter
account, and did only a single status update. The update was actually
done, but I am still receiving the error message. I implemented
temporary fix (ignore the error code), but that's an ugly solution.
On Nov 30, 5:26 pm, Bess bess...@gmail.com wrote:
I am afraid Twitter has added this error - don't allow any duplicate
tweet at least from Twitter API. I have to add random text to bypass
this 403 error.
On Nov 30, 11:11 am, EastSideDev eastside...@gmail.com wrote:
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
--
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-dev] Re: oAuth reporting a status update error when none exists
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
