Closed erperejildo closed 2 years ago
@erperejildo I've run the example app using flutter run --release
and it works.
Try to upgrade to the last version of this plugin. keep in mind that starting with the version 4.2.0 the android manifest configuration has been changed. Go to the documentation to check that changes
this seems an error with your hashes. You should go to your facebook console and check if you don't have some notification of the facebook team, also check your key hashes
@erperejildo I've run the example app using
flutter run --release
and it works.Try to upgrade to the last version of this plugin. keep in mind that starting with the version 4.2.0 the android manifest configuration has been changed. Go to the documentation to check that changes
this seems an error with your hashes. You should go to your facebook console and check if you don't have some notification of the facebook team, also check your key hashes
I'll try to use latest version, ok. What do you mean with Facebook console? I can only see this place to put the hash:
https://user-images.githubusercontent.com/5629919/166911150-e9e16dea-8c9f-4cda-a969-d6797bd250bd.png
@erperejildo I've run the example app using
flutter run --release
and it works. Try to upgrade to the last version of this plugin. keep in mind that starting with the version 4.2.0 the android manifest configuration has been changed. Go to the documentation to check that changes this seems an error with your hashes. You should go to your facebook console and check if you don't have some notification of the facebook team, also check your key hashesI'll try to use latest version, ok. What do you mean with Facebook console? I can only see this place to put the hash:
https://user-images.githubusercontent.com/5629919/166911150-e9e16dea-8c9f-4cda-a969-d6797bd250bd.png
My suggestion is run the app in android studio and use the logcat to show the error when the app crash, because I'm sure that the error is not due to this plugin
@erperejildo I've run the example app using
flutter run --release
and it works. Try to upgrade to the last version of this plugin. keep in mind that starting with the version 4.2.0 the android manifest configuration has been changed. Go to the documentation to check that changes this seems an error with your hashes. You should go to your facebook console and check if you don't have some notification of the facebook team, also check your key hashesI'll try to use latest version, ok. What do you mean with Facebook console? I can only see this place to put the hash: https://user-images.githubusercontent.com/5629919/166911150-e9e16dea-8c9f-4cda-a969-d6797bd250bd.png
My suggestion is run the app in android studio and use the logcat to show the error when the app crash, because I'm sure that the error is not due to this plugin
the thing is I don't see any issue while testing the app myself. And yes, it's probably more related to Facebook itself and its configuration but when asking the staff they keep saying it doesn't work and if the hash is not updated I should ask on its forum (and no one never reply there).
I guess it could more people like without the necessary support to fix it. Any explanation to understand why they see different key hash while testing my app?
@erperejildo I've run the example app using
flutter run --release
and it works. Try to upgrade to the last version of this plugin. keep in mind that starting with the version 4.2.0 the android manifest configuration has been changed. Go to the documentation to check that changes this seems an error with your hashes. You should go to your facebook console and check if you don't have some notification of the facebook team, also check your key hashesI'll try to use latest version, ok. What do you mean with Facebook console? I can only see this place to put the hash: https://user-images.githubusercontent.com/5629919/166911150-e9e16dea-8c9f-4cda-a969-d6797bd250bd.png
My suggestion is run the app in android studio and use the logcat to show the error when the app crash, because I'm sure that the error is not due to this plugin
the thing is I don't see any issue while testing the app myself. And yes, it's probably more related to Facebook itself and its configuration but when asking the staff they keep saying it doesn't work and if the hash is not updated I should ask on its forum (and no one never reply there).
I guess it could more people like without the necessary support to fix it. Any explanation to understand why they see different key hash while testing my app?
if your app is in debug mode some time the key hash returned by the command is wrong
keytool -exportcert -alias key -keystore assets/.keystore | openssl sha1 -binary | openssl base64
in that case you can get the correct hey hash using native code
https://developers.facebook.com/docs/facebook-login/android/troubleshooting?locale=en_US
I used latest version and didn't help:
Locally it complains now about this review stage but I can't send it without this fixed.
"you can get the correct hey hash using native code". I don't understand this even after reading that. Is there any possible way to do that from Flutter?
are you saying that the login flow works fine but it shows a warning in that case you need to send a request to Facebook to be able to use the permissions that you are requesting to the user. as another hand In pub.dev you can find some packages to get the correct key hash
I' sorry man but I cannot help you more with this because is not an issue of this plugin.
please considere close this issue.
"are you saying that the login flow works fine but it shows a warning". That's correct "you need to send a request to Facebook to be able to use the permissions". But that's not possible. First of all because if request more permissions I'll need to send the app for review and they will reject it. Second, I don't need extra permissions, for me it works as it is. "In pub.dev you can find some packages to get the correct key hash". Can you point me to that? I thought that was only possible but that command I shared above.
I'll close the ticket in the meantime since it's not related
keytool -exportcert -alias key -keystore assets/.keystore | openssl sha1 -binary | openssl base64
is the command I used and that is still showing the "wrong" hash
keytool -exportcert -alias key -keystore assets/.keystore | openssl sha1 -binary | openssl base64
is the command I used and that is still showing the "wrong" hash
As I mentioned before in debug mode some times that command not works, try to use native code and android studio (WITH LOCAT) to get the correct hash
I tried that an specific package to show it and I get the same key hash I already had in Facebook
Describe the bug Maybe it's not 100% related to this dependency but this is what I see while testing my app:
I got this message recently but I have to say that my code was working fine and I didn't update anything. Facebook support doesn't give any clue and they keep saying that login is not working when they review the app (without any other help).
I use Flutter and this package: https://pub.dev/packages/flutter_facebook_auth But I don't think code/framework/package is related at all to this issue. Probably more related to the key hash but this is also updated by this command:
My key hash starts like this:
But Facebook's "support" shows me this snapshot from its test:
Why is it different? Is it because I cannot move my app to Live mode?:
That's because of this:
Then, looking into that the problem is this:
Ok, so the problem is During Login, your app is crashing. Fine, but how should I fix it?
Despite I don't think this is related this is my login function:
Environment Add your
flutter doctor -v
:Add your
pubspec.yaml
:Add your `MainActivity:
Add your
AndroidManifest.xml
:Add your
/app/res/values/strings.xml
:To Reproduce Try log in with Facebook on released app
Expected behavior I shouldn't see any error
Screenshots Added above