I tested to make sure Facebook and Facebook.login are not nil. I can’t see any way to debug it farther. It simply does nothing and I have no idea why.
Any read these forums?
Hi there,
It would be helpful if you posted snippets of your code where you call facebook.login(), as well as your facebook listener function and your build.settings file. There are a number of potential places where something may be missing that would cause it not to be working.
- Andrew
Thanks for the response Andrew.
I should mention this exact facebook routine works using Corona SDK, as well as Android Enterprise. Which leads me to believe it has to be something with the library and not the implementation.
You’ve had no trouble with facebook within LUA (ie facebook = require “facebook”…facebook.login()appid, listener, {“publish_stream”} ) ?
@tntwickey, Facebook deprecated publish_stream (even though it might still work), so you probably want to use publish_actions instead.
Also, API call would be facebook.login( appid, listener, {“publish_actions”} )
You might also want to take a look at this:
http://docs.coronalabs.com/daily/guide/social/setupFacebook/index.html
Make sure to add publish_actions as one of the permissions for you app at Facebook dev portal.
Good luck.
Naomi
Hi there,
Yes, I’ve had no trouble using the facebook implementation within Lua, and using facebook.login() and posting to the user’s wall. Although I don’t use publish_stream, I use publish_actions (as recommended here: http://developers.facebook.com/blog/post/2012/04/25/streamlining-publish_stream-and-publish_actions-permissions/).
But I’m not an Enterprise user, so I may not be facing the exact issue you are.
- Andrew
Thanks Naomi and Andrew.
I wasn’t aware of the stream --> actions change although I don’t think thats the issue. It sounds like it would still work. I will take a closer look at the App settings on facebook. ( It was working for a long time so it’s annoying 
Still no solution. It just hangs with no error. The facebook module is loading and facebook and facebook.login are not nil. I print that out via native alert when code is called. Nothing behind the facebook call will run.
WIll Corona ever support the iOS Facebook integration like they did with Twitter? It would sure help LOTS of developers.
Hi tntwickey,
Do you include
Also, I noticed you mentioned printout out some debug info via a native alert. A better method, if you’re not aware, is to use regular Lua print statements. When you install on an iOS device, keep it connected to your computer. In the XCode, go to the Organizer window and click Console for the connected device, and you’ll be able to see the print statement output. If you haven’t checked that already, I’d suggest looking at it and seeing if any error messages are getting printed there.
Also, have you included your Facebook app ID in your build.settings? There are actually two places you need to include it, and if you don’t include it in one, I believe the login process will crash, which may explain the behavior you’re seeing.
- Andrew
Thanks Andrew.
It was the build.settings file. Having a FacebookAppID field new perhaps as it wasn’t there before.
Hi there,
It would be helpful if you posted snippets of your code where you call facebook.login(), as well as your facebook listener function and your build.settings file. There are a number of potential places where something may be missing that would cause it not to be working.
- Andrew
Thanks for the response Andrew.
I should mention this exact facebook routine works using Corona SDK, as well as Android Enterprise. Which leads me to believe it has to be something with the library and not the implementation.
You’ve had no trouble with facebook within LUA (ie facebook = require “facebook”…facebook.login()appid, listener, {“publish_stream”} ) ?
@tntwickey, Facebook deprecated publish_stream (even though it might still work), so you probably want to use publish_actions instead.
Also, API call would be facebook.login( appid, listener, {“publish_actions”} )
You might also want to take a look at this:
http://docs.coronalabs.com/daily/guide/social/setupFacebook/index.html
Make sure to add publish_actions as one of the permissions for you app at Facebook dev portal.
Good luck.
Naomi
Hi there,
Yes, I’ve had no trouble using the facebook implementation within Lua, and using facebook.login() and posting to the user’s wall. Although I don’t use publish_stream, I use publish_actions (as recommended here: http://developers.facebook.com/blog/post/2012/04/25/streamlining-publish_stream-and-publish_actions-permissions/).
But I’m not an Enterprise user, so I may not be facing the exact issue you are.
- Andrew
Thanks Naomi and Andrew.
I wasn’t aware of the stream --> actions change although I don’t think thats the issue. It sounds like it would still work. I will take a closer look at the App settings on facebook. ( It was working for a long time so it’s annoying
Still no solution. It just hangs with no error. The facebook module is loading and facebook and facebook.login are not nil. I print that out via native alert when code is called. Nothing behind the facebook call will run.
WIll Corona ever support the iOS Facebook integration like they did with Twitter? It would sure help LOTS of developers.
Hi tntwickey,
Do you include
Also, I noticed you mentioned printout out some debug info via a native alert. A better method, if you’re not aware, is to use regular Lua print statements. When you install on an iOS device, keep it connected to your computer. In the XCode, go to the Organizer window and click Console for the connected device, and you’ll be able to see the print statement output. If you haven’t checked that already, I’d suggest looking at it and seeing if any error messages are getting printed there.
Also, have you included your Facebook app ID in your build.settings? There are actually two places you need to include it, and if you don’t include it in one, I believe the login process will crash, which may explain the behavior you’re seeing.
- Andrew
Thanks Andrew.
It was the build.settings file. Having a FacebookAppID field new perhaps as it wasn’t there before.