[twitter-dev] Invalid / expired Token error message when trying to update status

2010-10-25 Thread angelsk
I'm using the OAuth token and secret provided in my application
settings for My OAuth Token - this is a personal twitter posting
cron job.

I have exactly the same code in another implementation posting to
another twitter account which is working fine.

However, when I try and update the status of my main account
'angelsk', I get Invalid / expired Token.

Any help would be great.

I've tried:

* Re-copying and pasting the access token / secret and consumer key /
secret
* De-authorising the application on my Connections page and revisiting
the application page to get a new token

Still no luck.

J

-- 
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] Invalid / expired Token error message when trying to update status

2010-10-25 Thread Taylor Singletary
If you create an alternate application with the same account, issue access
tokens for that account, and perform the same test -- does everything work
fine? We've seen some cases where an API key becomes poison but have not
yet been able to determine the cause or a solution. Are there any other
environmental differences?

Taylor

On Sat, Oct 23, 2010 at 3:23 PM, angelsk goo...@jocarter.co.uk wrote:

 I'm using the OAuth token and secret provided in my application
 settings for My OAuth Token - this is a personal twitter posting
 cron job.

 I have exactly the same code in another implementation posting to
 another twitter account which is working fine.

 However, when I try and update the status of my main account
 'angelsk', I get Invalid / expired Token.

 Any help would be great.

 I've tried:

 * Re-copying and pasting the access token / secret and consumer key /
 secret
 * De-authorising the application on my Connections page and revisiting
 the application page to get a new token

 Still no luck.

 J

 --
 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] Invalid / expired Token

2010-10-07 Thread Don Neumann
I'm trying to use the latest twitter-async libraries and can't get
this to work at all. I've registered an application and have the
consumer key and consumer secret and am using some simple code:

include 'epitwitter/EpiOAuth.php';
include 'epitwitter/EpiCurl.php';
include 'epitwitter/EpiTwitter.php';

$twit = new EpiTwitter($consumer_key, $consumer_secret);
$resp = $twit-post_statusesUpdate(array('status' = 'foo'));

And I get this:
PHP Fatal error:  Uncaught exception
'EpiTwitterNotAuthorizedException' with message '{request:/1/
statuses/update.json,error:Invalid / expired Token}' in []:
255

I was using an oauth token and secret which twitter gave me before but
that is unusable now..

-- 
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] Invalid / expired Token

2010-09-06 Thread Rajendra Singh
Hello,

I took the twoleggedtwitter.php example file and added the following
two lines:

   $request = new OAuthRequester(TWITTER_UPDATE_STATUS_API, 'POST',
status=Test);
   $result = $request-doRequest();

However, when I execute it, I get:
Exception:  Request failed with code 401:  {request:/statuses/
update.json,error:Invalid / expired Token}

Can someone help me?  What am I doing wrong?

-- 
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?hl=en


Re: [twitter-dev] Invalid / expired Token

2010-09-06 Thread Taylor Singletary
Twitter doesn't support any two-legged OAuth operations at this time.

Taylor

On Mon, Sep 6, 2010 at 2:44 PM, Tom van der Woerdt i...@tvdw.eu wrote:
 On 9/6/10 10:57 PM, Rajendra Singh wrote:
 Hello,

 I took the twoleggedtwitter.php example file and added the following
 two lines:

-- 
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?hl=en


[twitter-dev] Invalid / expired Token for all calls after successful connection made

2009-03-26 Thread Dimebrain

I am able to consistently exchange the request token for the access
token and see my application in the Connections tab for my account.
However, I'm no longer able to make protected resource requests with
the final token and secret. It worked for me earlier in the evening,
but now is consistently returning Invalid / expired Token for any
authenticated call I make.


[twitter-dev] Invalid / expired Token after authorizing request token

2009-03-18 Thread Dimebrain

Hello,

I'm unit testing my OAuth implementation and am able to obtain a
request token successfully. After obtaining it, I redirect the user to
the authorize URL (with token parameter and no callback) and hang and
wait for a few seconds while I click Allow on the token's redirected
authorization page.

At this stage, I'm under the impression that I should now exchange
that request token (which should be authorized due to my clicking the
big green button) for an access token. I perform my signature hashing
and such based on the access URL, provide the required parameters
including the token, and make my request, but this call consistently
returns Invalid / expired Token.

I'm assuming it can't find the token I'm trying to look up. Am I
looking at this the wrong way?