Error in Embeded Login after selecting WABA and Phone
The embeded setup screen just goes blank with the following error: Invalid stepID provided.
Tony-Marketing-API.cn is a vibrant community dedicated to Facebook, Meta,Google Ads api, app development, Instagram, and related technologies. It offers valuable bug solutions, troubleshooting cases, and problem-solving strategies shared by users. Stay updated with real-world solutions, development tips, and the latest trends in digital marketing and app development.
The embeded setup screen just goes blank with the following error: Invalid stepID provided.
For the last few days the instagram login api login process hasn't been working. I am using the embeded link provided in the app dashboard > Instagram > Instagram > Api Setup with Instagram Login > Step 3 and this results in a page that says "Error, please wait a few minutes before you try again". It was working for a while, but has been like this for at least the last two days.
I'm in process of registering phone number to be used with Whatsapp API, when I try to generate access token for my phone number, I'm greeted with this alert.
There was a problem registering (my phone number). Unsupported post request. Object with ID '(phone_number_id)' does not exist, cannot be loaded due to missing permissions, or does not support this operation. Please read the Graph API documentation at https://developers.facebook.com/docs/graph-api
There also this message that tells me the phone number needs to be registered.
When I attempt to follow the link, it brings me to this page, it has instruction to follow and "certificate".
The these instruction link lead to documentation on how to register the phone number, however the top of documentation clearly state that this instruction no longer valid as of now because it is using on premise API. So I tried to find the one valid for cloud API, I found this documentation → https://developers.facebook.com/docs/whatsapp/cloud-api/reference/registration/
The documentation offers a way to register the phone number through API, below is the snippets I copied from the documentation.
curl 'https://graph.facebook.com/v21.0/106540352242922/register ' \ -H 'Content-Type: application/json' \ -H 'Authorization: Bearer EAAJB...' \ -d ' { "messaging_product": "whatsapp", "pin": "212834" }
The question is how do I get phone number ID if my phone number is not "registered" to begin with ? I tried to retrieve the phone number ID by following the link here → https://developers.facebook.com/docs/whatsapp/business-management-api/manage-phone-numbers#get-all-phone-numbers, but it only list the test phone number, my phone number does not appear.
{ "data": [ { "verified_name": "Test Number", "code_verification_status": "NOT_VERIFIED", "display_phone_number": "+1 555-131-8955", "quality_rating": "GREEN", "platform_type": "CLOUD_API", "throughput": { "level": "STANDARD" }, "id": "375420581369195" } ], "paging": { "cursors": { "before": "xxxx", "after": "xxxx" } } }
Hi everyone,
I'm trying to generate an access token for the Instagram API, but I'm encountering some issues. Specifically, when I click on "Add account," no window opens for the Instagram login.
I then tried to run a test under the "App Roles" tab as a test user, and that worked fine. After that, I went back to the "Generate Access Token" section, accepted the test within the Instagram app, and tried to generate the token, but unfortunately, it didn't work either.
Has anyone experienced the same issue or know how to resolve it? Thanks a lot!
I have been trying to create collections to organize my catalog items, but it appears that the collections feature is not functioning as expected. other community posts facing same issue:
https://developers.facebook.com/community/threads/430022226558492/?join_id=f8625f32d5ceb3f7d
https://developers.facebook.com/community/threads/1104416270863922/?join_id=f94e298b680f25352
https://developers.facebook.com/community/threads/222137454323396/?join_id=f03fb76ef0ee81fb7
https://developers.facebook.com/community/threads/1202862247527971/?join_id=f1446a6c8cfc502b8
this issue seems to be abandoned and forgotten, despite being crucial.