Partial Outageshare-external
Whatsapp Embedded Signup cannot authorize
11

This is the error we got after we use this link to authorize our whatsapp account for testing authorization

https://www.facebook.com/v20.0/dialog/oauth?response_type=token&display=popup&client_id=813375437548289&redirect_uri=https%3A%2F%2Fdevelopers.facebook.com%2Ftools%2Fexplorer%2Fcallback&auth_type=rerequest&config_id=890487576457728

It just go white after we select our verified phone number.We tried with different phone numbers . All go white after we verified them. What could be the issue?

```javascript p4ALoIvfokR.js:70 ErrorUtils caught an error:

Invalid stepID provided

Subsequent non-fatal errors won't be logged; see https://fburl.com/debugjs. ```

Yongrui
Asked about a month ago
De

Getting the same error from something that was working perfectly all along :(

October 27 at 12:14 AM
M M Mirazul

I'm encountering the same issue; it appears to be a Facebook bug. Please let me know if anyone finds a solution for this.

October 27 at 9:52 PM
Take

Meta announced the issue and expect it to be fully resolved within a couple of hours: https://metastatus.com/whatsapp-business-api

Recovering from disruptions: Embedded Signup Oct [...]:01 PM GMT+3 We are recovering from the Embedded Signup issue and expect it to be fully resolved within a couple of hours. Thank you for your patience.

Some disruptions: Embedded Signup Oct 28 2024 2:24 PM GMT+3 We are currently experiencing an increase in errors with the Embedded Signup for WhatsApp Business Account(WABA) creation. Our team is actively working on resolving this issue as a priority. We apologize for any inconvenience this may cause and appreciate your patience as we work to resolve the problem.

October 28 at 8:33 AM
Selected Answer
1

I am also getting the same error, it started yesterday. Before it was working perfectly fine.

October 26 at 9:09 PM
Manish
Ricardo

Same here. It was working, but without any explanation, it stopped working.

October 27 at 7:12 AM
San

Same here- friday 24 was working- suddenly this error - How can we contact to meta ? - Will they come back here?

October 27 at 8:56 AM
Ricardo

I don't know if it's possible to contact Meta directly. But I've seen in other topics official Meta developers responding and suggesting solutions.

October 27 at 5:23 PM
San

I think it´s resolved now - It is working for me now

October 29 at 2:34 AM
1

I am also getting same error. If anyone found any solution, please update here

October 27 at 3:43 AM
Dhiraj
Ricardo

I'm regularly revisiting this topic waiting for a solution. If I find the solution, I'll post it here immediately.

October 27 at 7:14 AM
1

Another similar case, check this topic: https://developers.facebook.com/community/threads/1375786556731748/

October 27 at 7:36 AM
Ricardo
1

I am also getting same error

October 27 at 7:41 AM
Abbas Eren
1

I'm encountering the same error. If anyone solves it, please post it

October 27 at 1:20 PM
Leo
1

I'm having the same issue. This is the worst experience connecting a service I have ever had in 20 years. what a bullshit service

October 28 at 6:12 AM
Fineguide
1

I think, issue is resolved now

October 28 at 10:40 AM
Manish
Sayantan

Yes, Problem is solved from my side also

October 28 at 1:51 PM
2

Same issue here, I am about the throw the towel here, it's been 2 weeks I am wrestling with Embedded sign up, it was supposed to smooth the onboarding of my users, instead I am getting wrecked.

October 26 at 2:30 PM
Özgür
Ricardo

I've also been trying for days to successfully build the embedded sign-up but haven't managed yet. I'm feeling exhausted and stressed too, but I won't throw in the towel. When I succeed, I'll try to help you guys here.

October 26 at 3:33 PM
2

I am seeing the same error. Nothing changed and all of sudden it happened. (On my test APP)

October 27 at 2:12 PM
Robin
Ricardo

In my case, this problem also occurs in my test APP.

October 27 at 5:25 PM
M M Mirazul

We are facing the same issue. It's getting blank just after few step and doesn't complete the process. I think it's a bug from Facebook end

October 27 at 9:51 PM
Muraduzzaman

Facing the same issue, My customer are not able to connect their WhatsApp number, it's getting blank and error in console. Please fix the issue as soon as possible.

October 28 at 12:07 AM
Manish

Still the same issue

October 28 at 3:24 AM
Manish

Meta has acknowledged this issue - https://metastatus.com/whatsapp-business-api

October 28 at 5:52 AM
2

same error when i select the phone number or add a new one i get a blank page with that error on console.

October 28 at 3:50 AM
Daniel
4

I'm getting the same error. If you find a solution, post it here.

https://www.facebook.com/v21.0/dialog/oauth?app_id=1062946508282086&cbt=1729966639773&channel_url=https%3A%2F%2Fstaticxx.facebook.com%2Fx%2Fconnect%2Fxd_arbiter%2F%3Fversion%3D46%23cb%3Dff50bccab67b76846%26domain%3Dprodutivi.com.br%26is_canvas%3Dfalse%26origin%3Dhttps%253A%252F%252Fprodutivi.com.br%252Fff691f099b43d3632%26relation%3Dopener&client_id=1062946508282086&config_id=1977844512715505&display=popup&domain=produtivi.com.br&e2e=%7B%7D&extras=%7B%22setup%22%3A%7B%7D%2C%22featureType%22%3A%22%22%2C%22sessionInfoVersion%22%3A%222%22%7D&fallback_redirect_uri=https%3A%2F%2Fprodutivi.com.br%2Ffacebook&locale=en_US&logger_id=f11f73b2740dfa655&origin=1&override_default_response_type=true&redirect_uri=https%3A%2F%2Fstaticxx.facebook.com%2Fx%2Fconnect%2Fxd_arbiter%2F%3Fversion%3D46%23cb%3Df8755dc4481d70311%26domain%3Dprodutivi.com.br%26is_canvas%3Dfalse%26origin%3Dhttps%253A%252F%252Fprodutivi.com.br%252Fff691f099b43d3632%26relation%3Dopener%26frame%3Df5e286c46ebe6432c&response_type=code&sdk=joey&version=v21.0

DevTools - Console:

p4ALoIvfokR.js:70 ErrorUtils caught an error:

Invalid stepID provided

Subsequent non-fatal errors won't be logged; see https://fburl.com/debugjs.
October 26 at 11:27 AM
Ricardo
Sayantan

Same issue from our side

October 27 at 11:01 PM