无法与注销后，Facebook的凭据重新登录 [英] Can't relogin with Facebook credentials after logout
问题描述
我有一个Android应用程序，允许用户登录他们的Facebook凭证。一旦他们退出的第一次，他们无法再次登录。从应用程序页面，用户设置的清理应用程序的权限后的Facebook的网站，登录作品正确的。
我用 LoginButton 登录。
这需要能够访问登录信息，扩展该 AuthActivity 活动活动。
公共类AuthActivity延伸活动{
私人AuthUtils authUtils;
@覆盖
保护无效的onCreate（包savedInstanceState）{
super.onCreate（savedInstanceState）;
authUtils =新AuthUtils（本）;
authUtils.onCreate（savedInstanceState）;
}
公共AuthUtils getAuthUtils（）{
返回authUtils;
}
@覆盖
公共无效的OnStart（）{
super.onStart（）;
authUtils.onStart（）;
}
@覆盖
公共无效的onStop（）{
super.onStop（）;
authUtils.onStop（）;
}
@覆盖
公共无效onResume（）{
super.onResume（）;
authUtils.onResume（）;
}
@覆盖
公共无效的onPause（）{
super.onPause（）;
authUtils.onPause（）;
}
@覆盖
公共无效的onDestroy（）{
super.onDestroy（）;
authUtils.onDestroy（）;
}
@覆盖
公共无效的onSaveInstanceState（包outState）{
super.onSaveInstanceState（outState）;
authUtils.onSaveInstanceState（outState）;
}
@覆盖
公共无效onActivityResult（INT申请code，INT结果code，意图数据）{
super.onActivityResult（要求code，因此code，数据）;
authUtils.onActivityResult（要求code，因此code，数据）;
}
}
AuthUtils这个样子。我剥夺了所有的Google+登录相关的东西，一切都没有什么关系的登录过程，像我的应用程序preferences保存用户信息的。
公共类AuthUtils实现ConnectionCallbacks，OnConnectionFailedListener {
私人最终活动activityContext;
私人UiLifecycleHelper facebookUiHelper;
公共AuthUtils（活动范围内）{
this.activityContext =背景;
facebookUiHelper =新UiLifecycleHelper（背景下，facebookStatusCallback）;
}
公共无效signInFacebook（）{
LoginButton facebookLoginButton =新LoginButton（activityContext）;
facebookLoginButton.setReadPermissions（Arrays.asList（电子邮件））;
facebookLoginButton.performClick（）;
}
公共无效signOutFacebook（）{
会话facebookSession = Session.getActiveSession（）;
如果（facebookSession！= NULL）{
facebookSession.closeAndClearTokenInformation（）;
}
}
私人StatusCallback facebookStatusCallback =新StatusCallback（）{
@覆盖
公共无效电话（最后一届会议上，SessionState会状态，例外的例外）{
如果（state.isOpened（））{
Request.newMeRequest（会话，新GraphUserCallback（）{
@覆盖
公共无效onCompleted（GraphUser用户，响应响应）{
字符串email =;
如果（user.asMap（）的containsKey（电子邮件））{
电子邮件= user.getProperty（电子邮件）的toString（）。
} 其他 {
// ...无关登陆
}
//这里的一些行动，而不是相关的登录。
}
}）;
}否则如果（state.isClosed（））{
// ...无关登陆
}
}
};
公共无效的onCreate（包savedInstanceState）{
facebookUiHelper.onCreate（savedInstanceState）;
}
公共无效onResume（）{
facebookUiHelper.onResume（）;
}
公共无效的onPause（）{
facebookUiHelper.onPause（）;
}
公共无效的onDestroy（）{
facebookUiHelper.onDestroy（）;
}
公共无效的onSaveInstanceState（包outState）{
facebookUiHelper.onSaveInstanceState（outState）;
}
公共无效onActivityResult（INT申请code，INT结果code，意图数据）{
facebookUiHelper.onActivityResult（要求code，因此code，数据）;
}
}
我有同样的问题，运行Facebook的示例应用程序时也是如此。我解决了这个通过提供我的默认签名密钥Facebook的：无论是在我的开发人员设置在的 https://developers.facebook.com/settings/developer/sample-app/ ，然后在Android平台上的应用程序设置。
Facebook的提出一个简单的方法来获得你的默认密钥，可排除下找到在 https://developers.facebook.com/docs/android/getting-started 。在code这样做运行Hello Facebook的示例应用程序时提供如下。
尝试{
PackageInfo信息= getPackageManager（）。getPackageInfo（
com.facebook.samples.hellofacebook
PackageManager.GET_SIGNATURES）;
对于（签名签名：info.signatures）{
消息摘要MD = MessageDigest.getInstance（SHA）;
md.update（signature.toByteArray（））;
Log.d（KeyHash：Base64.en codeToString（md.digest（），Base64.DEFAULT））;
}
}赶上（的NameNotFoundException E）{
}赶上（抛出：NoSuchAlgorithmException E）{
}
请注意：当你发布的应用程序，你不应该使用默认密钥，并生成和签名的应用程序与你自己的
。I have an Android application that allow users to login with their Facebook credentials. Once they logout for the first time, they can't login again. After clearing the application's permission from the Applications page in user settings on Facebook's website, logging in works correctly.
I use a LoginButton to login.
Activities that need to be able to access the login information, extend this AuthActivity Activity.
public class AuthActivity extends Activity {
private AuthUtils authUtils;
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
authUtils = new AuthUtils(this);
authUtils.onCreate(savedInstanceState);
}
public AuthUtils getAuthUtils() {
return authUtils;
}
@Override
public void onStart() {
super.onStart();
authUtils.onStart();
}
@Override
public void onStop() {
super.onStop();
authUtils.onStop();
}
@Override
public void onResume() {
super.onResume();
authUtils.onResume();
}
@Override
public void onPause() {
super.onPause();
authUtils.onPause();
}
@Override
public void onDestroy() {
super.onDestroy();
authUtils.onDestroy();
}
@Override
public void onSaveInstanceState(Bundle outState) {
super.onSaveInstanceState(outState);
authUtils.onSaveInstanceState(outState);
}
@Override
public void onActivityResult(int requestCode, int resultCode, Intent data) {
super.onActivityResult(requestCode, resultCode, data);
authUtils.onActivityResult(requestCode, resultCode, data);
}
}
AuthUtils look like this. I stripped of all Google+ login related stuff and everything that doesn't have anything to do with the login process, like saving the user information with my application preferences.
public class AuthUtils implements ConnectionCallbacks, OnConnectionFailedListener {
private final Activity activityContext;
private UiLifecycleHelper facebookUiHelper;
public AuthUtils(Activity context) {
this.activityContext = context;
facebookUiHelper = new UiLifecycleHelper(context, facebookStatusCallback);
}
public void signInFacebook() {
LoginButton facebookLoginButton = new LoginButton(activityContext);
facebookLoginButton.setReadPermissions(Arrays.asList("email"));
facebookLoginButton.performClick();
}
public void signOutFacebook() {
Session facebookSession = Session.getActiveSession();
if(facebookSession != null) {
facebookSession.closeAndClearTokenInformation();
}
}
private StatusCallback facebookStatusCallback = new StatusCallback() {
@Override
public void call(final Session session, SessionState state, Exception exception) {
if(state.isOpened()) {
Request.newMeRequest(session, new GraphUserCallback() {
@Override
public void onCompleted(GraphUser user, Response response) {
String email = "";
if(user.asMap().containsKey("email")) {
email = user.getProperty("email").toString();
} else {
// ... not related to login
}
// Some actions here, not related to login.
}
});
} else if(state.isClosed()) {
// ... not related to login
}
}
};
public void onCreate(Bundle savedInstanceState) {
facebookUiHelper.onCreate(savedInstanceState);
}
public void onResume() {
facebookUiHelper.onResume();
}
public void onPause() {
facebookUiHelper.onPause();
}
public void onDestroy() {
facebookUiHelper.onDestroy();
}
public void onSaveInstanceState(Bundle outState) {
facebookUiHelper.onSaveInstanceState(outState);
}
public void onActivityResult(int requestCode, int resultCode, Intent data) {
facebookUiHelper.onActivityResult(requestCode, resultCode, data);
}
}
I had the same problem, even when running Facebook's sample apps. I solved this by providing my default signing key to Facebook: both in my Developer Settings for the Sample Apps at https://developers.facebook.com/settings/developer/sample-app/ and then in your Apps settings in the Android platform.
Facebook suggests an easy way to get at your default key which can be found under Troubleshooting at https://developers.facebook.com/docs/android/getting-started. The code for doing so when running the Hello Facebook example app is provided below.
try {
PackageInfo info = getPackageManager().getPackageInfo(
"com.facebook.samples.hellofacebook",
PackageManager.GET_SIGNATURES);
for (Signature signature : info.signatures) {
MessageDigest md = MessageDigest.getInstance("SHA");
md.update(signature.toByteArray());
Log.d("KeyHash:", Base64.encodeToString(md.digest(), Base64.DEFAULT));
}
} catch (NameNotFoundException e) {
} catch (NoSuchAlgorithmException e) {
}
Note: When you're publishing apps, you shouldn't be using the default key and be generating and signing apps with your own.
这篇关于无法与注销后，Facebook的凭据重新登录的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
