Open saidmmm2002 opened 14 years ago
Never mind, fixed the issue. Thank you
Do you mind sharing how you fixed the issue? Was it a XAuthTwitterEngine problem?
Yes, I'd also like to know how you fixed it.
Me, too ;-)
I just went to the original implementation at git://github.com/norio-nomura/ntlniph.git
IMPORTANT: READ THIS FIRST: http://aralbalkan.com/3133 - it will keep you from banging your head against the wall since you have to explicitly ask Twitter to activate xAuth for your app! And also read this: http://apiwiki.twitter.com/Twitter-REST-API-Method:-oauth-access_token-for-xAuth
Sorry, i was looking through norio nomura's implementation, but that seems to be using basic auth. What exactly did you do?
At the moment authentication is going through regular OAuth, i.e. through a webview that brings up Twitter's own authentication page.
Hi, Great Code. When a password has a special character such as +, this causes the xAuth process to fail. I am aware that I need to url-encode it before (or maybe not?), anyways I tried both cases, but no luck. I know it is from the + sign, but still cant get it to work. Note: the password works fine when using regular Basic authentication
Any comments? or help would be great. Thanks