问题的回调在微博中的Android回调、问题、微博中、Andr
我在我的应用程序实现的微博，我在回调面临的问题。
I have implemented Twitter in my application , i am facing problem in Callback.
微博的API最近已经更新，所以我无法发送回调URL。
Twitter API's has been updated recently so i am unable to send Callback URL.
另外，设置页面改变现在没有选择的选择基于Web的应用程序或桌面应用程序。
Also the Setting Page now change there is No Option for Selecting Web Based application or Desktop Application.
如果我送回调在这一行：
If i send Callback in this Line :
authUrl = provider.retrieveRequestToken(consumer,CALLBACK_URL);
它总是返回
oauth.signpost.exception.OAuthNotAuthorizedException: Authorization failed (server replied with a 401). This can happen if the consumer key was not correct or the signatures did not match.
但是，如果我发送的空本公司的重定向到Twitter登录页面，但成功的授权之后，不返回回我的应用程序。
but if i send as Null in this its Redirecting to Twitter Login Page,but after successful Authorization it doesn't returns back to my Application.
在将显示PIN号码我想重定向回我的应用程序。
After the Pin number is displayed i want to Redirect back to my Application.
注：微博已经更新了中邮提供的API，因此旧的codeS不能正常工作
Note : Twitter had updated their API so old Codes available in the Post is not working.
我尝试了所有的以下链接
I tried all the Following Links
链接1 ， 链接2 ， 链接3 ， LINK4 ， Link5 ， 链接6
Link 1, Link 2, Link 3, Link4 , Link5 , Link 6
我的code是如下：
public class Main extends Activity {
OAuthConsumer consumer;
OAuthProvider provider;
Twitter twitter;
private static String CALLBACK_URL = "twitterapptest://connect";
@Override
public void onCreate(Bundle icicle) {
super.onCreate(icicle);
setContentView(R.layout.main);
consumer = new DefaultOAuthConsumer(
"XXXXXXXXXXX",
"XXXXXXXXXXXXX");
provider = new DefaultOAuthProvider(
"https://api.twitter.com/oauth/request_token",
"https://api.twitter.com/oauth/access_token",
"https://api.twitter.com/oauth/authorize");
String authUrl = null;
try {
authUrl = provider.retrieveRequestToken(consumer,null);
this.startActivity(new Intent(Intent.ACTION_VIEW, Uri.parse(authUrl)));
} catch (OAuthMessageSignerException e) {
// TODO Auto-generated catch block
e.printStackTrace();
} catch (OAuthNotAuthorizedException e) {
// TODO Auto-generated catch block
e.printStackTrace();
} catch (OAuthExpectationFailedException e) {
// TODO Auto-generated catch block
e.printStackTrace();
} catch (OAuthCommunicationException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
BufferedReader br = new BufferedReader(new InputStreamReader(System.in));
String pin = null;
try {
pin = br.readLine();
} catch (IOException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
try {
provider.retrieveAccessToken(consumer, "4947222");
} catch (OAuthMessageSignerException e) {
// TODO Auto-generated catch block
e.printStackTrace();
} catch (OAuthNotAuthorizedException e) {
// TODO Auto-generated catch block
e.printStackTrace();
} catch (OAuthExpectationFailedException e) {
// TODO Auto-generated catch block
e.printStackTrace();
} catch (OAuthCommunicationException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
URL url = null;
try {
url = new URL("http://twitter.com/statuses/mentions.xml");
} catch (MalformedURLException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
HttpURLConnection request = null;
try {
request = (HttpURLConnection) url.openConnection();
} catch (IOException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
try {
consumer.sign(request);
} catch (OAuthMessageSignerException e1) {
// TODO Auto-generated catch block
e1.printStackTrace();
} catch (OAuthExpectationFailedException e1) {
// TODO Auto-generated catch block
e1.printStackTrace();
} catch (OAuthCommunicationException e1) {
// TODO Auto-generated catch block
e1.printStackTrace();
}
try {
request.connect();
} catch (IOException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
try {
System.out.println("Response: " + request.getResponseCode() + " "
+ request.getResponseMessage());
} catch (IOException e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
}
/**
* As soon as the user successfully authorized the app, we are notified
* here. Now we need to get the verifier from the callback URL, retrieve
* token and token_secret and feed them to twitter4j (as well as
* consumer key and secret).
*/
@Override
protected void onNewIntent(Intent intent) {
super.onNewIntent(intent);
Uri uri = intent.getData();
if (uri != null && uri.toString().startsWith(CALLBACK_URL)) {
String verifier = uri
.getQueryParameter(oauth.signpost.OAuth.OAUTH_VERIFIER);
try {
// this will populate token and token_secret in consumer
provider.retrieveAccessToken(consumer,
verifier);
// TODO: you might want to store token and token_secret in you
// app settings!!!!!!!!
AccessToken a = new AccessToken(consumer.getToken(),
consumer.getTokenSecret());
// initialize Twitter4J
twitter = new TwitterFactory().getInstance();
twitter.setOAuthConsumer("XXXXXXX", "XXXXXXXXXX");
twitter.setOAuthAccessToken(a);
// create a tweet
Date d = new Date(System.currentTimeMillis());
String tweet = "#OAuth working! " + d.toLocaleString();
// send the tweet
twitter.updateStatus(tweet);
} catch (Exception e) {
Toast.makeText(this, e.getMessage(), Toast.LENGTH_LONG).show();
}
}
}
}
我的清单：
<?xml version="1.0" encoding="utf-8"?>
<activity android:name=".OAuthForTwitter" android:label="@string/app_name"
android:configChanges="orientation|keyboardHidden" android:launchMode="singleInstance">
<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="twitterapptest" android:host="connect" />
</intent-filter>
</activity>
</application>
<uses-sdk android:minSdkVersion="4" />
<uses-permission android:name="android.permission.INTERNET" />
推荐答案
问题是，回调URL。 我们应该在应用程序的设置页面中的回调URL的字段名称给一个虚拟回调URL。
The problem is that Callback URl. We should give one Dummy Callback URL in the Field Name of CallBack URL in Application' s Settings Page.
如果我们做这样的并发送回拨URL在我们的code，登录成功后会有一个选项称为重定向到你的应用程序
If we do like that and send the Call Back URL in our code, after successful Login there will be a option called Redirecting to your Application
有关进一步的参考检查该Link Twitter的
For Further Reference check this Link for Twitter
