We did make a change last night that enforced that oauth_timestamps could not be in the future (previously we only validated that they weren't in the past).
Ensure that your oauth_timestamp is always within 5 minutes of api.twitter.com, regardless of the time within the system environment you're executing requests. Taylor On Wed, Sep 1, 2010 at 10:03 AM, Dewald Pretorius <dpr...@gmail.com> wrote: > I'm seeing a similar thing. Some of my users who have been OAuth > authorized for many weeks now suddenly get an invalid OAuth signature. > > On Sep 1, 1:59 pm, mostafa farghaly <keepon...@gmail.com> wrote: > > Hi, > > i switched to oauth since 2 weeks or so, and deprecated basic auth > > completely, and all my client users upgrade, and the app stats show > > that every thing is fine and they're enjoying oauth, yesterday i get > > the message failed to validate oauth signature ...., and all my client > > users report the same message, i believe that the application my be > > black listed because i do alot of requests during my development of > > iphone app? plz help. > > -- > 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 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
