Once you're in the application summary page, choose Edit Settings and then pick Mobile and Devices on the left-hand side. Once you have this, you need to give it to Facebook.įind your application on Facebook's Developer page (or create a new one if you haven't set one up already). This generates a short string of characters (which may include characters such as '=' or '/') that identify the signature called a certificate.
In order to provide Facebook with information about the signature, you need to run the command Jay provides above (repeated here): keytool -exportcert -alias androiddebugkey -keystore ~/.android/debug.keystore | openssl sha1 -binary | openssl base64 Details about the Debug keystore are available in the Android Documentation - Signing Applications. What I didn't know is that the Eclipse environment is signing builds automatically when you push them to the device using a debug keystore. The issue is that Facebook needs information about the key used to sign the application in order to allow the authorization. apk applications, because they can't be distributed. I suspect that Facebook has a blanket policy to allow unsigned. I have no idea why this worked on the emulator but failed on the device. D/Facebook-authorize( 2194): Login failed: invalid_key The failure I saw when running adb logcat was the following. The authentication step was working just fine until I moved from deploying on the emulator to an actual device. I was developing using the Facebook Android SDK in combination with PhoneGap and the Phonegap Facebook plug in. This question is long since answered here (and in the Facebook Android SDK), but I'm going to try and capture the full solution for anyone that ends up stumbling upon this thread. Update: I wrote a more detailed blog post about this problem and explains how SSO causes it:
0 kommentar(er)
