Posts under category Facebook Javascript SDK

Starting December 21st all API requests coming from Heroku get blocked by FB. Requests coming from local machine with whitelisted IP continue to work. Ran a script to identify Heroku IP and added that IP manually to whitelist but this is not scalable since Heroku assigns IPs dynamically. Has anyone else started seeing this issue recently? Any feedback from FB?

We have implemented Facebook login on our React application. Our "Log in with Facebook" button's click handler calls FB.login. We have supplied a callback to FB.login that handles the response and authenticates with our backend using the provided access token.
The works in most cases - except if the user has two-factor authentication enabled on their Facebook account. In this scenario, if the user successfully goes through the flow in the Facebook popup to complete two factor authentication and verify their identity, the popup closes - but the response object supplied to the FB.login callback has a status of "unknown" and does not include an access token.
The user must then click "Log in with Facebook" a second time, and only then is a successful auth response supplied to the FB.login callback.
Looking for support in handling this scenario so that the user does not need to click "Log in with Facebook" twice in order to authenticate with our app.

Since 5th September, our internal JS error tracking has been flagging failed fetch requests to localhost:12387. No changes have been made on our side, and the existing Facebook tracking pixel we use loads via Google Tag Manager.
Specifically, on closer inspection, the config file found at - https://connect.facebook.net/signals/config/ - has this chunk of code within it that tries to make a call to localhost.
(function(a,b,c,d){var e={exports:{}};e.exports;(function(){var f=a.fbq;f.execStart=a.performance&&a.performance.now&&a.performance.now();if(!function(){var b=a.postMessage||function(){};if(!f){b({action:"FB_LOG",logType:"Facebook Pixel Error",logMessage:"Pixel code is not installed correctly on this page"},"*");"error"in console&&console.error("Facebook Pixel Error: Pixel code is not installed correctly on this page");return!1}return!0}())return;f.__fbeventsModules||(f.__fbeventsModules={},f.__fbeventsResolvedModules={},f.getFbeventsModules=function(a){f.__fbeventsResolvedModules[a]||(f.__fbeventsResolvedModules[a]=f.__fbeventsModulesa);return f.__fbeventsResolvedModules[a]},f.fbIsModuleLoaded=function(a){return!!f.__fbeventsModules[a]},f.ensureModuleRegistered=function(b,a){f.fbIsModuleLoaded(b)||(f.__fbeventsModules[b]=a)});
f.ensureModuleRegistered("SignalsFBEvents.plugins.actionid",function(){
return function(a,b,c,d){var e={exports:{}};e.exports;(function(){"use strict";var a=f.getFbeventsModules("SignalsFBEventsPlugin"),b=f.getFbeventsModules("SignalsFBEventsEvents"),c=b.setFBP,d=f.getFbeventsModules("signalsFBEventsGetIsAndroid"),g=f.getFbeventsModules("signalsFBEventsGetIsAndroidIAW");b=f.getFbeventsModules("SignalsFBEventsLogging");var h=b.logError;b=f.getFbeventsModules("SignalsFBEventsLocalStorageUtils");var i=b.getLocalStorageItem,j=b.setLocalStorageItem,k=b.isLocalStorageSupported,l=2,m=0;e.exports=new a(function(a,b){if(g()||!d()||!k())return;c.listen(function(a,c){if(a==null||c==null||c===""||m>=l)return;a=b.pluginConfig.get(a,"actionID");if(a==null)return;var d=a.portNumber;a=a.ttlInHour;var e="aidTime",f=i(e);if(f!=null&&(new Date().getTime()-Number(f))/(1e36060) f.ensureModuleRegistered("fbevents.plugins.actionid",function(){
return e.exports})})()})(window,document,location,history);
Can anyone advise why a request exists in this file for localhost in production?

Since Sep 16 2024 20:32 UTC fetching of data using the facebook-nodejs-business-sdk has been broken in our app. When creating requests without the use of SDK, the use-cases work as expected. Root cause is described in https://github.com/facebook/facebook-nodejs-business-sdk/issues/298 tldr: The default data: {} parameter is making all get requests fail to load data. Are there any plans to fix it?

  1. 1
  2. 2
  3. 3