I haven't fully read through this thread, but I'd like to throw in my help.

I ran into the same problem (at least the same error) recently and
discovered that the server's system time was incorrect (by about 3 hours).
In some obscure documentation, I found that the timestamp must be within 5
minutes of real time in order for the nonce to be accepted. 

Check your system time, adjust if necessary, and try again. Give it a shot.

Rob
  
  
 

-----Original Message-----
From: twitter-development-talk@googlegroups.com
[mailto:twitter-development-t...@googlegroups.com] On Behalf Of Chad Etzel
Sent: Wednesday, August 26, 2009 7:15 PM
To: twitter-development-talk@googlegroups.com
Subject: [twitter-dev] Re: Keep getting "Invalid / used nonce", even with
new nonce


Hi Jason,

The API endpoint and all other parameters sent with the request would
be helpful.

Thanks,
-Chad

On Wed, Aug 26, 2009 at 7:15 PM, Jason Martin<legos.j...@gmail.com> wrote:
>
> Aright, here's one set of request/response headers:
>
> Request:
> {
>    Authorization = "OAuth realm='',
> oauth_consumer_key='tJdfiGin0BMT7Qugbj787g',
> oauth_signature_method='HMAC-SHA1',
> oauth_signature='J%2BgLcaHUvLolHv2eZdpDJWSzumM%3D',
> oauth_timestamp='1251325616',
> oauth_nonce='83a0141dd608569dc22b037e3b5fbe606ebd845f',
> oauth_version='1.0'";
> }
>
> Response:
> {
>    "Cache-Control" = "no-cache, max-age=300";
>    Connection = close;
>    "Content-Encoding" = gzip;
>    "Content-Length" = 88;
>    "Content-Type" = "application/json; charset=utf-8";
>    Date = "Wed, 26 Aug 2009 22:26:58 GMT";
>    Expires = "Wed, 26 Aug 2009 22:31:58 GMT";
>    Server = hi;
>    "Set-Cookie" =
>
"_twitter_sess=BAh7ByIKZmxhc2hJQzonQWN0aW9uQ29udHJvbGxlcjo6Rmxhc2g6OkZsYXNo%
250ASGFzaHsABjoKQHVzZWR7ADoHaWQiJWEzYzdlN2I5NzhhMmVjZGI1YWVjYTU4%250AODgxYjc
5YmE2--64d7889886ab87d71ab67936215e1d51fcb99de9;
> domain=.twitter.com; path=/";
>    Status = "401 Unauthorized";
>    Vary = "Accept-Encoding";
>    "Www-Authenticate" = "Basic realm='Twitter API'";
> }
>
> And the response body:
>
> {"request":"/statuses/replies.json","error":"Invalid / used nonce"}
>
> Lemme know if you need anything else.
>
>  - Jason
>
> On Aug 26, 2009, at 6:05 PM, Chad Etzel wrote:
>
>>
>> The request/response headers specifically, but the more info the better
>> usually.
>> -Chad
>>
>> On Wed, Aug 26, 2009 at 5:58 PM, Jason Martin<legos.j...@gmail.com>
wrote:
>>>
>>> Anything specific you need to look at? Or do just want me to just paste
>>> in
>>> what's been sent  and what's been received?
>>>
>>>  - Jason
>>>
>>> On Aug 26, 2009, at 5:46 PM, Chad Etzel wrote:
>>>
>>>>
>>>> Hi Jason,
>>>>
>>>> If you have traces of the HTTP request/responses that will help
>>>> diagnose what is going on.
>>>>
>>>> -Chad
>>>>
>>>> On Wed, Aug 26, 2009 at 12:51 PM, Jason Martin<legos.j...@gmail.com>
>>>> wrote:
>>>>>
>>>>> I'm always getting the "Invalid / used nonce" error, even though I am
>>>>> providing a new nonce. I am 100% sure my code works, because if I
>>>>> remove my user cache, and the screen pops up to log into Twitter, then
>>>>> I immediately go to the user's timeline in my app, and everything
>>>>> loads: followed timeline, mentions, and DMs. However, when I close my
>>>>> app, and relaunch it, and go back the user's timeline again (same
>>>>> things are loaded: followed timeline, mentions, and DMs), but I get
>>>>> that "Invalid / user nonce" error. If my method of creating a nonce
>>>>> isn't always going to give me an unused one, what will? I'm currently
>>>>> encrypting a UUID I get from the iPhone OS, and I've tried encrypting
>>>>> the current time in seconds. Any other methods I should be trying?
>>>>>
>>>>>  - Jason
>>>>>
>>>
>>>
>
>

Reply via email to