We have a meta tracking pixel on a client website, embedded and tracking correctly using google tag manager. We also show some of the content from the site embedded in a web view in their Android app. We've noticed tha the Webview is throwing an error as the Pixel javascript attempts to access http://localhost. Android, by default since Android 9 disallows cleartext http connections unless explicitly enabled. We don't wish to enable this as it could be insecure. I have two questions 1. Anyone know why it accesses http://localhost ? 2. Why does it do it over an http not https? 3. could this be caused by a misconfiguration?
It is in the javascript retrieved from https://connect.facebook.net/signals/config/?v=2.9.167&r=stable&domain= &hme=&ex_m=
I did try and change the version and some time back, this code didn't reference localhost.
Is there some way I can disable this?

We have thousands of clients who want us to run their Facebook Pages for them and we have a big problem because we can only send 6 requests. For each next request we have to either wait for one of the clients to approve their request or to delete some of the old requests in order to send more. Is there a possibility to increase this limit in some way?
This is endpoint we use for sending requests: POST https://graph.facebook.com/v19.0/{business-id}/client_pages

Dear Developers,
We are currently using the Facebook API to support our company's services. Recently, we have been receiving notifications in the developer console indicating that we need to upgrade our Facebook Graph API version (*1). At present, our app is utilizing version 14.0, and since the support for this version will end on September 17, 2024, we are required to upgrade to v15.0 or higher.
However, when we checked the API Upgrade Tool in the developer console, it shows a message (*2) stating that there are no changes or available upgrades between v14.0 and v20.0. This has made it difficult for us to proceed with upgrading the API version on our own, as the tool does not provide any guidance on how to perform the migration.
We would greatly appreciate your advice or guidance on the following:
How should we proceed with upgrading to v15.0 or higher in light of the message in the API Upgrade Tool? Are there any specific steps we should follow to ensure a smooth transition and avoid potential service disruptions? Your expertise and assistance would be highly valuable to us as we navigate this situation.
Thank you in advance for your help.
(*1)Your App is currently accessing Graph API v14.0 which will reach the end of its 2-year lifetime on 17 September, 2024. We estimate 5 endpoints that calls will be impacted by this change and may stop working after the automatic upgrade push. To ensure a smooth transition, please migrate all calls to Graph API v15.0 or higher. Use the API Upgrade Tool to understand exactly how this change will impact your app.
Note: If you do not see any impacted calls in the API Upgrade Tool, your app/code may not be affected by this upgrade.
Visit our changelog to see the full list of changes in all Graph API versions.
(*2)Your app has no changes for the methods you selected between v14.0 and v20.0

I've been making requests to the Product Catalog Products API using this URL:

https://graph.facebook.com/v20.0/[PRODUCT_CATALOG_ID]/products?access_token=[ACCESS_TOKEN]&filter={"name":{"i_contains":"Water"}}&fields=["retailer_id","name","description","price","visibility","inventory","url","image_url"]

Until recently, everything worked fine, but now the response only returns the name field. Here's an example of the response I'm getting:

{     "data": [         {             "name": "Water"         }     ],     "paging": {         "cursors": {             "before": "[BEFORE_CURSOR]",             "after": "[AFTER_CURSOR]"         },         "next": "[NEXT_URL]",         "previous": "[PREVIOUS_URL]"     } } 

The fields such as description, price, visibility, and others are missing. Has anyone encountered this issue, or are there changes to the API that I may have missed?

Please find and help to resolve this number pending issue.