我发表我的应用程序，为了测试它，安装APK在我的手机上。随着出口APK的Facebook不起作用（错误keyhash），但与开发商bin'ed APK它工作正常。
I published my APP and in order to test it, installed the APK on my phone. With the exported APK Facebook doesn't work (wrong keyhash) but with the developer bin'ed apk it works fine.
有人可以告诉我这是怎么回事？为什么keyhash有什么不同？ （第二次，Eclipse更新改变了它的第一次）。
Can somebody tell me what's going on? Why is the keyhash different? (Second time, eclipse update changed it the first time).
此外
既然我已经上传的APK市场，并将其发布（目前未发表的，非常讨厌）。此外，我已经删除了APK本地，所以我不能找出密钥哈希，我无法从市场下载我自己的应用程序（尝试虽然谷歌的发挥，不会引起它不是免费的）。从我的谷歌开发者控制台我甚至不能下载的APK（WTF？）。这样，我需要上传另一个版本（说1.1？） - 虽然我的应用程序将新跳过有什么新的在谷歌节播放这是非常讨厌
Since I've already uploaded the APK to the market and published it (now unpublished, extremely annoying). Also I've deleted the APK locally so I can't find out the key-hash and I can't download my own app from the market (Tried though Google play, can't cause it's not free). I can't even download the APK from my Google Developer Console (Wtf?). So will I need to upload another version (Say 1.1?) - although my app will new skip the "What's new" section in Google Play which is extremely annoying.
任何人都可以建议我应该做的吗？
Can anyone suggest what I should do here?
推荐答案
关键你签订的分布是不同的，你使用的调试一个你的应用程序。 Facebook的指令不明确这一点，admitedly。
The key you sign your app with for distribution is different to the one you use for debugging. The facebook instructions are not clear on this admitedly.
您需要生成散列对你的分配密钥库
You need to generate the hash against your distribution keystore
keytool -exportcert -alias YOUR_DISTRIBUTION_CERT_NAME -keystore YOUR_DISTRBUTION_KEYSTORE_FILE | openssl sha1 -binary | openssl base64
然后考虑过developers.facebook.com添加到您的Facebook应用程序设置现场为哈希可以采取多种散列（即调试证书和您的分发证书）。
then add it to your Facebook App Settings over at developers.facebook.com the field for the hash can take multiple hashes (ie. your debug cert and your distribution cert).
相关推荐
最新文章