Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Twitter Development Talk
Home
About this group
Join this group
Message from discussion oauth status update returning error 401 invalid / used nonce
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Taylor Singletary  
View profile  
 More options Jun 11 2010, 8:53 pm
From: Taylor Singletary <taylorsinglet...@twitter.com>
Date: Fri, 11 Jun 2010 17:53:50 -0700
Local: Fri, Jun 11 2010 8:53 pm
Subject: Re: [twitter-dev] oauth status update returning error 401 invalid / used nonce
Print | View thread | Show original | Report this message | Find messages by this author
xAuth in this case, I think, is unrelated to the issue. If you can use
a different key and use the "my token" feature to get your access
token, then try to tweet using that token, it will sufficiently
express the problem I think.

Taylor

On Jun 11, 2010, at 2:48 PM, Craig <chanson9...@gmail.com> wrote:

> Hello,

> I have an iphone app that is using xauth.  I am able to obtain the
> access token with no problem at all.  When I go to post a status
> update, I receive an invalid / used nonce error.  It can't actually be
> a used nonce since I have checked this multiple times.  Here are the
> details of the post:

> url:
> http://api.twitter.com/1/statuses/update.xml

> signature base string:
> POST&http%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses
> %2Fupdate.xml&oauth_consumer_key%3Dmyconsumerkey%26oauth_nonce
> %3D397vi5Ug1YHC3UAVUAoB%26oauth_signature_method%3DHMAC-
> SHA1%26oauth_timestamp%3D1276292596%26oauth_token%3Dmytoken
> %26oauth_version%3D1.0%26status%3Dmy%2520tweet

> Authorization header:
> OAuth oauth_nonce="397vi5Ug1YHC3UAVUAoB", oauth_signature_method="HMAC-
> SHA1", oauth_timestamp="1276292596",
> oauth_consumer_key="myconsumerkey", oauth_token="mytoken",
> oauth_signature="yOh2zQPGDBlVEP5cDWhjddQWTLc%3D", oauth_version="1.0"

> Content-Type:
> [request setValue:@"application/x-www-form-urlencoded"
> forHTTPHeaderField:@"Content-Type"];

> I can see no reason why this shouldn't work.  Any help would be
> greatly appreciated!

> Thanks,
> Craig


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google