Facebook adapter not working?

[elsigh]

I tried using it for a project and then tried the demo extension in the tree, and in both cases after loading the extension a tab opens up in chrome on the Facebook robots.txt page but the JS code doesn't end up executing the query with the token. Guessing something might've changed with how the end of the auth callback works? But with the demo, each time I click the browser action icon, a new tab opens but my music never gets populated.

[elsigh]

Additionally, it would be cool to know what the settings are on the Facebook app itself. Was it Website with Facebook Login with Site URL configured to to the robots.txt endpoint? (That's what I did in my attempt and got the same behavior with the demo extension)

[elsigh]

Wonder if this might not be relevant: http://stackoverflow.com/questions/8675362/how-do-i-get-facebooks-new-oauth-2-0-access-token-with-javascript-in-google-chr

[neocotic]

I'll have a look at this later as, although that SO answer says it needs a special return, I'm not sure why this implementation isn't working. This framework doesn't actually follow the desktop flow as it tricks API's into believing it's a normal website at <target_site>/robots.txt which we override to redirect you back to the extension and finalise the process.

However, if facebook are doing something special this will need to be looked into. Unfortunately, my work blocks facebook so I can't quickly test this right now.

[borismus]

Confirm. The FB sample stopped working for me too.