Skip to content

Releases: rithik-dev/firebase_phone_auth_handler

v1.1.0

06 Oct 21:25
Compare
Choose a tag to compare
  • Updated README.md
  • Updated dependencies
  • Updated example app

v1.0.8

20 Jan 13:53
3532257
Compare
Choose a tag to compare
  • Added sendOtpOnInitialize parameter to the handler
  • Fixed OTP resend issue if the OTP expiration timer is still active
  • Fixed #15
  • Added shouldAwaitCodeSend to the sendOTP fn to give more control over the function
  • Updated dependencies

v1.0.7

24 Oct 12:18
Compare
Choose a tag to compare
  • Stacktrace in onLoginFailed is now non-nullable
  • Updated a dependency to the latest release
  • Updated example app

v1.0.6

16 Jul 14:36
Compare
Choose a tag to compare
  • BREAKING: Added stack trace to onLoginFailed and onError callbacks
  • Added a boolean linkWithExistingUser to link the new credentials with an existing signed-in user, instead of creating a new one.
  • Added onError callback for general purpose errors by the library
  • Updated example app
  • Updated dependencies

v1.0.5+1

13 Jul 13:07
Compare
Choose a tag to compare
  • Fixed files formatting
  • Updated example app

v1.0.5

10 Jul 21:09
Compare
Choose a tag to compare
  • BREAKING: Renamed flag timeOutDuration to autoRetrievalTimeOutDuration
  • BREAKING: Renamed verifyOTP to verifyOtp
  • BREAKING: Updated verifyOtp function signature to not take a named argument, and accept otp as a positional argument
  • Added a new otpExpirationDuration flag, as autoRetrievalTimeOutDuration is a completely different parameter.
  • Added callback onCodeSent and flag signOutOnSuccessfulVerification
  • Added isSendingCode flag to controller
  • Optimized code to reduce number of rebuilds
  • Updated example app
  • Updated dependencies
  • Refactored code

v1.0.4

07 Jun 11:28
Compare
Choose a tag to compare
  • Updated example app
  • Updated dependencies
  • Fixed linter warnings

v1.0.3

03 May 10:13
Compare
Choose a tag to compare
  • Updated example app
  • Updated README.md

v1.0.2

29 Apr 20:42
Compare
Choose a tag to compare
  • Renamed auth_service to auth_controller
  • Updated dependencies
  • Minor bug fixes
  • Updated example app
  • Updated README.md

v1.0.1

26 Jan 11:29
Compare
Choose a tag to compare

FirebasePhoneAuthHandler For Flutter

pub package
likes
popularity
pub points

  • An easy-to-use firebase phone authentication package to easily send and verify OTP's with auto-fetch OTP support via SMS.
  • Supports OTP on web out of the box.

Screenshots

      

Getting Started

Step 1: Before you can add Firebase to your app, you need to create a Firebase project to connect to your application.
Visit Understand Firebase Projects to learn more about Firebase projects.

Step 2: To use Firebase in your app, you need to register your app with your Firebase project.
Registering your app is often called "adding" your app to your project.

Also, register a web app if using on the web.
Follow on the screen instructions to initialize the project.

Add the latest version 'firebase-auth' CDN from here.
(Tested on version 8.6.1)

Step 3: Add a Firebase configuration file and the SDK's. (google-services)

Step 4: When the basic setup is done, open the console and then the
project and head over to Authentication from the left drawer menu.

Step 5: Click on Sign-in method next to the Users tab and enable Phone.

Step 6: Follow the additional configuration steps for the platforms to avoid any errors.

Step 7: IMPORTANT: Do not forget to enable the Android Device Verification
service from Google Cloud Platform. (make sure the correct project is selected).

Step 8: Lastly, add firebase_core as a dependency in your pubspec.yaml file.
and call Firebase.initializeApp() in the main method as shown:

void main() async {
  WidgetsFlutterBinding.ensureInitialized();
  await Firebase.initializeApp();
  runApp(_MainApp());
}

Usage

To use this plugin, add firebase_phone_auth_handler as a dependency in your pubspec.yaml file.

  dependencies:
    flutter:
      sdk: flutter
    firebase_phone_auth_handler:

First and foremost, import the widget.

import 'package:firebase_phone_auth_handler/firebase_phone_auth_handler.dart';

Wrap the MaterialApp with FirebasePhoneAuthProvider to enable your application to support phone authentication like shown.

class _MainApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return FirebasePhoneAuthProvider(
      child: MaterialApp(
        debugShowCheckedModeBanner: false,
        home: HomeScreen(),
      ),
    );
  }
}

You can now add a FirebasePhoneAuthHandler widget to your widget tree and pass all the required parameters to get started.

FirebasePhoneAuthHandler(
    phoneNumber: "+919876543210",
    builder: (context, controller) {
        return SizedBox.shrink();
    },
),

