Closed GoogleCodeExporter closed 9 years ago
It has to authenticate with facebook first. If you are already logged on to
facebook then you see only this message. If it does it only on your first
message to facebook it is the expected behaviour. If it does it every time then
it is a problem. What is your case? Does it happen on the first message, every
time you start firefox ?
Original comment by chstath
on 4 Mar 2011 at 10:13
Every time I start firefox.
I don't understand this behavior, other plugins doesn't.
firestatus is already authorized to access facebook. Why is it necessary this
authentication additional!?
Original comment by si...@simonbcn.net
on 4 Mar 2011 at 10:20
https://developers.facebook.com/docs/authentication/
Original comment by si...@simonbcn.net
on 4 Mar 2011 at 10:21
Ok. It is probably some kind of bug. It would be helpful if you could send me
some firefox configuration. Enter 'about:config' in the address bar, type
firestatus in the filter and send me everything (as a screenshot or whatever
suits you).
Original comment by chstath
on 4 Mar 2011 at 10:25
Original comment by si...@simonbcn.net
on 4 Mar 2011 at 10:31
Attachments:
I don't sure about this problem. The facebook documentation is confuse to me
and I haven't any experience with social apps. But I think one possible
solution is to request the offline_access permission:
"....In addition to the access token (the access_token parameter), the response
contains the number of seconds until the token expires (the expires parameter).
Once the token expires, you will need to re-run the steps above to generate a
new code and access_token, although if the user has already authorized your
app, they will not be prompted to do so again. If your app needs an access
token with an infinite expiry time (perhaps to take actions on the user's
behalf after they are not using your app), you can request the offline_access
permission." (https://developers.facebook.com/docs/authentication/)
Don't you think?
Original comment by si...@simonbcn.net
on 7 Mar 2011 at 2:33
Original comment by chstath
on 14 Apr 2012 at 3:48
Original issue reported on code.google.com by
si...@simonbcn.net
on 4 Mar 2011 at 10:06Attachments: