I applied user authentication with phone number in my flutter app using firebase, but the SMS with the one time password service is limited to 50 SMS/day, so I wanted to find a way to authenticate by phone number without firebase. its possible
I tried searching for ways to authenticate with phone number but all the results I found were using firebase
Related
I am working on an application that will sign up users based on their phone numbers. Everywhere I have read, there are articles regarding signing in users using their phone number. While researching for this I landed on a stackoverflow article itself that mentioned that the signInWithPhoneNumber() article will work for sign up when queried for first time, and will be used for sign in once the user is created as in this article What will happen if I sign in user using phone number without user creation in firebase?.
Going by this article, I wrote the following code to achieve my purpose
import auth from "#react-native-firebase/auth";
console.log("going to sign up with", numberToSend);
// numberToSned is the input number to which the message has to be sent
const confirmation = await auth().signInWithPhoneNumber(numberToSend);
I also set up a dummy number to test the feature.
But whenever this request is made my application shuts down by itself
Also I do not get any error on the console regarding this
So I wanted to ask is their a way to sign up users using their phone number in firebase with react-native?
As the link you describe (but didn't share) says: Firebase makes no distinction between signing up with a phone number or signing in with a phone number. The code for both cases is exactly the same, as shown in the documentation on Firebase phone authentication.
I'm trying to achieve phone number verification with the autofill feature in React native application. So far, I've discovered that there are 2 ways i.e either append hash key in sms body or use SMS User Consent API like https://developers.google.com/identity/sms-retriever/user-consent/overview
Is there any way/library through which we can avoid using the hash key?
Hi im working on a phone number based android app,
Im currently using google firebase.
Google firebase is pretty expensive when it comes to phone authentication,
I was thinking if there are any other ways to authenticate a phone number.
Programmable sms like twilio is fairly cheaper but still pretty expensive for my budget.
Is it possible to use voip to auth a phone number?
Are there any other alternatives?
Using twilio is right option for limited number of sms for your purpose, as for voip they all depend on SMS gateways, and to have gateway which may be cheaper but require massive sms, as they are more expensive.
Example of UseCase: I am a teacher, with this mobile device. I need to create and enable 40 students to use the app, from their userIDs which are authenticated using my mobile number, as they do not have their mobile device with them in class. They might go back home and sign in from their devices, but they might also sign in from the teacher's device. They don't want to use a password. They prefer an OTP. How can we do this?
Context:
We work with youth in the community, and need to enable many of them to sign in to an app using OTP, using the same mobile device. How can we maintain the integrity of the user's digital identity while making login easy?
The react-native app allows users to create UserIds using OTP or Facebook or Google OAuth. While we can only sign in one user per mobile device, we have the requirement to get multiple youth to sign in using one device. They need not stay signed on. OTP seems to need a single mobile number, and not multiple unique user Ids to be created with one mobile number
How can we design the backend and code such that this need can be met?
Does Google's SMS Retriever API get the list of phone numbers from the SIM lines on the user's device (which means that it's similar to TelephonyManager), or from the user's Google Play account?
I'm the product manager at Google for this API. Yes, as of the latest version of Play Services, the Phone Selector shows both the phone number for the device from the TelephonyManager (if it can be parsed as as a valid phone number) as well as recent phone numbers for the active Google Accounts on the device.
This is not directly addressed from the docs but if we infer from this statement in the Obtain the user's phone number:
Often, it is the best user experience to use the hint picker to prompt
the user to choose from the phone numbers stored on the device and
thereby avoid having to manually type a phone number
we can deduce that SMS Retriever API gets the contacts from your device.
Update
Please look at #Steven Soneff's answer
The numbers are retrieved from Smart Lock for Passwords on Android. They are retrieved if the user already stored it using Smart Lock else they will be empty. You may also ask the user to store the number for future use-cases using Smart Lock for Passwords.