Messenger Platform · error code

Messenger error 2071011: Messenger Extensions are not enabled

ConfigurationGeneric & request errors

Last verified against Meta for Developers - Messenger Platform error codes

What Messenger returns
Messenger Extensions are not enabled - could be "messenger_extensions" was not set on a url, the domain was not added to the allow list or this is an outdated version of Messenger client

What error 2071011 means

Code 2071011 is the most common Messenger Extensions SDK failure, and its message lists the three usual causes: "Messenger Extensions are not enabled - could be "messenger_extensions" was not set on a url, the domain was not added to the allow list or this is an outdated version of Messenger client."

Each part is a separate requirement. The URL button or persistent menu item that opens the webview must set messenger_extensions: true; without it the page opens as a plain webview and the SDK cannot attach. The page's domain must be on the Page's allow list, set through the whitelisted_domains property of the Messenger Profile API, and the Extensions guide notes that all domains on your page have to be listed. And the person's Messenger client must be recent enough to support the SDK.

Because the SDK loads either way, the page looks fine until the first SDK call fails, typically getContext(). If only some people see the error, suspect the client version; if everyone does, it is configuration.

What it looks like

{
  "type": "web_url",
  "url": "https://example.com/form",
  "title": "Open form",
  "messenger_extensions": true
}

Why it happens

  • The URL button or menu item opening the page lacks messenger_extensions: true.
  • The page's domain is missing from whitelisted_domains in the Messenger Profile.
  • Redirects or subdomains: the final domain differs from the one allow-listed.
  • Opening the URL from a plain link in a text message instead of a configured button.
  • Outdated Messenger clients.

How to fix Messenger error 2071011

  1. 1Set messenger_extensions to true on every URL button and menu item that opens the page.
  2. 2Add the exact https origin to whitelisted_domains via POST /me/messenger_profile and confirm it with a GET.
  3. 3Remove redirects so the webview loads directly on the allow-listed domain.
  4. 4Allow the profile change time to apply, then reopen the webview from a fresh button.
  5. 5If only some people fail, ask them to update Messenger.

How to stop it recurring

Keep allow-listed domains in your Page setup script, not as a one-time manual step, and generate URL buttons from one helper that always sets messenger_extensions. Add a check in the webview that reports SDK init errors to your server. Menu configuration rules are in the Messenger limits reference.

Official reference: Meta for Developers - Messenger Platform error codes. See all Messenger error codes or the Messenger limits and quotas.

Related codes

Error 2071011 - quick answers

What does Messenger error 2071011 mean?

Code 2071011 is the most common Messenger Extensions SDK failure, and its message lists the three usual causes: "Messenger Extensions are not enabled - could be "messenger_extensions" was not set on a url, the domain was not added to the allow list or this is an outdated version of Messenger client." Each part is a separate requirement.

How do I fix Messenger error 2071011?

1. Set messenger_extensions to true on every URL button and menu item that opens the page. 2. Add the exact https origin to whitelisted_domains via POST /me/messenger_profile and confirm it with a GET. 3. Remove redirects so the webview loads directly on the allow-listed domain. 4. Allow the profile change time to apply, then reopen the webview from a fresh button. 5. If only some people fail, ask them to update Messenger.

Stop debugging Messenger by hand

Connect the channel through Conferbot: tokens, webhooks and retries are handled, failures show as readable status.