Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

As an Android developer who's been struggling to get OAuth 1.x working for the past few weeks in his spare time, I wish I could say it's any better on this side of the pond. We have some marginal improvements since we can register our own app to be the receiver of the OAuth callback (using Intents). But it's still excessively complicated.


Last summer I had some issues getting OAuth working with the Twitter API for Android apps. I ended up using the signpost library. I posted my results with instructions here: https://github.com/adelevie/AndroidOAuth. Maybe it will help you.


Similarly here https://github.com/vitalius/Twiturr/blob/master/src/com/twit...

I also find using WebView activity for launching twitter authentication page is more robust in terms of controlling activity focus.


Thanks, I'll definitely take a look. My issues now mostly stem from attempting to integrate the OAuth solution that I have working into the SyncAdapter / ContentProvider abstraction that Android provides.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: