Problem Description
Customer adds a Facebook.authorize(); from an app, without any results.
Actual Results
The function never goes and logs into facebook.
Expected results
The app should be able to login into fb
Test Case
1. Create a new mobile project
2. Add the code in the example to a button
3. Run it
wishToShareViaFacebook.addEventListener('click', function(e){
if (e.index == 0) {
if (Titanium.Facebook.loggedIn) {
var data = { link: "www.jokwear.com", name: "Great Apparel, Great Message", message: "Check out JokWear!", caption: "Follow your favourite athletes, support other athletes", picture: "http://jokwear.com/images/joklogo.gif", description: "JokWear is a clothing brand that not only touts excellent fabric but also a social movement that you can achieve anything you set your mind to.", test: [ {foo:'Encoding test', bar:'Durp durp'}, 'test' ] }; Titanium.Facebook.requestWithGraphPath('me/feed', data, 'POST', showRequestResult);
} else {
Titanium.Facebook.authorize();
}
}
});
Extra info
There is a bug where platform didn't want to launch the FB authorize from a dialog, since it's bad practice to get a dialog from a dialog. So, we recommended the customer to add an app event catching this, closing the dialog and then adding the other dialog. It's not runnning.
The customer creates a small function doing a setTimeout, and that way, the function it's called properly within the if.
Mauro - Please provide the complete environment information for these tickets.
Done. Best, Mauro
Aha. I think I get at what's happening here. I might be able to modify Kitchen Sink to recreate the situation. Basically, since the dialog is a real UI window and becomes the key window, the FB module tries to insert itself into the dialog as it goes away.
Mauro, does this describe what you're seeing?
Pull https://github.com/appcelerator/titanium_mobile/pull/2018 pending.
Yes, that's the behavior! TY! M
Closing ticket due to time passed.