Can't create a test number in API configuration
3

I'm following this tutorial https://developers.facebook.com/docs/whatsapp/cloud-api/get-started but on step 2 I can't create a test number, I keep getting a red message saying that test numbers is not working and I need to contact support. Is that a workaround besides killing my personal number to turn into a bussines number? I just wanna test some stuff.

Giovane
Chiesta circa un mese fa
Charlton

I am also having the same problem: "Error WhatsApp test numbers are currently unavailable. Contact support."

For the devs... if they see this?

{
  "data": {
    "xfb_create_whatsapp_business_test_account": null
  },
  "errors": [
    {
      "message": "A server error field_exception occured. Check server logs for details.",
      "severity": "CRITICAL",
      "mids": [
        "a5fc7ecd2df5022bb3c9008a189441bc"
      ],
      "code": 2655005,
      "api_error_code": 2,
      "summary": "WhatsApp test numbers are currently unavailable",
      "description": "WhatsApp test numbers are currently unavailable. Contact support.",
      "description_raw": "WhatsApp test numbers are currently unavailable. Contact support.",
      "is_silent": false,
      "is_transient": false,
      "is_not_critical": false,
      "requires_reauth": false,
      "allow_user_retry": false,
      "debug_info": null,
      "query_path": null,
      "fbtrace_id": "Guci0oR+OR/",
      "www_request_id": "AwR1JTzneqjTd9k7eaewci4",
      "path": [
        "xfb_create_whatsapp_business_test_account"
      ]
    }
  ],
  "extensions": {
    "is_final": true
  }
}
23 settembre alle ore 14:00
Risposta selezionata
1

+1 I have the same issue I've been trying to sort for a week. Meta - please could you let us know that this is being worked on as it sounds like a platform error?

27 settembre alle ore 01:18
Rob
1

No solutions yet I guess.

27 settembre alle ore 12:19
Giovane
2

I'm experiencing the same problem, I thought it was a problem when creating the app, but when creating another one I faced the same problem, it seems to be an internal error.

23 settembre alle ore 09:59
Giosimar