skip to Main Content

Facebook supports submitting an application for review that leverages their Messenger Platform, for example see documentation here: https://developers.facebook.com/docs/app-review/resources/sample-submissions/messenger-platform/.

However, as best I can tell they have dropped support for any application using Messenger Platform. I’m hoping someone can confirm whether this is true. If I had more time I would make this shorter.

Exhibit A: Bug Reporting is Disabled

You cannot submit any bugs for the Messenger Platform. Go to https://developers.facebook.com/support/bugs/create/ and select your Facebook app then under "Affected Product" select "Messenger Platform", and notice that any sub-choice here shows this message:

We regret that support is unavailable for this product

Advanced technical support via this channel is no longer publically available for this product. Instead, these issues will be supported via the Developer Community Forum. We believe engagement through the community will aid collective understanding of our products and we are continuously improving the experience on the forum. We will also regularly monitor the forum so to support developers on critical issues facing their business.

We apologize for any inconvenience and welcome any feedback or feature requests related to the community forum to make it the most effective channel possible. Thank you!

enter image description here

Exhibit B: Test Users are Disabled

Facebook recommends providing Test Accounts as part of the review process, see:

And, app reviewers from Facebook reinforce this in their feedback:

  • We have had 13 app review rejections since Aug 2023 and every one mentions test users, here are some excerpts:
    • App rejected – Unable to verify use case experience in app, Developer Policy 1.9 – Build a quality product: "2. Provide correct test credentials"
    • App rejected – Invalid or insufficient credentials provided, Developer Policy 1.9 – Build a quality product: "your app’s test credentials did not allow us to fully review the content of the app or there were no test credentials provided for us to use during our review"
    • App rejected – Unable to verify use case experience in app, Developer Policy 1.9 – Build a quality product: "provide us with a working FB account test credential"
    • App rejected – Unable to verify use case experience in app, /etc/resolv.conf: "please provide a Facebook test credentials"
  • My Facebook business support message received the recommendation to "provide valid Facebook test credentials"

However, test users cannot be created, see https://developers.facebook.com/docs/development/build-and-test/test-users, which has had this message since at or around Feb 2023:

We are temporarily removing the ability for apps to create new test users. This should not affect existing test users. We will share an update once access to creating new test users has been reinstated.

enter image description here

AND, importantly, fake accounts violate policy, see https://developers.facebook.com/docs/app-review/submission-guide/common-mistakes "You used a fake account" with the recommendation to instead "create a test user".

It seems there is 1 primary bug report for this:

2023-03-15 https://developers.facebook.com/support/bugs/212115691400384/?comment_id=212244461387507 – Meta says not creating test accounts "is By Design" and to instead "try with app roles" (I assume this means to use fake accounts?)

And, many community threads. I could not find any thread where Meta comments.

Part of the confusion as well is that Facebook App Review staff appear to (mostly?) be in Philippines which may prevent real user accounts from being logged into (eg. a FB account created in the US will get a "credentials are invalid" error when logging into from Phillipines). I experienced the lockout too by using BrowserStack and switching to Philippines, but I noticed by logging into US then switching to PH using same session I got passed, and then repeated logins from PH worked, but still reviewers report they can’t login. I see https://developers.facebook.com/community/threads/215832727746738/ suggests giving reviewers "access credentials for the Gmail account that you used to create the Facebook account as well".

UPDATE 2023-11-02: I got a reply from Meta Support saying to create real accounts (despite this violating their policy, to my understanding):

create a real Facebook account

My next question to them will be: if we provide credentials but the reviewers cannot login due to geo-restriction (or other security lockouts we can’t control), what do we do?

Exhibit C: Reviewers Cannot Receive Messages

There seems to be a primary bug stating that test users cannot receive messages from real apps:

2023-09-25 https://developers.facebook.com/support/bugs/319543153939123/ "(#-1) Unexpected internal error" – LOTS of discussion about rejections for apps with "pages_messaging"

Then, a large number of threads talking about app review rejections because reviewers cannot receive messages (which has happened to me a dozen times):

My understanding of this bug is that entities in Facebook’s test world (mostly) can’t interact with entities in Facebook’s live world. So, if you want a test user to talk to a test page you need to do so through a test app. However, test apps can’t be logged into due to the error "App not active, This app is not accessible right now…"

So, you have to have real users, real pages, and a real app OR test users, test pages, and a test app. Using real users violates the Facebook terms and cannot be logged into by reviewers because of geo-lockout (or other reason), and test users cannot be created nor can test apps be used.

