All of my hashkey’s end in an = sign. Try adding it with the = on the end. I don’t think Facebook prints it with the = sign.
o.0 you’re right, what the eff…
seriously I apologize for that last post…its been a long week. Let me find my device and give a try.
ok, so unless I need to wait another 24 hours after adding = to that hash key, getting the same error.
The only suggestion I have at this point is to take the command you’re running to generate the hash key and break it down into it’s three steps. There are three commands separated by pipe’s ("|"), like:
Command 1 | command 2 | command 3
Run whatever your doing with just the first part and see if you’re getting an error message or some output that is binar.
Then run the first two commands, looking for errors
Make sure you’re buidling Corona SDK with the same keystore you’re using for generating the hash.
Make sure you have the right OpenSSL installed. There have been several people on windows have installed a different version and it started working for them.
Hi Rob, sorry to ask you with this wrong topic below
local function onSystemEvent( event )
if event.type == “applicationOpen” and event.url then
printURL( event.url )
end
end
dose this work on android yet? and do we have any other way to make thing work like this?
@uysuntray, in the future please either open a new post, or post on appropriate topics. People will have trouble fining these answers in the future or will be confused about why this problem comes up for a random other issue. However, there is a filed bug report for this and has been confirmed, however there is no ETA on getting it fixed.
@Rob, can you get the key hash that Facebook requires by searching the adb logcat on the device itself?
I’m trying now, and getting no joy…
It should print the desired hash key in the adb logcat. However, you have to make a couple of substitutions. I think hypens need turned into underscores or visa versa and I think the ? on the end needs to be a +.
Rob
After 3 hours of working with this, I realized that I needed to create test users for the test app. In addition, the key hash doesn’t seem to come into play when you’re using the test app as well.
Someone definitely needs to untangle this process. It is BRUTAL.
I don’t know that I’ve ever had to create a test account.
As far as the hash key, this is by far the place where people struggle the most. I think the biggest issue is people don’t understand what keystores are, what hashes of those keystores are, how the command’s pipeline information between the three commands that are running. People don’t know where they keep their keystores and if they choose to use a debug one, they end up using the default android one and not the default Corona SDK keystore which is different. Then you factor in different versions of OpenSSL and you can see how much fun this is. We developed a blog post just for this:
http://coronalabs.com/blog/2013/07/30/understanding-facebook-authentication/
It should be the most accurate source of information about creating the keyhash.
Rob
For sure, I don’t know how Corona could make it easier to integrate Facebook, aside from storming the castle and demanding less moving parts from Mark.
I did follow that posted guide, but since the key hash was irrelevant when running the test app, my time debugging seemed like a waste. Fortunately, following the steps to generate the hash instead of look for in my logcat yielded an openssl error on my machine ::sarcasm::.
I guess the only suggestion I can make to folks that are attempting this, is to make sure to note whether you are working from a test app or a production app. It may seen inconsequential, but it’s pretty important.
@Rob, can you get the key hash that Facebook requires by searching the adb logcat on the device itself?
I’m trying now, and getting no joy…
It should print the desired hash key in the adb logcat. However, you have to make a couple of substitutions. I think hypens need turned into underscores or visa versa and I think the ? on the end needs to be a +.
Rob
After 3 hours of working with this, I realized that I needed to create test users for the test app. In addition, the key hash doesn’t seem to come into play when you’re using the test app as well.
Someone definitely needs to untangle this process. It is BRUTAL.
I don’t know that I’ve ever had to create a test account.
As far as the hash key, this is by far the place where people struggle the most. I think the biggest issue is people don’t understand what keystores are, what hashes of those keystores are, how the command’s pipeline information between the three commands that are running. People don’t know where they keep their keystores and if they choose to use a debug one, they end up using the default android one and not the default Corona SDK keystore which is different. Then you factor in different versions of OpenSSL and you can see how much fun this is. We developed a blog post just for this:
http://coronalabs.com/blog/2013/07/30/understanding-facebook-authentication/
It should be the most accurate source of information about creating the keyhash.
Rob
For sure, I don’t know how Corona could make it easier to integrate Facebook, aside from storming the castle and demanding less moving parts from Mark.
I did follow that posted guide, but since the key hash was irrelevant when running the test app, my time debugging seemed like a waste. Fortunately, following the steps to generate the hash instead of look for in my logcat yielded an openssl error on my machine ::sarcasm::.
I guess the only suggestion I can make to folks that are attempting this, is to make sure to note whether you are working from a test app or a production app. It may seen inconsequential, but it’s pretty important.