Writing Twitter Client using OAuth: Callback fails

by Samuh » Mon, 15 Feb 2010 21:14:08 GMT

Sponsored Links
 I am working on an Android application which is to serve as a simple
Twitter client. I am using OAuth for authorization and have registered
my application with Twitter as new OAuth client.
Now when the user authorizes the application, I expect to be taken to
the Callback URL(which is pointing to my application); but this is not

My Problem along with source code is described in detail here:
 http://stackoverflow.com/questions/2199357/oauth-twitter-on-android-callback-fails )

The following intent is launched post authorization:
Intent {
act=android.intent.action.VIEW dat= http://twitter.com/oauth/authorize? 
cmp=com.android.browser/.BrowserActivity }

Some how, the hypothetical URL, I provided while registering my
application, gets called.

Please let me know if I am missing something here...



Writing Twitter Client using OAuth: Callback fails

by Samuh » Mon, 15 Feb 2010 21:37:28 GMT

 I made a mistake above.

The following intent is launched for authorization:
Intent {
act=android.intent.action.VIEW dat= http://twitter.com/oauth/ 
cmp=com.android.browser/.BrowserActivity }


Sponsored Links

Other Threads

1. RIL accessing and ways of doing this


My project needs to read data from base band. Some of data from base
band is read by RIL and we are planning to access base band processor
code(which we might get from OEM) with one of our own system service.
No at this point i have a concern...

I think RIL communicate with Base Band and read most of the data..so i
am planning to expand the RIL funciotnality to read all the data i
needed from Base Band and give it to me...
So is this possible??? Can i expand RIL to get the my required data???

If yes then here is my second question:
Currently telephony manager reads data from RIL..and pass it to
applicaiotns/Services in upper layers.
Now if i want my services in applicaiotn layer to read data from RIL
then how can we do it???

Can you help on this??



2. DNS settings not working in android 1.6 x86 porting

In settings, while configuring eth0 with static ip information, the
dns nameserver values are not updated to

So some websites which expects the nameserver details crashes while
calling  gethostbyaddr.
If we manually add the nameserver ip to the resolve.conf, then the
crash is not observed

for example, if we launch calender from google.com--> more options.

Following is the logcat logs for this issue.
E/InetAddress( 1327): gethostbyaddr: getnameinfo: unknown host Tn
W/dalvikvm( 1327): threadid=53: thread exiting with uncaught exception
E/AndroidRuntime( 1327): Uncaught handler: thread http1 exiting due to
E/AndroidRuntime( 1327):
E/AndroidRuntime( 1327):        at
E/AndroidRuntime( 1327):        at
E/AndroidRuntime( 1327):        at
E/AndroidRuntime( 1327):        at
E/AndroidRuntime( 1327):        at
E/AndroidRuntime( 1327):        at
E/AndroidRuntime( 1327):        at
I/Process (  994): Sending signal. PID: 1327 SIG:
I/dalvikvm( 1327): threadid=7: reacting to signal
I/dalvikvm( 1327): Wrote stack trace to '/data/anr/traces.txt'

Can anybody post a  help to resolve this issue.

unsubscribe: android-porting+unsubscr...@googlegroups.com

3. How to get ListView behavior inside a ScrollView?

4. AV sync issue in real media porting

5. TextView cuts off part of an initial capital "J"

6. AIDL: Stub class methods not being called

7. change booting Monkey image.