If hash key is not properly generated then you can face problems like
A native Login Dialog is displayed but after accepting the permissions popup goes of and nothing happens in log cat
But Login and share will work fine if native app on device is disabled (Login Dialog opens in web view in this case and proper hash key is not required for this)
I was facing the same problem and solved this one by getting hash key using this code. Hash key was different from one generated using openSSl and keytool
and after updating this hash key in Facebook app all works fine
//================================== To Get Facebook Hash key Programmatically =========================//
PackageInfo info;
try {
info = activity.getPackageManager().getPackageInfo("com.checkmyplanner", PackageManager.GET_SIGNATURES);
for (Signature signature : info.signatures) {
MessageDigest md;
md = MessageDigest.getInstance("SHA");
md.update(signature.toByteArray());
String something = new String(Base64.encode(md.digest(), 0));
//String something = new String(Base64.encodeBytes(md.digest()));
Log.e("hash key", something);
}
} catch (NameNotFoundException e1) {
Log.e("name not found", e1.toString());
} catch (NoSuchAlgorithmException e) {
Log.e("no such an algorithm", e.toString());
} catch (Exception e) {
Log.e("exception", e.toString());
}
Just change your package name and get proper hash key