Facebook recently warned us that our app will be restricted due to violation of our Platform Terms and Policies. They asked to provide more information including login credential of test or debugging user.
As response, we provided link to the app and credential of a test user to log into the app through URL. We tested the app and URL using the same credential to make sure it's working, and for sure it was fine.
In spite of all the details we provided, Facebook is still warning us and restricting our app to be accessed by publice. We don't understand what have missed and why it's still complaing about the violation however wer provided a valid credential and valid URL to the app!

I'm trying to get App review for being able to ask for permission to user and after that being able to publish a carousel on the linked account.
I've added the Instagram test account and test the all process (that works and can be done many times). But when I submit it I get the response in the attached image.
For my request I've put a video showing the all process from the connection to my app to the publishing process + addes a proof that it work.
And I have give the following explanation (I've just hide the credentials to post it here) :
Hello, here are the explanations for all the steps to process the Instagram OAuth + creating and publishing content.
Step 1 : Go to page https://app.eazia.fr/version-test and login with the user - mail : "XXXXXX" and password : "XXXXXX" Step 2 : Check the Instagram checkbox and click on the button "Continuer", it will redirect you to the Intagram OAuth Step 3 : Log with the following Instagram account - mail : "XXXXXX" password : "XXXXXX" Step 4 : Accept all the autorization and you will be redirect to https://app.eazia.fr/version-test/onboarding/linksuccess where you need to click on the button "Générer vos posts avec eaZia" to continue Step 5 : Click on the burger menu into the navbar and click on the "Posts" menu Step 6 : You have been redirected to https://app.eazia.fr/version-test/workspace_user/posts/draft and now click on the only post you can see Step 7 : You have been redirected to https://app.eazia.fr/version-test/workspace_user/edit?post=1726477073340x417398956456673300. Scroll down to the bottom of the page where you can locate the button "Publier", click on it. Step 8 : After the click the images are put in a carousel which is published on the Instagram account "edukare.finance.center" after 20 to 30 seconds.
If you have any issue with one of the step please keep us inform on what is the step which is problematic and what is the exact problem. Regards.
The thing is when I check the logs of my application I can see that there is no connection attempt and no attempt to access to my webapp during the "checking phase". Can you help me please ?

this code error is not in the documentation. Can we know more about this ??

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?

We have an App with multiple Ad-Accounts.
We use the Webhook 'leadgen'. The Callback-Url is verified and the hook works for most Pages.
We tried to add a new page recently, but no leads are sent. We have created a new access token with the following permissions:
pages_show_list, ads_read, ads_management, leads_retrieval, pages_read_engagement, pages_manage_metadata, pages_manage_ads
In the Access Token Debugger https://developers.facebook.com/tools/debug/accesstoken the page shows up correctly in the permissons table.
On the Lead Ads-Testtool however https://developers.facebook.com/tools/lead-ads-testing we get the message 'no Webhook-Subscripton for Leads Ads'.
In the Graph API Explorer the page also doesn't show up under Page-Tokens, even though we can and did chose it when creating the token.
The person creating the Token is an Admin on the App. The webhook works fine for all other pages.
What's going on?