How to register test number when using WhatsApp Business API - facebook

I'm trying to send test message on WhatsApp Business API
it took a day until I was shown a test number on "from" option
now I need to register the test phone but don't know how.
the register link take me to the configuration page,
but there is no option to register
Here is my WhatsApp account:

You can't add any testing phone numbers, Facebook App by default provides one, that you can see in From dropdown,
You can add only productions phone numbers, follow the below ways,
You can find the option in your Facebook App > Getting Started under WhatsApp menu,
Second, you can add from Your Business Setting,
Read more about how to register a phone number in WhatsApp Business,
https://developers.facebook.com/docs/whatsapp/phone-numbers

I also experienced this, it seems to be a bug in facebook itself or some lock in relation verified business, I did a test by creating a new business account and also a new application for this account , I activated whatsapp business and everything worked perfectly. But when I try to do the same procedure with an already verified account, the test number requests some kind of registration and also sends a notification that the test number was not approved. Unfortunately I haven't found any solution for this yet.
notification refused number

Related

Is it possible to develop multiple Whatsapp bots with one phonenumber?

Whatsapp just released their api (yeah FINALLY!)
You have to confirm a phonenumber. I was wondering if you could create multiple Whatsapp bots with one phonenumber. Or you would need to buy prepaid cards for each new bot to receive sms and confirm that number.
Each bot should have it's own number.
When a user sends a message, the correct bot needs to load which is not possible, as it cannot guess which one was intended.
A possible workaround is to combine all bots into a single one and create a redirection phase (first one obviously) with a "bot selection menu".
For example:
Hi, please choose the correct service:
shopping helper
calendar
timer
app downloader
Choosing an option will load the requested agent

Set up Firebase email verification without Apple Developer Account

I'm currently working on an IOS app and I'm using Firebase to deal with all the logging in and authentication.
I would like to set up email verification but every tutorial online says that my Dynamic Link needs to be registered in Xcode as an "Associated Domain". It doesn't seem I can do that without a developer account which I don't want to buy just yet
Is there any way that I can set up email verification without paying for a developer account?
Thank you,
Ethan
You can use Firebase Authentication's email verification without setting up an associated domain The only difference is that in that case you can't automatically re-open the app when the user clicks the link, as that requires the domain association. So the user will have to (re) open the app themselves, but aside from that email verification itself will work fine.

Facebook test users and auth

