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?

While editing a message template whatsapp manager, the page wouldn't open. It loaded for a while and then refreshed itself continously. I waited to see if the edit page would appear, but instead, I received a temporary ban stating that I had misused the feature. I understand the ban condition, but it wasn't my fault—the page kept reloading and triggering the request.

I have created an app on the Facebook Developer platform and set up a WhatsApp webhook for sending and receiving messages. In the WhatsApp API setup, I added two phone numbers; the first one is working fine, but the second one shows a status of "pending." Both my business and WhatsApp accounts are verified, and a payment method has been added. The only difference between these two accounts is that the number with the "pending" status does not have two-step verification enabled. I tried adding it via the Graph API, but it returned an error stating that the account is not registered. In short, I need assistance in getting my mobile number connected instead of showing "Not applicable" or "pending." Your help in this matter would be greatly appreciated.

I was requesting Advanced Access for the instagram_graph_user_profile permission, but all of a sudden it is removed from my app review stage. When I go back to the Permission and Features section and hover on it, I get a prompt "This is not available in advanced access". Note: It shows available in my other apps. Also, I have verified my business and made sure I am on the right track.

API set up with Instagram Login.

Seeing the error in the attached screenshot.

• The callback URL is a Railway.app domain

• The verify token is a unique code that is self generated.

• After entering these details, we should see a GET request on our server logs - I do not see anything.

And I receive an error code: The callback URL or verify token couldn't be validated. Please verify the provided information or try again later.

More information: https://developers.facebook.com/community/threads/1460022321208053/?post_id=1460022324541386

we tried this multiple times over different days, and tried different length codes with varying characters.