Yet another Facebook API bug with facebook.showDialog on Android.

So when I try to publish something to my or friends wall using facebook.showDialog, the post actually goes fine, and it fires up the response in the listener, but instead of closing the API window when the posting is done, it open my browser’s window with the link I provide in the “link” or “redirect_uri” properties, and when I close the browser, and go back to my app, the publish API window is still present and I need to click “back” to close it up again.

Anyone knows about this and about a work around??

Corona build : 2013.1257

Phone : Galaxy S3

iOS: Android 4.1.2

Thanks.

Please file a bug report and include a sample project.

I’ll try and find the time to mock up a sample project and file the report, I was hoping this was a known issue.

Thanks.

Hello dchan, I’ve submitted the bug report with the explanation and an example simplified project that shows the problem.

Thanks.

What is the case #?

Case 28141, thanks :slight_smile:

Well, the bug was confirmed by the tech team, but for now they can’t tell if it’s their bug or the Facebook API’s bug, also, they don’t consider this a priority bug, as if a Facebook connectivity issue is not a problem in this day and age of constant Facebook involvement with everything we do online… well, that’s it I guess for this bug.

Please file a bug report and include a sample project.

I’ll try and find the time to mock up a sample project and file the report, I was hoping this was a known issue.

Thanks.

Hello dchan, I’ve submitted the bug report with the explanation and an example simplified project that shows the problem.

Thanks.

What is the case #?

Case 28141, thanks :slight_smile:

Well, the bug was confirmed by the tech team, but for now they can’t tell if it’s their bug or the Facebook API’s bug, also, they don’t consider this a priority bug, as if a Facebook connectivity issue is not a problem in this day and age of constant Facebook involvement with everything we do online… well, that’s it I guess for this bug.