brione-zz / brion-learns-oauth Goto Github PK

The OAuthActivity doesn't handle the case where it resumes without getting a new key. It used to start the main activity. It just needs to know when to finish.

Get rid of dead development branches.

A new HttpClient is created for every interaction. This needs to be fixed. Research some way to make it better.

HttpUrlConnection has been recommended for use in post Gingerbread implementations.

In my RL job we found that it regressed in the very latest version to have the same problems as pre-Honeycomb and we had to use a version-specific workaround.

This has all changed so we are required to both have an application Url registered with Twitter, we must also pass that same Url in order for things to work.

All that will need to be updated.

Hello sir,

I have downloaded this example and tried it out and by using this example, status is being updated successfully on twitter. But whats the problem i am facing is whenever i try to search the part of status text at search.twitter.com URL (For example, status is "This is the demo status udpate by paresh and if i try to search update or paresh or any word at search.twitter.com then it is not showing the same status but showing other statuses containing the same word and which i had posted using the actual twitter application.)

In short, Problem: want to search about the status(posted by this example) at www.search.twitter.com.

So sir, can you please help me to figure out what may be the possible solution to this issue?

I used this code and Authorization is done.. but the error comes while I am posting status update... Can anyone please help..

I already worked on http://github.com/brione/Brion-Learns-OAuth and getting the error listed below, when I am posting status update...

WARN/System.err(190): org.apache.http.client.HttpResponseException: Unauthorized WARN/System.err(190): at org.apache.http.impl.client.BasicResponseHandler.handleResponse(BasicResponseHandler.java:71) WARN/System.err(190): at org.apache.http.impl.client.BasicResponseHandler.handleResponse(BasicResponseHandler.java:59) WARN/System.err(190): at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:657) WARN/System.err(190): at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:627) WARN/System.err(190): at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:616) WARN/System.err(190): at com.test.twitter.BLOA$PostTask.doInBackground(BLOA.java:343) WARN/System.err(190): at com.test.twitter.BLOA$PostTask.doInBackground(BLOA.java:1) WARN/System.err(190): at android.os.AsyncTask$2.call(AsyncTask.java:185) WARN/System.err(190): at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:256) WARN/System.err(190): at java.util.concurrent.FutureTask.run(FutureTask.java:122) WARN/System.err(190): at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:648) WARN/System.err(190): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:673) WARN/System.err(190): at java.lang.Thread.run(Thread.java:1060)

I succeed with OAuth Authentication and getting user_secret and user_token and stored in preferences...

So the issue is with http posting using OAuth header...

Twitter tightened its security regarding OAUTH and the http-based URLs in the product are out of date and don't work. Neither does the method of having a fake URL registered at the Twitter site, which was the only way it could be done at the time, although I'm starting to suspect that my URL scheme was wrong too.

java.io.IOException: No authentication challenges found

results when trying to post a status.

hi

I am getting unauthorized 401 exception at the line
mConsumer.sign(post);

in PostTask class's doInBackground method of BLOA.java file.. please tell me how can i solve that exception?