Facebook Login

Solar2D Network
#1

I started with Facebook SSO which worked fine for me, then when I realized that if a user has the Facebook app installed on the phone, there was a conflict with single sign on. I went through the process of getting the key hashes for my app and copied it into my Facebook developer account. Everything was working fine at this point.

I was using the Corona SDK trial version and building an apk with the androiddebugkey. I have now upgraded to the pro version of Corona and rebuilt my apk using the same key hash and the androiddebugkey , but now when I try to log in to facebook it tells me that my app is misconfigured for Facebook login.

Has anyone had this problem? [import]uid: 208811 topic_id: 35702 reply_id: 335702[/import]

#2

I’m not sure why things would have changed, but perhaps the debugkey changed or something. Regardless before you can release your app, you will need to create a release key. See this forum post on how to do that:

https://developer.coronalabs.com/forum/2011/04/16/signing-android-applications-3-easy-steps

It might be worth it to get your production key made.

But regardless, if you use “adb logcat” and look at the output from your android device, Facebook will tell you exactly what keystore it’s looking for. You can copy/paste from the logfile to Facebook’s setup screen and that should fix your issue.
[import]uid: 199310 topic_id: 35702 reply_id: 142040[/import]

#3

Thanks Rob, I made a release key after I made this post, just in case that was the problem.I ran the logcat and copy/pasted in the key that it was looking for, works fine now. I still would really like to know why the accepted hash key changed though, what would cause this? [import]uid: 208811 topic_id: 35702 reply_id: 142071[/import]

#4

I’m not sure why things would have changed, but perhaps the debugkey changed or something. Regardless before you can release your app, you will need to create a release key. See this forum post on how to do that:

https://developer.coronalabs.com/forum/2011/04/16/signing-android-applications-3-easy-steps

It might be worth it to get your production key made.

But regardless, if you use “adb logcat” and look at the output from your android device, Facebook will tell you exactly what keystore it’s looking for. You can copy/paste from the logfile to Facebook’s setup screen and that should fix your issue.
[import]uid: 199310 topic_id: 35702 reply_id: 142040[/import]

#5

Thanks Rob, I made a release key after I made this post, just in case that was the problem.I ran the logcat and copy/pasted in the key that it was looking for, works fine now. I still would really like to know why the accepted hash key changed though, what would cause this? [import]uid: 208811 topic_id: 35702 reply_id: 142071[/import]