facebook

问题 I'm trying to get the ad spend and mobile app installs for my app using the Facebook Graph API v2.11 for marketing. In the Graph API Explorer, when I try /act_<my account>/campaigns?fields=insights{actions,spend}&time_range={'since':'2017-07-07','until':'2017-12-12'} In the output, under "insights", I get an object of this type: "data": [ { "actions": [ { "action_type": "comment", "value": "3" }, { "action_type": "like", "value": "33" }, { "action_type": "link_click", "value": "1531" }, {

问题 Have you ever noticed how facebook says “3 friends and 33 others liked this”? I was wondering what the best approach to do this is. I don’t think going through the friends list, and the list of users who “liked this” and comparing them is efficient at all! Do they keep a track of this in the database? That will make the database size very huge. What do you guys think? Thanks! 回答1: I would guess they outer join their friends table with their likes table to count both regular likes and friend

问题 I am setting up a Facebook login, and am successfully getting things like first_name , email , etc. However, I cannot seem to figure out how to get birthday. If I call for birthday as below, nothing returns. FB.api('/me', {fields: 'birthday'}, function(response) { console.log(JSON.stringify(response)); }) If I call user_birthday as below, I get this error: "error":{"message":"(#100) Tried accessing nonexisting field (user_birthday) FB.api('/me', {fields: 'user_birthday'}, function(response) {

问题 I am currently using a client-side React component to have a user login to Facebook via OAuth in my application. On the server-side, I use the npm package passport-facebook-token to validate the authenticity of the accessToken after a successful client-side login. One practice I do not see often is in addition to asking Facebook if the accessToken is valid, shouldn't the server also check if the email provided by the client's payload matches the e-mail coming back from Facebook? Allow me to

问题 Everything was perfectly working few days ago(till 31st August 2018 morning), suddenly the app got stuck with white blank screen. I did some debug and search on it. And found that my app is not even opening splash screen and all I get in logcat is: com.facebook.internal.AttributionIdentifiers: getAttributionIdentifiers should not be called from the main thread I also updated the Facebook SDK with latest one Facebook Android SDK 4.36.0 which seems updated on 29th August 2018. If I removed the

问题 I am currently using a client-side React component to have a user login to Facebook via OAuth in my application. On the server-side, I use the npm package passport-facebook-token to validate the authenticity of the accessToken after a successful client-side login. One practice I do not see often is in addition to asking Facebook if the accessToken is valid, shouldn't the server also check if the email provided by the client's payload matches the e-mail coming back from Facebook? Allow me to

问题 Everything was perfectly working few days ago(till 31st August 2018 morning), suddenly the app got stuck with white blank screen. I did some debug and search on it. And found that my app is not even opening splash screen and all I get in logcat is: com.facebook.internal.AttributionIdentifiers: getAttributionIdentifiers should not be called from the main thread I also updated the Facebook SDK with latest one Facebook Android SDK 4.36.0 which seems updated on 29th August 2018. If I removed the

问题 We're building a Facebook application here at work, using the iframe method. For the application to work, it needs to set cookies from within the iframe. Safari has third party cookies disabled by default, so we are currently redirecting the whole browser to our server, set the cookie required to track the session, and then redirect back to the Facebook application page again. This method works, and works good. Unless someone with Firefox comes along who has manually disabled third party

问题 We're building a Facebook application here at work, using the iframe method. For the application to work, it needs to set cookies from within the iframe. Safari has third party cookies disabled by default, so we are currently redirecting the whole browser to our server, set the cookie required to track the session, and then redirect back to the Facebook application page again. This method works, and works good. Unless someone with Firefox comes along who has manually disabled third party

问题 We're building a Facebook application here at work, using the iframe method. For the application to work, it needs to set cookies from within the iframe. Safari has third party cookies disabled by default, so we are currently redirecting the whole browser to our server, set the cookie required to track the session, and then redirect back to the Facebook application page again. This method works, and works good. Unless someone with Firefox comes along who has manually disabled third party