I have a project where I am using Selenium to test the Facebook auth. I created a Facebook app, created a test user inside this app and created some tests using Facebook login. Until now, it was working. But during the last two weeks something changed in Facebook and my tests are failing. It is due to interface changes in permissions dialog (I am targeting the button by his id). The second problem is that I don't get the email address from Facebook test user but a proxy email which is longer than 75 characters (my db field length is hardcoded in framework I am using).
If I log in as a regular user, it is working correctly and I get this permission box:
But when I log in as the test user I created (via 'switch to' in app's developer roles), I get this box:
I tested it ~2 weeks ago and this was yet working. Today it is changed. So my questions:
How to get back the old permissions box for test users?
How can I get the real email address and not the proxy?
Thanks!
I experienced the same problem with the Auth Dialog. I tried it with some old and new apps with various settings including March/Apr. 2013 Breaking Changes enabled/disabled, but it didn't help.
However, I guess I can help you with the email problem. When you login as a test user and go to account settings page, you will see the test user's primary email addres. By default this should be a really long one like the image I attached.
Facebook Platform returns this primary email address. If you pass the Auth Dialog with your test user account and see the privacy setting page, you will find the default primary email address is shared with the app. You have to provide a new email address for the test user and set the new one as primary email address via account setting page.
Why is the Login Dialog different with a test user?
With your test user, you can see the future of login dialogs. In fact, this isn't "not working" but this is an update which was unveiled on December 2012. Let me quote:
Our Login dialogs have undergone a redesign to make it easier to
understand permissions that apps request. We've simplified
presentation and have also updated our language for greater clarity.
“Basic info” has been renamed to “public profile and friend list,” to
reflect what what is being shared. Apps accessing your public profile
get your name, profile picture, age range, gender, language, country
and other public information.
Source: Providing People Greater Clarity and Control, developers.facebook.com/blog
The reason why you don't meet this update with a regular user, is that Facebook doesn't use to update everyone at the same time. They partially launch updates depending on the country, the type of account or some other parameters I ignore.
Example of a partial update (unified_message FQL table) dedicated to developer accounts:
We are providing early access to this API for registered developer
accounts only until the new messaging system is broadly available. You
should use the message table for production applications at the
current time.
In our case, we now know that test users can access to the update, but it is also said:
We have already launched many of these improvements as part of our
iOS6 integration and are now rolling them out more broadly.
About proxy emails
In fact, proxy emails are a way for any users to keep their real email anonymous. You have to consider proxy emails.
When joining an app, the user can choose between a real email and a proxy email:
Other thing you need to expect are users who didn't validate their account when connecting to your app, a case which is possible as described here and here.
Then, why do test users give back a proxy email? Because test users (being bots and having fake emails) didn't validate their emails.
You see that in at least 3 cases (and finally, test users are a good example), you need to handle these proxy emails. They are incidentally or accidentally met by developers and they can't be neglected. For your case, you can still try to disallow tests users who have a proxy email from accessing your app. But you should accept them and shouldn't force them to share their original e-mail addresses. A better solution is that you validate the test users emails:
Connect to the test user account that gives a proxy email
Add an email address (password needed here),
Go to the email mailbox and click on the validation link,
Set the new email address as primary,
The test user should now give his original email and not a proxy anymore!

Security options keeping us from testing applications

I work for a iPhone game developer. We use Facebook as a way for people to register their account to easily add friends and post news of their game progress.
We have created several Facebook accounts to test game account attachment and various friend features our game has.
Unfortunately, recently added security features are preventing us from logging into our test accounts. We are being asked to enter in a cellphone number to receive a SMS with a code to enter so we can verify they are real people. Unfortunately, after a phone number is used once, it cannot be used for any other account. So at the moment, we have two accounts that can be used, and about a dozen accounts that are inaccessible to us.
I haven't been able to find any solutions to this problem and we are really short on time at the moment so I need one ASAP.
They dont want you to create accounts like that, they want you to create accounts like this
This is odd, when I have test user accounts they never ask me to confirm the account. Maybe you should generate new test users for your app at: https://developers.facebook.com/apps/{yourAppId}/permissions. Then click on Add in the test user section.

Facebook Developer Account Verify

I created a new Facebook account and verified it with my cell phone. I even see "Your mobile phone has been successfully verified." in https://www.facebook.com/confirmphone.php address.
So, everything seems perfect.
Then, I became Facebook friends with my friend (he is also verified and already created an Application). We are trying to add ME as an ADMIN for this Facebook Application from HIS account.
Even though both are completely verified by phone, HE canNOT add me as ADMIN for that application. He is getting
Only verified developers can be added as listed developers of this application. Read http://www.facebook.com/help/?faq=17580 for details.
message all the time.
We waited more than an hour just in case the Facebook system did not recognize my new verification.
In fact, I even tried removing the phone number and get verified again.
None of above did work and still getting the message which does not allow me to become an Admin of the application.
Could you help me?
Thanks in advance
I've heard of people having all kinds of problems with the developer section of Facebook.com
One resolution seems to be to log out of both accounts and log back in again.
It turns out that, facebook itself does not accept my account and thinks it is duplicate account. And in order to make them believe the Facebook team want me to provide these below:
Our systems indicated that your account may not be authentic based on
a variety of factors. If you believe you are being prevented from
creating apps by mistake, please reply to this email with a digital
image of your government-issued identification. Make sure the
identification you provide meets all of the following requirements:
Must be government-issued (e.g. passport, driver's license)
Must be in color
Must clearly show your full name, date of birth, and photo
If possible, please save this file in JPEG image format.
I dont know why they are making such a huge problem.
In my case, I used phone number to login my account and hadn't any email attached. after adding email as a primary contact I was able to verify my developer account.