On 8/13/10 11:58 PM, Gurpartap Singh wrote: > Will talk in points: > > # An existing OAuth app which already has xAuth access, works > perfectly in the implementation. > > # Created a new OAuth app with Twitter. Got xAuth access for it > through email. > > # Replaced the implementation's API keys to the new OAuth app's API > keys. > > # Getting 401 error on OAuth echo attempt with Twitpic. > > # If the original API key is used, it works fine. > > # "Use Twitter for login" is checked in new OAuth app's settings. > > # Requested Twitter to look if it really has access. They verified it > to have xAuth access. > > Where's the catch?
Yikes, points. I prefer numbers :-) 1. Don't use the same user keys for different consumer keys. 2. OAuth echo is not dependent on xAuth 3. If your application is a desktop application, you should not check "Use Twitter for login". Tom
