Publish stream problem.

[PSBT]

Hi!

I'm having a problem when trying to publish a stream. The problem occurs when:

1. Launching theRunAround app, and login in to FB.
2. On successful login, leave the app.
3. Login to FB in a browser.
4. Re-launch theRunAround app.

The session is correctly restored (my friends are displayed), but when I want to add a run, and the FB dialog appears, the dialog shows the following error:

"An error occurred with 'my_app_name' . Please try again later."

I've added FBDialogDelegate's dialog:didFailWithError: method to the sample, and when I click the "ok" button in the FBDialog, the following is printed to xCode's console:

Error Domain=facebookErrDomain Code=110 UserInfo=0x4d58830 "Operation could not be completed. (facebookErrDomain error 110.)"

What can it be? How can I fix this? This is actually happening to me in my own app, but I've also been able to reproduce it in theRunAround app, and that's why, above, I enumerate the steps to reproduce the issue using that sample.

Thanks you very much!

[yujuan]

The error with FBDialog stream publish are usually related to the cookie. You are log into touch.facebook.com, is that correct?
I Notice that if I use another device login into touch.facebook.com. and then login into the app with the sdk. I refresh on touch.facebook.com, the touch site is logged out also. It should be some bug in the server side that does not handle the touch site cookie well, I will investigate on that and keep you posted.

[PSBT]

Actually I tested connecting to the regular Facebook in a browser, but I guess that it also occurs with the touch.facebook.com you mention, so the problem can also arise, when for example I'm running my app in my iphone, leave it, go to another app that also uses FB, and log in there...

Thanks!

[yujuan]

Actually, there is security reason for this design. When you login in to new place the old cookie get invalid , so that the mobile cookie can be valid at only one place with the assumption one user has only one cookie. But for iphone, as different app's web view does not share the cookie. this is a problematic. I will see if we can change on the server side. Thanks

[PSBT]

The other solution might be to detect this error, and ask the user to re-login. The only problem with this approach is that I noticed that FBDialogDelegate's dialog:didFailWithError: methods gets called only after the user has clicked the Ok button in the dialog. Also this method doesn't get called when closing the dialog with the 'x' at the top.

Any suggestions as to how should I handle this error?

Thanks!

[yujuan]

For close dialg with 'x', the delegate dialogDidNotCompleteWithUrl will be called. As for judge if the dialog complete succeed or not. For judge if astream publish dialog go through successfully, you would need to check if a parameter post_id is appended to the url.
Though this way may tentatively make it look better, it is still not desirable as we do not want user to login frequently especially when the switch between facebook connect apps. So the best fix should be on the server side.

[nanomb]

Any news about this? I´m also having this issue and users are complaining about those errors :(
Which solution have you guys developed for this problem in your own apps?

[yujuan]

We currently have a change to address this issue but still under review. will let you know once the change go out

[venky284]

This is exactly the same error i get..
am also looking for some sort of solution..
do any one have a fix for this.

[ayyoitsp]

I'm getting the same problem at times. It seems doing an explicit logout before login resolves the issue, but seems like a bad overall solution. Thoughts?

[JPGarcia2010]

I have the same error always when trying to open the dialog to publish an stream. I've tried to do a logout before but didn't work. This is happening also on the Demo Application. What is the solution for this error?

[ghost]

Also seeing this using SSO with the facebook application on the phone and its also not working, I am getting the 110 error. This happens on the simulator and the device. It is working on the 3.2 ipad simulator but this does not use SSO.