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.

⚠️Ad Library Report
⚠️Some disruptions: Ad Library Report Sep 11 2024 12:43 AM GMT+6
We have identified an issue with the spend calculations being incorrectly reflected in the Ad Library Report for some advertisers. We are currently working to resolve the problem and will provide an update here when resolved.

Our website displays multiple payment bank options, each linked to a corresponding native mobile application using deep links (e.g., app://q?qPay_QRcode=...). The functionality was working seamlessly across all browsers, including Safari, Chrome, and in-app browsers like Messenger’s, up until August 2024.
Deep links to native banking apps still work flawlessly in Safari and Chrome. However, in the Messenger in-app browser, clicking on a deep link to open a native banking app does not trigger the native app as expected. Instead, the user is redirected to the app store, even if the application is already installed on their device. Notably, the Messenger-specific fb:// deep links continue to function properly in the same environment, indicating that the issue is isolated to third-party app deep links (such as banking apps).
This issue disrupts the payment flow for users who access our website from Messenger, leading to confusion and inconvenience. Users are unable to seamlessly transition from our web interface to their native banking apps, negatively impacting their overall experience. As the issue persists only in the Messenger in-app browser and does not affect other browsers, we believe this to be a change or restriction introduced specifically within Messenger's handling of external deep links.

Hi I recently received a required action for "Platform Terms 3.b.i-iii - App does not request users to grant permission We found that your app has access to the user_age_range permission, but your app's use of this permission is not allowed. This violates Platform Terms 3.b.i-iii."
But our app no longer required this permission, but the reviewer response keep asking us to remove it from "app dashboard" which we have no idea where to remove except for the permission / feature section, which we already did.