At first glance, it looks like the host parameter does not match your oauth_callback.
On Jul 13, 7:16 pm, bo <bost...@gmail.com> wrote: > I have a Twitter app and I need user of my Android application to > authorize its use. I'm at the point where I can call Twitter app page > in the browser from my code and successfully authorize. However, the > callback seem not to be working, I end up with the confirmation > message and PIN in the browser but my Android activity is never called > (onResume is not triggered) and browser just stays open. Here's what I > have > > 1. Twitter URL which starts activity in the external > browser:http://twitter.com/oauth/authorize?oauth_token=actualtokenhere&oauth_... > 2. In my activity definition I have this intent-filter > > <intent-filter> > <action > android:name="android.intent.action.VIEW" /> > <category > android:name="android.intent.category.DEFAULT" /> > <category > android:name="android.intent.category.BROWSABLE" /> > <data android:scheme="myapp" android:host="twitt"/> > </intent-filter> > > 3. As I stated - I get confirmation but not redirect so the Android > app is never called back --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
