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