Conclusion: Kobayashi Maru?

This is a no-win scenario. Test user creation is required but "temporarily disabled" for the last 8 months, you can’t file a bug to get support because Meta has said they no longer support Messenger Platform, Meta isn’t involved in the community queues for related issues, Business support is repeating similar information as reviewers and existing documentation, reviewers are rejecting apps not on the basis of any policy issue but because they can’t login to real user accounts, and reviewers can’t use their own test accounts because of the bug (319543153939123).

Has Facebook dropped support for approving messaging based apps?

I see a few people claiming they have gotten apps approved, but I don’t know if those were because of chance (brute force plus "human error" on the reviewer’s side), or because they were non-messaging based apps, or because they had "Advanced Access" on "pages_messaging" permission granted or overridden by Meta support (see Meta’s comments on 319543153939123 where they manually override the reviewer’s rejection and grant "Advanced Access").

Note: I haven’t mentioned Instagram here because it has additional issues that would make this too lengthy (there is undocumented configuration to get it to work during app review process).

I’ve read through all the bugs, community threads, Stack Overflows, Facebook docs, taking the app review surveys, filing business support bugs, using app review chat support. I would have expected somewhere someone would explain how to work around the 319543153939123 bug or how to provide a real Facebook account, OR someone to say explicitly that all messaging app reviews are on hold.

2

Answers


  1. I have been attempting to get an app approved for pages_messaging for two months now, to no avail. Facebook continually denies my application, claiming that my app has a technical issue and cannot respond to their requests. Nonetheless, my app is processing all the information and sending a response, but it’s rejected by the Facebook Graph API because pages_messaging is not approved.

    I suspect they have terminated support for apps but haven’t been clear about it. It’s absurd that I am required to have pages_messaging enabled just to request permission to use pages_messaging!

    Login or Signup to reply.
  2. On November 2, 2023, an individual from Facebook – who utilized account number 7639600659389614 – communicated with my chatbot, potentially related to this thread. There were no issues with the bot’s response time; it managed to reply to all inquiries within a span of fewer than three seconds:

    2023-11-02 23:01:40
    I have a question. Can you help?

    2023-11-02 23:01:42
    Sure, I’m here to help! What do you need assistance with?

    2023-11-02 23:01:53
    Help

    2023-11-02 23:01:54
    Of course! How can I assist you today?

    2023-11-02 23:02:04
    Menu

    2023-11-02 23:02:06
    I’m sorry, but I’m not able to provide a menu as I am a text-based AI assistant. However, I can assist you with various tasks or answer any questions you may have. How can I assist you today?

    2023-11-02 23:02:20
    What time is it?

    2023-11-02 23:02:22
    It is currently [current time]. How can I assist you futher?

    Believing that the bug might have been rectified, I resubmitted my application (ID: 800061748303885), requesting only pages_messaging approval.

    An attempt was made to verify the account from account number 7160766827275260 today. However, the chatbot was not able to reply to any messages due to the Facebook 2018012 error, indicated in the log below:

    [07:07, 05/11/2023] [ERROR] Error in send_message to 7160766827275260, API return is: 400 and error is b'{"error":{"message":"(#-1) Erro interno inesperado","type":"OAuthException","code":-1,"error_subcode":2018012,"fbtrace_id":"Ag7-HuoZEB6nyEqH5EC-AqD"}}’

    [07:07, 05/11/2023] [ERROR] Error in send_message to 7160766827275260, API return is: 400 and error is b'{"error":{"message":"(#-1) Erro interno inesperado","type":"OAuthException","code":-1,"error_subcode":2018012,"fbtrace_id":"ADVIlvfqbG3UvLqzC24qGNn"}}’

    [07:08, 05/11/2023] [ERROR] Error in send_message to 7160766827275260, API return is: 400 and error is b'{"error":{"message":"(#-1) Erro interno inesperado","type":"OAuthException","code":-1,"error_subcode":2018012,"fbtrace_id":"ABG3cPIiETpJShA1wqMLX_5"}}’

    [07:09, 05/11/2023] [ERROR] Error in send_message to 7160766827275260, API return is: 400 and error is b'{"error":{"message":"(#-1) Erro interno inesperado","type":"OAuthException","code":-1,"error_subcode":2018012,"fbtrace_id":"AoFIvBaWQ5AnZ9NCjBevasw"}}’

    Login or Signup to reply.
Please signup or login to give your own answer.
Back To Top
Search