Right now the it was able to post once we accept the app permissions through browser but if we are doing it for the first time which fb app installed its going to the share and asking would like to on u r behalf and messaging is not getting posted at all .The problem is only with the android builds. It is not asking for the acess permissions. Could you please help.
Has anyone found a solution to the Android issue of not being able to post anything? I tried what @beckslash suggested on his other thread but it did not work for me. Wanting to release my app this week, any other ideas of what we can do?
@rxmarccall Most likely it’s because the hash key is incorrect. As Rob Miracle said, you still need a valid hash key and Corona is no longer outputting it in the console. You have to generate it yourself like this:
I’ve noticed this problem only after I installed the Facebook app on my device. when I removed it, the popup vanished and the original facebook login page came back.
I am currently working on an update to an already live app. I had a working android hash key already for my live app, shouldn’t this hash key still work with my updated app? Or do I have to create a new one?
If the hash was correctly generated there’s no reason to worry. You’ll sign the apk with the same certificate you generated the has in the first place.
Yea so the issue is just what others have reported of a weird Android pop up that asks if the user wants the app to be allowed on their facebook. Click OK and nothing happens. Works fine on IOS, not on Android. Tried what you suggested with the “get Permissions” function and it still doesn’t ever post anything. Might just be disabling facebook on my app for now seeing as there is no solution to this.
Let me try to make sure everyone understands this. Facebook tries to detect if their native app is installed. If it is, it uses it for SSO or Single Sign On. Your app gets backgrounded, the native Facebook app launches and prompts you to login and agree to a set of permissions. It then calls back to your app to bring it out of the background and let it know you’ve logged in correctly.
If you DO NOT have the native facebook app installed, it opens up a webView and tries to log you in through their web interface. This is why you can make it work without the native app installed.
Why won’t it work with the native app installed? Well its all about that big about being able to bring your app out of the background to the foreground and re-establish communications. On Apple’s iOS they use a URL scheme to do it. That’s why you have to put that bit in your build.settings about “fbYOURAPPID” so that the native facebook app can restart you.
Your package name must match the package name that you’re building your APK with. Your Key Hash is used to secure the login and it must match what your app is being built with. In the past, you could provide FB a bogus key hash and they would spit out what they were expecting in the console log, but there are reports they are not longer doing that, so you have to make sure you get it right.
I have everything set up like you have shown Rob, I have a hash that was used in my currently live app. I’m going to try and generate a new one just for fun to see if it fixes anything. However when I run the command given by beckslash, I get ‘openss’ is not a recognized command.
@rob, yea that was a typo in my post, I have it correct in the prompt. Do I need a special version of the Java sdk? Or should the one that Corona require work?