Runtime Error when trying Facebook login after going to new build 1135, loginFailed with no isError

Social Media
#1

I haven’t tried my Facebook posting in a while, but it did work last time. After the 1135 update, it didn’t work, and I found out about the additional FacebookAppID line, so I added that.

Now, I get the Facebook login, I log in, Facebook asks me about the audience, and then just goes back to my app. In the log, I get only this in my FB listener:

Runtime error

Runtime error

Very troublesome that it reports two runtime errors with no detail.

No detail on the runtime errors, but I print out the contents of the event, and it’s:

type = session

name = fbconnect

phase = loginFailed

isError = false

response =

I thought I was submitting to the app store tonight, and this has stopped me cold. I’ve gone back to my FB settings for my app in FB developer, and they are unchanged from when it worked, except:

Facebook Login: enabled now, but it didn’t help

Deep Linking: enabled now, but it didn’t help

Sandbox Mode: enabled or disabled, no difference

Anyone have any ideas?

Thanks!

#2

Hi RealHandy,

That sounds strange.  Have you tried going back to an older daily build to see if it works then?

  • Andrew
#3

I’ve since confirmed that the runtime error doesn’t occur when I don’t provide a table of permissions on login. Of course, then I can’t publish. But including the permissions table with publish_actions in it causes the error. Also, Corona docs still use publish_stream, which FB has changed in their API. Not good. I’ve also opened a bug because Scrumptious sample app doesn’t work. Can’t go back to older version because I’ve spent all this time porting to widget 2.0.

#4

All,

Although the Scrumptious app still isn’t working for me (403 error and other strangeness), I fixed my FB problem with the error-less loginFailed event phase. See the explanation in this other forum post:

http://forums.coronalabs.com/topic/36197-facebook-broken-in-my-app-and-scrumptious-is-it-working-for-anyone-in-ios-as-of-build-1135/

#5

Hi RealHandy,

That sounds strange.  Have you tried going back to an older daily build to see if it works then?

  • Andrew
#6

I’ve since confirmed that the runtime error doesn’t occur when I don’t provide a table of permissions on login. Of course, then I can’t publish. But including the permissions table with publish_actions in it causes the error. Also, Corona docs still use publish_stream, which FB has changed in their API. Not good. I’ve also opened a bug because Scrumptious sample app doesn’t work. Can’t go back to older version because I’ve spent all this time porting to widget 2.0.

#7

All,

Although the Scrumptious app still isn’t working for me (403 error and other strangeness), I fixed my FB problem with the error-less loginFailed event phase. See the explanation in this other forum post:

http://forums.coronalabs.com/topic/36197-facebook-broken-in-my-app-and-scrumptious-is-it-working-for-anyone-in-ios-as-of-build-1135/