$FB.Event.subscribe about angular-easyfb HOT 7 CLOSED

Hi @karypid ,

The module does support FB.Event.subscribe, which is used in the implementation of ezfb-xfbml directive.
I'll try to recreate your situation and figure out where the problem is ASAP.

Thank you for the issue!

from angular-easyfb.

I just created a plunk according to your description.

http://plnkr.co/edit/lgijTPgOuqpdiEmi7R7V?p=preview

Which seems to work fine.

Though I do find a bug unrelated to your problem, and I'll open a new issue for myself.

from angular-easyfb.

Interesting! The plunk does work and it's exactly what I'm doing! It seems like there's something in my set-up that's causing this...

Basically, I am using a yeoman scaffold (yo angular) and testing with "grunt server".

I copy pasted your plunkr demo into my project as follows:

• copy-paste plunkr/app.js into app/app.js
• copy-paste plunkr/index.html into index.html
• copy-paste plunkr/home.html into app/views/home.html
• copy-paste plunkr/login.html into app/views/login.html

I edited the routes to add the views/ prefix and app.js to define my own app id. Running "grunt server" fires up the browser (firefox) and shows the home.html view which displays (even though I am logged into facebook):

{
"status": "unknown"
}

The login view shows the facebook icon. I can log in via the pop-up but when the pop-up closes I still see the facebook logo prompting me to login (as if I haven't logged in). Going back to the home view I see the same "unknown" status.

I wonder if node.js requires some extra configuration...

from angular-easyfb.

Ok, can you try your plunk with Firefox version 26? That's the one I'm using and it seems to have the problem...

I use Chrome for general browsing and Firefox for dev testing. So I visited your plunk with Chrome and then tested my app with Firefox (doesn't work).

I just tried the plunk with Firefox and it doesn't seem to work for me...

On the bright side, I tried my app with Chrome and it does indeed work!

from angular-easyfb.

Hi @karypid ,

I just have the plunk tested on my Firefox 26, and it works.

I guess the issue has something to do with your development environment.

Facebook SDK may have to notify the events through some cross domain technique, which means you might need some configuration for the localhost development.

When I was setting up the demo page on plunker, I've configured the plnkr-demo app to be able to work with run.plnkr.co too.

from angular-easyfb.

BTW, the configuration I mentioned is the Facebook App configuration, which is configurable at

https://developers.facebook.com/apps

from angular-easyfb.

I still can't figure out why my Firefox doesn't work. For the moment I am using Chrome which seems to work fine.

In any case, I don't think this is an angular-easyfb issue. I stepped through the code and the only difference seems to be the random identifier generated when forming the URL param to pass to the arbiter. In the network log, I can see that Facebook genuinely returns an unknown status for the request.

I will keep looking into this when I have more time, and post back when I figure it out...

from angular-easyfb.