Facebook/applicationResume issue reported as Case 32784 with complete sample project.
Of course software can have bugs (as long as the number is convergent).
It’s still a good channel for end-users to file bug reports but it seems Corona heavily reply on end-users (us as paying customers) to find out/sort out bugs. And they don’t allocate enough & own resources (such as QA team) to dig out more bugs proactively.
Besides, there should be higher-level plans to fix bugs.
I got a reply from CoronaLabs a few hours ago regarding my bug report.
If you don’t configure your build.settings as below, the Facebook SDK will silently crash which results in the behavior you’re seeing.
I updated my test project with these settings, and now it dispatches the applicationResume event.
You must include all of these elements in your build.settings:
settings = { plugins = { ["facebook"] = { publisherId = "com.coronalabs", supportedPlatforms = { iphone=true, ["iphone-sim"]=true } } }, iphone = { plist = { UIApplicationExitsOnSuspend = false, FacebookAppID = "XXXXXXXXXX", --replace XXXXXXXXXX with your Facebook App ID CFBundleURLTypes = { { CFBundleURLSchemes = { "fbXXXXXXXXXX", } --replace XXXXXXXXXX } } } } }
http://docs.coronalabs.com/guide/social/implementFacebook/index.html
I got the following message from CoronaLabs today.
The plugin has been fixed so that it will still dispatch a applicationResume event even if the settings are not present. Also there will now be a log message which states the issue.
I guess it’ll soon be included in an upcoming daily build.
This proves that CoronaLabs does listen, and that reporting bugs do pay off.
The plugin will not require a new daily build. Plugins go live when we fix them.
Rob
Huh! That’s true!
Sorry. I was in an “Enterprise state of mind” 
Yeah, absolutely… except that this bug is probably the least I ever cared and the couple ones I care most have been sitting there for months.
And what I was trying to say is not about this reporting channel. Anyway…
May I ask which unsolved bugs do you have that are most important to you?
I can do some testing myself, and also report it. The more reports they have, the more attention it gets.
There are a few bugs that is related to webView orientation support. I reported two bugs earlier, and Corona fix one of them, introduce more bugs, fix them, now stop. So there are still some bugs related to webView orientations that are not fixed & not reported.
There was another fix to native object resizing that went out in the past couple of builds.
If you have bug numbers, it would be helpful.
Rob
I know what have been fixing because I check the daily builds every day to see if anything related has been fixed. And I test webView orientation right away when something is being fixed, but the only thing I found is that I found more bugs & the full-screen video orientation bug is still being ignored because it lacks a product-level bug fixing plan. It is fixed only half way through and stays in this funny state.
Please provide me bug numbers. I can’t ask the engineers the status if I don’t have them.
Rob
I also see there is no “applicationResume” event from iOS devices, why it that?
I remember it was not like this before…
iOS changed something?
my app relies on “applicationResume” to do something, now it’s gone, which caused a bug.
The answer to your other question Corona has been ignoring to answer
is that… if you add system event after Facebook is required (require(“facebook”))
You will see no “applicationResume” in iOS.
So the solution is to add system event before Facebook is required. (And I implemented a simple subscriber-notification mechanism for other modules to receive the system events from a single system event listener before FB is required)
Why? I don’t know. I found this out in the hard way. Don’t thank me too much.
Is there a bug report on this?
No, I am reluctant to file new bug reports because I can’t see the bugs I already filed are going to be fixed any time soon.
Besides, I really don’t like Corona relies a lot on end-users (us, as paying customers) to find out the bugs for you. Just like this thread for example, someone already pointed out clearly that the event is missing for iOS, but it seems no one inside Corona cares to dig out further (This problem has been there for an year). Ignoring becomes a norm.
It’s totally fine if this is Corona strategy considering all the business & financial factors running the company. But I just don’t like it.
Besides, I feel Corona has a policy that never promise anything, which is also something I don’t like. I can never see any plan of bug fixing and roadmaps about this SDK future. I will take whatever it is now and make no further hope.
I haven’t used facebook myself yet, but I just tested this and it’s confirmed. If Facebook is required() before adding your own event handlers the applicationResume event fails to dispatch.
Now I’ll go {OffTopicRant=true}
I wouldn’t go so far as to say that CoronaLabs is ignoring anybody.
First of all, a single post on a forum doesn’t sound an alarm in the engineering department. There are so many topics posted every day that it’s impossible for CoronaLabs to scour through every single one of them to find potential bugs.
Secondly, *any* SDK has bugs and the only way to bring attention to them is to officially report them.
I know it might feel like a pain to file bug reports, but the fact of the matter is if anybody finds what seems to be a bug, it *must* be reported via the “Report a bug” link if you want it to get attention. Only then can CoronaLabs analyze, prioritize and schedule a fix.
It’s as simple as that…
{OffTopicRant=false}
Facebook/applicationResume issue reported as Case 32784 with complete sample project.
Of course software can have bugs (as long as the number is convergent).
It’s still a good channel for end-users to file bug reports but it seems Corona heavily reply on end-users (us as paying customers) to find out/sort out bugs. And they don’t allocate enough & own resources (such as QA team) to dig out more bugs proactively.
Besides, there should be higher-level plans to fix bugs.
I got a reply from CoronaLabs a few hours ago regarding my bug report.
If you don’t configure your build.settings as below, the Facebook SDK will silently crash which results in the behavior you’re seeing.
I updated my test project with these settings, and now it dispatches the applicationResume event.
You must include all of these elements in your build.settings:
settings = { plugins = { ["facebook"] = { publisherId = "com.coronalabs", supportedPlatforms = { iphone=true, ["iphone-sim"]=true } } }, iphone = { plist = { UIApplicationExitsOnSuspend = false, FacebookAppID = "XXXXXXXXXX", --replace XXXXXXXXXX with your Facebook App ID CFBundleURLTypes = { { CFBundleURLSchemes = { "fbXXXXXXXXXX", } --replace XXXXXXXXXX } } } } }
http://docs.coronalabs.com/guide/social/implementFacebook/index.html