The phone number is the number to which the OTP will be sent which should be formatted in the following way:

+919876543210 - where +91 is the country code and 9876543210 is the phone number.

The widget returned from the builder is rendered on the screen.
The builder exposes a controller which contains various variables and methods.

Callbacks such as onLoginSuccess or onLoginFailed can be passed to the widget.

onLoginSuccess is called whenever the otp was sent to the mobile successfully and
was either auto verified or verified manually by calling verifyOTP function in the
controller. The callback exposes UserCredential object which can be used to find
user UID and other stuff. The boolean provided is whether the OTP was auto verified or
verified manually be calling verifyOTP. True if auto verified and false is verified manually.

onLoginFailed is called if an error occurs while sending OTP or verifying the OTP
or any internal error occurs, callback is triggered exposing FirebaseAuthException
which can be used to handle the error.

FirebasePhoneAuthHandler(
    phoneNumber: "+919876543210",
    builder: (context, controller) {
      return SizedBox.shrink();
    },
    onLoginSuccess: (userCredential, autoVerified) {
      debugPrint("autoVerified: $autoVerified");
      debugPrint("Login success UID: ${userCredential.user?.uid}");
    },
    onLoginFailed: (authException) {
      debugPrint("An error occurred: ${authException.message}");
    },
),

To logout the current user(if any), simply call

await FirebasePhoneAuthHandler.signOut(context);

controller.signOut() can also be used to logout the current user if the functionality is needed in
the same screen as the widget itself (where controller is the variable passed in the callback from the builder method in the widget).

Web (reCAPTCHA)

By default, the reCAPTCHA widget is a fully managed flow which provides security to your web application.
The widget will render as an invisible widget when the sign-in flow is triggered. An "invisible"
widget will appear as a full-page modal on-top of your application like demonstrated below.

reCAPTCHA1

Although, a RecaptchaVerifier instance can be passed which can be used to manage the widget.

Use the function recaptchaVerifierForWebProvider in FirebasePhoneAuthHandler which gives a boolean
to check whether the current platform is Web or not.

NOTE: Do not pass a RecaptchaVerifier instance if the platform is not web, else an error occurs.

Example:

recaptchaVerifierForWebProvider: (isWeb) {
    if (isWeb) return RecaptchaVerifier();
},

It is however possible to display an inline widget which the user has to explicitly press to verify themselves.

reCAPTCHA2

To add an inline widget, specify a DOM element ID to the container argument of the RecaptchaVerifier instance.
The element must exist and be empty otherwise an error will be thrown.
If no container argument is provided, the widget will be rendered as "invisible".

RecaptchaVerifier(
  container: 'recaptcha',
  size: RecaptchaVerifierSize.compact,
  theme: RecaptchaVerifierTheme.dark,
  onSuccess: () => print('reCAPTCHA Completed!'),
  onError: (FirebaseAuthException error) => print(error),
  onExpired: () => print('reCAPTCHA Expired!'),
),

If the reCAPTCHA badge does not disappear automatically after authentication is done,
try adding the following code in onLoginSuccess so that it disappears when the login process is done.

Firstly import querySelector from dart:html.

import 'dart:html' show querySelector;

Then add this in onLoginSuccess callback.

final captcha = querySelector('#__ff-recaptcha-container');
if (captcha != null) captcha.hidden = true;

If you want to completely disable the reCAPTCHA badge (typically appears on the bottom right),
add this CSS style in the web/index.html outside any other tag.

<style>
    .grecaptcha-badge { visibility: hidden; }
</style>

How I prefer using it usually

I usually have a phone number input field, which handles phone number input. Then pass the phone number
to the VerifyPhoneNumberScreen
widget from the example app.

// probably some ui or dialog to get the phone number
final phoneNumber = _getPhoneNumber();

// then call
void _verifyPhoneNumber() async {
  Navigator.push(
    context,
    MaterialPageRoute(
      builder: (_) => VerifyPhoneNumberScreen(phoneNumber: phoneNumber),
    ),
  );
}

/// route to home screen or somewhere in the onLoginSuccess callback for [VerifyPhoneNumberScreen] 

Sample Usage

import 'package:firebase_core/firebase_core.dart';
import 'package:firebase_phone_auth_handler/firebase_phone_auth_handler.dart';
import 'package:flutter/material.dart';

void main() async {
  WidgetsFlutterBinding.ensureInitialized();
  await Firebase.initializeApp();
  runApp(_MainApp());
}

class _MainApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return FirebasePhoneAuthProvider(
      child: MaterialApp(
        debugShowCheckedModeBanner: false,
        home: VerifyPhoneNumberScreen(phoneNumber: "+919876543210"),
      ),
    );
  }
}...
Read more