Hello,
I recently came across the update about Embedded Signup for onboarding WhatsApp Business app users. This is an excellent feature that can greatly simplify the process! However, one of the current requirements is to be a Solution Partner or Tech Provider.
Many businesses do not have access to a Solution Partner, which limits their ability to take advantage of this functionality. It would be incredibly valuable if WhatsApp Business accounts could be linked to any application, rather than being restricted to approved partners or tech providers. Expanding access would make this feature more inclusive and beneficial to a broader range of businesses.
I appreciate your time and consideration. Looking forward to your thoughts!
Best regards, Yehuda

Our service currently processes authentication through "https://www.instagram.com/oauth/authorize", and we have noticed a difference when logging in with two different business accounts.
After logging in with the first account, the page appears like CaseA in caseAB.png .
After logging in with the second account, the page appears like CaseB in caseAB.png .
If you check the URL after logging in with the first account, it redirects from /oauth/authorize to https://www.instagram.com/consent/?flow=ig_biz_login_oauth.
However, when logging in with the second account, the URL remains /oauth/authorize as expected.
Could you please confirm what differences between these two accounts might be causing this behavior?

To add the Facebook login feature to a live site, the app review must be completed. However, deploying the feature before the review is finished may cause issues, as it would mean applying an unapproved feature to the production environment.
Is there a way to undergo the review process in this situation?

What should I answer here? I don't understand please help. thank you

Hi Facebook Dev Community,
Users get API Error 100 when sharing pages from my food menu site https://menupriceinuk.co.uk/.
Tried: ✅ Verified Open Graph tags. ✅ Encoded URL parameters. ✅ Tested Graph API + sharer.php.
Issue: Dynamic paths (e.g., /menu/burger-specials) trigger the error, but static pages work.
Ask:
Are special characters in menu URLs causing this?
Any fixes for React/Node.js sites with frequent price updates?
Thanks for any quick tips!