Bingo!! Thanks so much Abraham!! My server time was out by a few
hours, synced it up and I get results just like expected!!
On May 16, 10:31 am, Abraham Williams <4bra...@gmail.com> wrote:
> Make sure your clock is properly synced. If it is more the a few minutes off
> it can cause the same error
The user was authenticating with firefox and this plugin:
https://addons.mozilla.org/en-US/firefox/addon/750
Desactivating the plugin solved the problem.
Hoping that will be useful, if someone already experienced a similar
case,
Arnaud.
On Oct 22, 10:58 pm, Arnaud Meunier
wrote:
> Hi,
>
> One
Did you configure a callback for your application OR passing it when getting
the request token?
On Sun, Aug 9, 2009 at 3:49 PM, Andy wrote:
>
> We're still having trouble with oAuth. When sending users to get
> oAuth'd, they are given a code (like a desktop app) rather then being
> redirected to
RRR
-Original Message-
From: João Pereira
Date: Wed, 17 Jun 2009 00:01:56
To:
Subject: [twitter-dev] Re: OAuth issue
I used this:
accessToken = twitter.getOAuthAccessToken(
preAuthorizedTwitterAccount.getOAuthToken
I used this:
accessToken = twitter.getOAuthAccessToken(
preAuthorizedTwitterAccount.getOAuthToken(),
preAuthorizedTwitterAccount.getOAuthTokenSecret(),
pinCode);
twitter.setOAuthAccessToken(accessToken);
twitterUser = twitter.v
As a corollary to this, are there any downloadable code examples out there
that implement the pin-based OAuth now? Everything I've found seems to be
failing on the lack of PIN support, and I'd like to be able to trace what's
going on through wireshark to debug this myself. Thanks!
On Mon, Jun 15,
