hi I have experiened this .how to avoid this ?
On Apr 14, 12:31 am, Dimebrain <[email protected]> wrote: > Hello, > > Recently, I have noticed that if I attempt to do a > requesttoken/accesstokenexchange, i.e. a new application OAuth workflow, I > always > fail with "Failed to validate oauth signature andtoken" from Twitter > if the application has already been successfully authorized in a > previous workflow. If I revoke the application and try again, it works > fine. > > Now I understand the motive for that, to avoid unnecessary load of > having apps that perform the OAuth exchange on every user session, but > this was not how it was working before. Did I miss an API > announcement? My app persists thetoken, so for me this isn't the end > of the world. > > First I'd like to know if this is expected behavior. I can faithfully > reproduce the scenario of noaccess, gainaccess, try to gainaccess > again and fail, revokeaccessand try again to succeed. My expectation > is the OAuth process works even if the user has already grantedaccess > to the user. > > Anyone experiencing this right now?
