firebase_messaging 6.0.16

  • Readme
  • Changelog
  • Example
  • Installing
  • 100

Firebase Cloud Messaging for Flutter #

pub package

A Flutter plugin to use the Firebase Cloud Messaging (FCM) API.

With this plugin, your Flutter app can receive and process push notifications as well as data messages on Android and iOS. Read Firebase's About FCM Messages to learn more about the differences between notification messages and data messages.

For Flutter plugins for other Firebase products, see

Usage #

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

Getting Started #

Check out the example directory for a sample app using Firebase Cloud Messaging.

Android Integration #

To integrate your plugin into the Android part of your app, follow these steps:

  1. Using the Firebase Console add an Android app to your project: Follow the assistant, download the generated google-services.json file and place it inside android/app.

  2. Add the classpath to the [project]/android/build.gradle file.

dependencies {
  // Example existing classpath
  classpath ''
  // Add the google services classpath
  classpath ''
  1. Add the apply plugin to the [project]/android/app/build.gradle file.
apply plugin: ''

Note: If this section is not completed you will get an error like this:

Default FirebaseApp is not initialized in this process [package name].
Make sure to call FirebaseApp.initializeApp(Context) first.

Note: When you are debugging on Android, use a device or AVD with Google Play services. Otherwise you will not be able to authenticate.

  1. (optional, but recommended) If want to be notified in your app (via onResume and onLaunch, see below) when the user clicks on a notification in the system tray include the following intent-filter within the <activity> tag of your android/app/src/main/AndroidManifest.xml:
      <action android:name="FLUTTER_NOTIFICATION_CLICK" />
      <category android:name="android.intent.category.DEFAULT" />

Optionally handle background messages

Background message handling is intended to be performed quickly. Do not perform long running tasks as they may not be allowed to finish by the Android system. See Background Execution Limits for more.

By default background messaging is not enabled. To handle messages in the background:

  1. Add the dependency in your app-level build.gradle file that is typically located at <app-name>/android/app/build.gradle.

    dependencies {
      // ...
      implementation '<latest_version>'

    Note: you can find out what the latest version of the plugin is here ("Cloud Messaging").

  2. Add an class to your app in the same directory as your This is typically found in <app-name>/android/app/src/main/java/<app-organization-path>/.

    package io.flutter.plugins.firebasemessagingexample;
    import io.flutter.plugin.common.PluginRegistry;
    import io.flutter.plugin.common.PluginRegistry.PluginRegistrantCallback;
    import io.flutter.plugins.GeneratedPluginRegistrant;
    import io.flutter.plugins.firebasemessaging.FlutterFirebaseMessagingService;
    public class Application extends FlutterApplication implements PluginRegistrantCallback {
      public void onCreate() {
      public void registerWith(PluginRegistry registry) {
  3. In, make sure to change package io.flutter.plugins.firebasemessagingexample; to your package's identifier. Your package's identifier should be something like com.domain.myapplication.

    package com.domain.myapplication;
  4. Set name property of application in AndroidManifest.xml. This is typically found in <app-name>/android/app/src/main/.

    <application android:name=".Application" ...>
  5. Define a TOP-LEVEL or STATIC function to handle background messages

    Future<dynamic> myBackgroundMessageHandler(Map<String, dynamic> message) {
      if (message.containsKey('data')) {
        // Handle data message
        final dynamic data = message['data'];
      if (message.containsKey('notification')) {
        // Handle notification message
        final dynamic notification = message['notification'];
      // Or do other work.

    Note: the protocol of data and notification are in line with the fields defined by a RemoteMessage.

  6. Set onBackgroundMessage handler when calling configure

          onMessage: (Map<String, dynamic> message) async {
            print("onMessage: $message");
          onBackgroundMessage: myBackgroundMessageHandler,
          onLaunch: (Map<String, dynamic> message) async {
            print("onLaunch: $message");
          onResume: (Map<String, dynamic> message) async {
            print("onResume: $message");

    Note: configure should be called early in the lifecycle of your application so that it can be ready to receive messages as early as possible. See the example app for a demonstration.

iOS Integration #

To integrate your plugin into the iOS part of your app, follow these steps:

  1. Generate the certificates required by Apple for receiving push notifications following this guide in the Firebase docs. You can skip the section titled "Create the Provisioning Profile".

  2. Using the Firebase Console add an iOS app to your project: Follow the assistant, download the generated GoogleService-Info.plist file, open ios/Runner.xcworkspace with Xcode, and within Xcode place the file inside ios/Runner. Don't follow the steps named "Add Firebase SDK" and "Add initialization code" in the Firebase assistant.

  3. In Xcode, select Runner in the Project Navigator. In the Capabilities Tab turn on Push Notifications and Background Modes, and enable Background fetch and Remote notifications under Background Modes.

  4. Follow the steps in the "Upload your APNs certificate" section of the Firebase docs.

  5. If you need to disable the method swizzling done by the FCM iOS SDK (e.g. so that you can use this plugin with other notification plugins) then add the following to your application's Info.plist file.


After that, add the following lines to the (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions method in the AppDelegate.m/AppDelegate.swift of your iOS project.


if (@available(iOS 10.0, *)) {
  [UNUserNotificationCenter currentNotificationCenter].delegate = (id<UNUserNotificationCenterDelegate>) self;


if #available(iOS 10.0, *) {
  UNUserNotificationCenter.current().delegate = self as? UNUserNotificationCenterDelegate

Dart/Flutter Integration #

From your Dart code, you need to import the plugin and instantiate it:

import 'package:firebase_messaging/firebase_messaging.dart';

final FirebaseMessaging _firebaseMessaging = FirebaseMessaging();

Next, you should probably request permissions for receiving Push Notifications. For this, call _firebaseMessaging.requestNotificationPermissions(). This will bring up a permissions dialog for the user to confirm on iOS. It's a no-op on Android. Last, but not least, register onMessage, onResume, and onLaunch callbacks via _firebaseMessaging.configure() to listen for incoming messages (see table below for more information).

Receiving Messages #

Messages are sent to your Flutter app via the onMessage, onLaunch, and onResume callbacks that you configured with the plugin during setup. Here is how different message types are delivered on the supported platforms:

App in ForegroundApp in BackgroundApp Terminated
Notification on AndroidonMessageNotification is delivered to system tray. When the user clicks on it to open app onResume fires if click_action: FLUTTER_NOTIFICATION_CLICK is set (see below).Notification is delivered to system tray. When the user clicks on it to open app onLaunch fires if click_action: FLUTTER_NOTIFICATION_CLICK is set (see below).
Notification on iOSonMessageNotification is delivered to system tray. When the user clicks on it to open app onResume fires.Notification is delivered to system tray. When the user clicks on it to open app onLaunch fires.
Data Message on AndroidonMessageonMessage while app stays in the background.not supported by plugin, message is lost
Data Message on iOSonMessageMessage is stored by FCM and delivered to app via onMessage when the app is brought back to foreground.Message is stored by FCM and delivered to app via onMessage when the app is brought back to foreground.

Additional reading: Firebase's About FCM Messages.

Notification messages with additional data #

It is possible to include additional data in notification messages by adding them to the "data"-field of the message.

On Android, the message contains an additional field data containing the data. On iOS, the data is directly appended to the message and the additional data-field is omitted.

To receive the data on both platforms:

Future<void> _handleNotification (Map<dynamic, dynamic> message, bool dialog) async {
    var data = message['data'] ?? message;
    String expectedAttribute = data['expectedAttribute'];
    /// [...]

Sending Messages #

Refer to the Firebase documentation about FCM for all the details about sending messages to your app. When sending a notification message to an Android device, you need to make sure to set the click_action property of the message to FLUTTER_NOTIFICATION_CLICK. Otherwise the plugin will be unable to deliver the notification to your app when the users clicks on it in the system tray.

For testing purposes, the simplest way to send a notification is via the Firebase Console. Make sure to include click_action: FLUTTER_NOTIFICATION_CLICK as a "Custom data" key-value-pair (under "Advanced options") when targeting an Android device. The Firebase Console does not support sending data messages.

Alternatively, a notification or data message can be sent from a terminal:

DATA='{"notification": {"body": "this is a body","title": "this is a title"}, "priority": "high", "data": {"click_action": "FLUTTER_NOTIFICATION_CLICK", "id": "1", "status": "done"}, "to": "<FCM TOKEN>"}'
curl -H "Content-Type:application/json" -X POST -d "$DATA" -H "Authorization: key=<FCM SERVER KEY>"

Remove the notification property in DATA to send a data message.

You could also test this from within Flutter using the http package:

// Replace with server token from firebase console settings.
final String serverToken = '<Server-Token>';
final FirebaseMessaging firebaseMessaging = FirebaseMessaging();

Future<Map<String, dynamic>> sendAndRetrieveMessage() async {
  await firebaseMessaging.requestNotificationPermissions(
    const IosNotificationSettings(sound: true, badge: true, alert: true, provisional: false),

     headers: <String, String>{
       'Content-Type': 'application/json',
       'Authorization': 'key=$serverToken',
     body: jsonEncode(
     <String, dynamic>{
       'notification': <String, dynamic>{
         'body': 'this is a body',
         'title': 'this is a title'
       'priority': 'high',
       'data': <String, dynamic>{
         'click_action': 'FLUTTER_NOTIFICATION_CLICK',
         'id': '1',
         'status': 'done'
       'to': await firebaseMessaging.getToken(),

  final Completer<Map<String, dynamic>> completer =
     Completer<Map<String, dynamic>>();

    onMessage: (Map<String, dynamic> message) async {

  return completer.future;

Issues and feedback #

Please file Flutterfire specific issues, bugs, or feature requests in our issue tracker.

Plugin issues that are not specific to Flutterfire can be filed in the Flutter issue tracker.

To contribute a change to this plugin, please review our contribution guide, and send a pull request.

6.0.16 #

  • Update lower bound of dart dependency to 2.0.0.

6.0.15 #

  • Fix - register pluginRegistrantCallback on every FcmDartService#start call.

6.0.14 #

  • Fix for missing UserAgent.h compilation failures.

6.0.13 #

  • Implement UNUserNotificationCenterDelegate methods to allow plugin to work when method swizzling is disabled.
  • Applications now only need to update their iOS project's AppDelegate when method swizzling is disabled.
  • Applications that need to use firebase_messaging with other notification plugins will need to add the following to their iOS project's Info.plist file:

6.0.12 #

  • Replace deprecated getFlutterEngine call on Android.

6.0.11 #

  • Make the pedantic dev_dependency explicit.

6.0.10 #

  • Update README to explain how to correctly implement Android background message handling with the new v2 embedding.

6.0.9 #

  • Update Android Gradle plugin dependency to 3.5.3, update documentation and example.
  • Update google-services Android gradle plugin to 4.3.2 in documentation and examples.

6.0.8 #

  • Support for provisional notifications for iOS version >= 12.

6.0.7 #

  • Remove the deprecated author: field from pubspec.yaml
  • Migrate the plugin to the pubspec platforms manifest.
  • Bump the minimum Flutter version to 1.10.0.

6.0.6 #

  • Updated README instructions for Android.

6.0.5 #

  • Add import for UserNotifications on iOS.

6.0.4 #

  • Support the v2 Android embedding.

6.0.3 #

  • Fix bug where onIosSettingsRegistered wasn't streamed on iOS >= 10.

6.0.2 #

  • Fixed a build warning caused by availability check.

6.0.1 #

  • FirebaseMessaging.configure will throw an ArgumentError when onBackgroundMessage parameter is not a top-level or static function.

6.0.0 #

  • Use UNUserNotificationCenter to receive messages on iOS version >= 10.

  • Breaking Change For iOS versions >= 10, this will cause any other plugin that specifies a UNUserNotificationCenterDelegate to [UNUserNotificationCenter currentNotificationCenter] to stop receiving notifications. To have this plugin work with plugins that specify their own UNUserNotificationCenterDelegate, you can remove the line

    [UNUserNotificationCenter currentNotificationCenter].delegate = // plugin specified delegate

    and add this line to your iOS project AppDelegate.m

    if (@available(iOS 10.0, *)) {
      [UNUserNotificationCenter currentNotificationCenter].delegate = (id<UNUserNotificationCenterDelegate>) self;

5.1.9 #

  • Fix strict compilation errors.

5.1.8 #

  • Updated README instructions for contributing for consistency with other Flutterfire plugins.

5.1.7 #

  • Remove AndroidX warning.

5.1.6 #

  • Fix warnings when compiling on Android.

5.1.5 #

  • Enable background message handling on Android.

5.1.4 #

  • Update documentation to reflect new repository location.
  • Update unit tests to call TestWidgetsFlutterBinding.ensureInitialized.

5.1.3 #

  • Update google-services Android gradle plugin to 4.3.0 in documentation and examples.

5.1.2 #

  • Updates to README and example with explanations of differences in data format.

5.1.1 #

  • Update README with more detailed integration instructions.

5.1.0 #

  • Changed the return type of subscribeToTopic and unsubscribeFromTopic to Future<void>.

5.0.6 #

  • Additional integration tests.

5.0.5 #

  • On Android, fix crash when calling deleteInstanceID with latest Flutter engine.

5.0.4 #

  • Automatically use version from pubspec.yaml when reporting usage to Firebase.

5.0.3 #

  • Update Dart code to conform to current Dart formatter.

5.0.2 #

  • Add missing template type parameter to invokeMethod calls.
  • Bump minimum Flutter version to 1.5.0.
  • Replace invokeMethod with invokeMapMethod wherever necessary.

5.0.1+1 #

  • Enable support for onMessage on iOS using shouldEstablishDirectChannel.

5.0.1 #

  • Fix error in the logs on startup if unable to retrieve token on startup on Android.

5.0.0 #

  • Update Android dependencies to latest.

4.0.0+4 #

  • Remove obsolete use_frameworks! instruction.

4.0.0+3 #

  • Update iOS configuration documentation.

4.0.0+2 #

  • Fix example app's floating action button that stopped working due to a breaking change.

4.0.0+1 #

  • Log messages about automatic configuration of the default app are now less confusing.

4.0.0 #

  • Breaking Change Update message structure for onMessage to match onLaunch and onResume

3.0.1 #

  • Log a more detailed warning at build time about the previous AndroidX migration.

3.0.0 #

  • Breaking change. Migrate from the deprecated original Android Support Library to AndroidX. This shouldn't result in any functional changes, but it requires any Android apps using this plugin to also migrate if they're using the original support library.

    This was originally incorrectly pushed in the 2.2.0 update.

2.2.0+1 #

  • Revert the breaking 2.2.0 update. 2.2.0 was known to be breaking and should have incremented the major version number instead of the minor. This revert is in and of itself breaking for anyone that has already migrated however. Anyone who has already migrated their app to AndroidX should immediately update to 3.0.0 instead. That's the correctly versioned new push of 2.2.0.

2.2.0 #

  • BAD. This was a breaking change that was incorrectly published on a minor version upgrade, should never have happened. Reverted by 2.2.0+1.

  • Breaking change. Migrate from the deprecated original Android Support Library to AndroidX. This shouldn't result in any functional changes, but it requires any Android apps using this plugin to also migrate if they're using the original support library.

2.1.0 #

  • Adding support for deleteInstanceID(), autoInitEnabled() and setAutoInitEnabled().

2.0.3 #

  • Removing local cache of getToken() in the dart part of the plugin. Now getToken() calls directly its counterparts in the iOS and Android implementations. This enables obtaining its value without calling configure() or having to wait for a new token refresh.

2.0.2 #

  • Use boolean values when checking for notification types on iOS.

2.0.1 #

  • Bump Android dependencies to latest.

2.0.0 #

  • Updated Android to send Remote Message's title and body to Dart.

1.0.5 #

  • Bumped test and mockito versions to pick up Dart 2 support.

1.0.4 #

  • Bump Android and Firebase dependency versions.

1.0.3 #

  • Updated iOS token hook from 'didRefreshRegistrationToken' to 'didReceiveRegistrationToken'

1.0.2 #

  • Updated Gradle tooling to match Android Studio 3.2.2.

1.0.1 #

  • Fix for Android where the onLaunch event is not triggered when the Activity is killed by the OS (or if the Don't keep activities toggle is enabled)

1.0.0 #

  • Bump to released version

0.2.5 #

  • Fixed Dart 2 type error.

0.2.4 #

  • Updated Google Play Services dependencies to version 15.0.0.

0.2.3 #

  • Updated package channel name

0.2.2 #

  • Simplified podspec for Cocoapods 1.5.0, avoiding link issues in app archives.

0.2.1 #

  • Fixed Dart 2 type errors.

0.2.0 #

  • Breaking change. Set SDK constraints to match the Flutter beta release.

0.1.4 #

  • Fixed Dart 2 type error in example project.

0.1.3 #

  • Enabled use in Swift projects.

0.2.2 #

  • Fix for APNS not being correctly registered on iOS when reinstalling application.

0.1.1 #

  • Simplified and upgraded Android project template to Android SDK 27.
  • Updated package description.

0.1.0 #

  • Breaking change. Upgraded to Gradle 4.1 and Android Studio Gradle plugin 3.0.1. Older Flutter projects need to upgrade their Gradle setup as well in order to use this version of the plugin. Instructions can be found here.
  • Relaxed GMS dependency to [11.4.0,12.0[

0.0.8 #

  • Added FLT prefix to iOS types
  • Change GMS dependency to 11.4.+

0.0.7 #

In FirebaseMessagingPlugin.m:

  • moved logic from 'tokenRefreshNotification' to 'didRefreshRegistrationToken'
  • removed 'tokenRefreshNotification' as well as observer registration
  • removed 'connectToFcm' method and related calls
  • removed unnecessary FIRMessaging disconnect

0.0.6 #

  • Change GMS dependency to 11.+

0.0.5+2 #

  • Fixed README example for "click_action"

0.0.5+1 #

  • Aligned author name with rest of repo.

0.0.5 #

  • Updated to Firebase SDK to always use latest patch version for 11.0.x builds

0.0.4 #

  • Updated to Firebase SDK Version 11.0.1

0.0.3 #

  • Updated
  • Bumped buildToolsVersion to 25.0.3

0.0.2+2 #

  • Updated

0.0.2+1 #

0.0.2 #

  • Updated to latest plugin API #

  • Downgraded gradle dependency for example app to make flutter run happy

0.0.1+1 #

  • Updated README with installation instructions

0.0.1 #

  • Initial Release


// Copyright 2019 The Chromium Authors. All rights reserved.
// Use of this source code is governed by a BSD-style license that can be
// found in the LICENSE file.

import 'dart:async';

import 'package:firebase_messaging/firebase_messaging.dart';
import 'package:flutter/material.dart';

final Map<String, Item> _items = <String, Item>{};
Item _itemForMessage(Map<String, dynamic> message) {
  final dynamic data = message['data'] ?? message;
  final String itemId = data['id'];
  final Item item = _items.putIfAbsent(itemId, () => Item(itemId: itemId))
    ..status = data['status'];
  return item;

class Item {
  final String itemId;

  StreamController<Item> _controller = StreamController<Item>.broadcast();
  Stream<Item> get onChanged =>;

  String _status;
  String get status => _status;
  set status(String value) {
    _status = value;

  static final Map<String, Route<void>> routes = <String, Route<void>>{};
  Route<void> get route {
    final String routeName = '/detail/$itemId';
    return routes.putIfAbsent(
      () => MaterialPageRoute<void>(
        settings: RouteSettings(name: routeName),
        builder: (BuildContext context) => DetailPage(itemId),

class DetailPage extends StatefulWidget {
  final String itemId;
  _DetailPageState createState() => _DetailPageState();

class _DetailPageState extends State<DetailPage> {
  Item _item;
  StreamSubscription<Item> _subscription;

  void initState() {
    _item = _items[widget.itemId];
    _subscription = _item.onChanged.listen((Item item) {
      if (!mounted) {
      } else {
        setState(() {
          _item = item;

  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text("Item ${_item.itemId}"),
      body: Material(
        child: Center(child: Text("Item status: ${_item.status}")),

class PushMessagingExample extends StatefulWidget {
  _PushMessagingExampleState createState() => _PushMessagingExampleState();

class _PushMessagingExampleState extends State<PushMessagingExample> {
  String _homeScreenText = "Waiting for token...";
  bool _topicButtonsDisabled = false;

  final FirebaseMessaging _firebaseMessaging = FirebaseMessaging();
  final TextEditingController _topicController =
      TextEditingController(text: 'topic');

  Widget _buildDialog(BuildContext context, Item item) {
    return AlertDialog(
      content: Text("Item ${item.itemId} has been updated"),
      actions: <Widget>[
          child: const Text('CLOSE'),
          onPressed: () {
            Navigator.pop(context, false);
          child: const Text('SHOW'),
          onPressed: () {
            Navigator.pop(context, true);

  void _showItemDialog(Map<String, dynamic> message) {
      context: context,
      builder: (_) => _buildDialog(context, _itemForMessage(message)),
    ).then((bool shouldNavigate) {
      if (shouldNavigate == true) {

  void _navigateToItemDetail(Map<String, dynamic> message) {
    final Item item = _itemForMessage(message);
    // Clear away dialogs
    Navigator.popUntil(context, (Route<dynamic> route) => route is PageRoute);
    if (!item.route.isCurrent) {
      Navigator.push(context, item.route);

  void initState() {
      onMessage: (Map<String, dynamic> message) async {
        print("onMessage: $message");
      onLaunch: (Map<String, dynamic> message) async {
        print("onLaunch: $message");
      onResume: (Map<String, dynamic> message) async {
        print("onResume: $message");
        const IosNotificationSettings(
            sound: true, badge: true, alert: true, provisional: true));
        .listen((IosNotificationSettings settings) {
      print("Settings registered: $settings");
    _firebaseMessaging.getToken().then((String token) {
      assert(token != null);
      setState(() {
        _homeScreenText = "Push Messaging token: $token";

  Widget build(BuildContext context) {
    return Scaffold(
        appBar: AppBar(
          title: const Text('Push Messaging Demo'),
        // For testing -- simulate a message being received
        floatingActionButton: FloatingActionButton(
          onPressed: () => _showItemDialog(<String, dynamic>{
            "data": <String, String>{
              "id": "2",
              "status": "out of stock",
          tooltip: 'Simulate Message',
          child: const Icon(Icons.message),
        body: Material(
          child: Column(
            children: <Widget>[
                child: Text(_homeScreenText),
              Row(children: <Widget>[
                  child: TextField(
                      controller: _topicController,
                      onChanged: (String v) {
                        setState(() {
                          _topicButtonsDisabled = v.isEmpty;
                  child: const Text("subscribe"),
                  onPressed: _topicButtonsDisabled
                      ? null
                      : () {
                  child: const Text("unsubscribe"),
                  onPressed: _topicButtonsDisabled
                      ? null
                      : () {

  void _clearTopicText() {
    setState(() {
      _topicController.text = "";
      _topicButtonsDisabled = true;

void main() {
      home: PushMessagingExample(),

Use this package as a library

1. Depend on it

Add this to your package's pubspec.yaml file:

  firebase_messaging: ^6.0.16

2. Install it

You can install packages from the command line:

with Flutter:

$ flutter pub get

Alternatively, your editor might support flutter pub get. Check the docs for your editor to learn more.

3. Import it

Now in your Dart code, you can use:

import 'package:firebase_messaging/firebase_messaging.dart';
Describes how popular the package is relative to other packages. [more]
Code health derived from static analysis. [more]
Reflects how tidy and up-to-date the package is. [more]
Weighted score of the above. [more]
Learn more about scoring.

We analyzed this package on Jul 2, 2020, and provided a score, details, and suggestions below. Analysis was completed with status completed using:

  • Dart: 2.8.4
  • pana: 0.13.13
  • Flutter: 1.17.5

Analysis suggestions

Package does not support Flutter platform linux

Because of import path [package:firebase_messaging/firebase_messaging.dart] that declares support for platforms: android, ios

Package does not support Flutter platform macos

Because of import path [package:firebase_messaging/firebase_messaging.dart] that declares support for platforms: android, ios

Package does not support Flutter platform web

Because of import path [package:firebase_messaging/firebase_messaging.dart] that declares support for platforms: android, ios

Package does not support Flutter platform windows

Because of import path [package:firebase_messaging/firebase_messaging.dart] that declares support for platforms: android, ios

Package not compatible with SDK dart

because of import path [firebase_messaging] that is in a package requiring null.


Package Constraint Resolved Available
Direct dependencies
Dart SDK >=2.0.0 <3.0.0
flutter 0.0.0
meta ^1.0.4 1.1.8
platform ^2.0.0 2.2.1
Transitive dependencies
collection 1.14.12 1.14.13
sky_engine 0.0.99
typed_data 1.1.6 1.2.0
vector_math 2.0.8
Dev dependencies
e2e ^0.2.1
firebase_core ^0.4.0
mockito ^3.0.0
pedantic ^1.8.0
test ^1.3.0