Hi,
I've used CFUUID's (
http://developer.apple.com/mac/library/documentation/CoreFoundation/Reference/CFUUIDRef/Reference/reference.html).
Apple's documentation states they use a combination of ethernet address and
time to generate a unique id.
George
On Fri, Jul 30, 2010 at 8:53 PM, Tom
Hello Taylor!
I don't think the error has something to do with the access token,
because sometimes the error is thrown during my request to retrieve a
Request Token.
I'm afraid the error has something to do with encodings or something
similar.
Also, I would like to know if there is an advised
Hi Mounir,
I'm using this code myself, maybe you can transform it to the language
you use.
http://www.devonferns.com/cocoablog/?p=45
Tom
On Jul 30, 11:32 am, Mounir Regragui reg.mou...@gmail.com wrote:
Hello Taylor!
I don't think the error has something to do with the access token,
because
Hi Taylor.
First of all, thank you for the help :)
I am almost sure that this is not a Data issue. As I told you, this
error happens randomly (unhopefully, it happens very often, 80% of my
API calls return with this error today). Also, I did not modify the
code I used before, and it was just
I would recommend adding some kind of logging so that when you do get a
failed request, you know the following:
the POST body included in the failed request and the signature base string
prior to signing for OAuth.
There's a chance that a certain sequence of characters and UTF-8 characters
might
Hey,
We are getting this error, but Twitter is also sending back a valid
response.
To clarify, if we post an update, the update appears in the timeline
but twitter returns a 401 error code (with the nonce message).
Same applies to friends timeline sometimes too.
Cheers
David
We have a weird error condition in the OAuth implementation right now that
throws invalid nonce errors when it's not necessarily the issue. We're still
tracking what exactly causes this down, but believe that it's not applicable
to the OAuth implementation rewrite we'll soon be rolling out.
In
Anyone have any ideas about this? I'm really not sure where to go or
what to check from here, and I need to get this taken care of. Any
information would be appreciated!
Cory,
I have had similar issues. When you get that 401 error, you need to
back off for a second or two, recalculate the nonce, and then resubmit
the request.
On Apr 28, 10:52 pm, Cory cory.imdi...@gmail.com wrote:
Anyone have any ideas about this? I'm really not sure where to go or
what to
My trial has worked so far today... not a single invalid nonce
error but it's only been 12 hours
Simon
On Aug 12, 12:59 pm, Rob O'Brien r...@zepoid.com wrote:
The interesting thing with my situation is that I'm still in development, so
there's only a single person (me) hitting the app.
No, my nonce is definately new every time. Surely if there was
something wrong with the way it was being generated it would error
during requestToken/accessToken/VerifyCredentials too?? All the code
ive looked through is doing it exactly the same way. Is the 'status'
parameter being used just
Ive only been trying since friday...do you have any problems calling
verifyCredentials or any other methods??
On Aug 10, 4:43 pm, Rob O'Brien r...@zepoid.com wrote:
I'm getting the same response. All weekend, I chalked it up to being an
issue during recovery of the systems, but I'm still
For our app, we successfully call request_token from our server. When
we then call statuses/update from the client, we get a 401 'Invalid /
used nonce' response. If the request_token call comes directly from
the client, the update call succeeds.
The nonces have been sanity checked and are
We have also been seeing similar behaviour for our iPhone app based on
MGTwitterEngine-1.0.8-OAuth.
If we call request_token from the client followed by statuses/update,
everything works ok. However, if we send the request_token from our
server, then statuses/update from the client, a 401
We're having the same issue in our app, occurs sporadically in our
logs - but I believe the cause with us is that:
We're generating nonce values as a timestamp seeded sequence of random
numbers
We're creating an instance of the Oauth class that does this for each
logged in user for the app
I'm getting the same response. All weekend, I chalked it up to being an
issue during recovery of the systems, but I'm still seeing it this morning
on 100% of my calls. It was working before the attack.
401:Authentication credentials were missing or incorrect. ?xml
version=1.0 encoding=UTF-8?
On Mon, 10 Aug 2009 04:14:43 -0700 (PDT)
graceawalker grace_blo...@hotmail.com wrote:
I am calling and getting the whole way up to getting the access token
just fine in my app (one im writing myself in c#), but when i try and
call the update status URL im getting an 'Invalid/used nonce' error
17 matches
Mail list logo
