cordova-plugin-firebasex  

Brings push notifications, analytics, event tracking, crash reporting and more from Google Firebase to your Cordova project.

Supported platforms: Android and iOS

IMPORTANT: Before opening an issue against this plugin, please read Reporting issues.


I dedicate a considerable amount of my free time to developing and maintaining this Cordova plugin, along with my other Open Source software.
To help ensure this plugin is kept updated, new features are added and bugfixes are implemented quickly, please donate a couple of dollars (or a little more if you can stretch) as this will help me to afford to dedicate time to its maintenance. Please consider donating if you're using this plugin in an app that makes you money, if you're being paid to make the app, if you're asking for new features or priority bug fixes.

MAINTENANCE OF THIS PLUGIN: Please note this plugin is maintained only by me - one person - in my spare time: I do not get paid for it. Therefore I will do my best to address bugs and issues as time permits but if you have an urgent requirement for a bug fix or missing feature, then I am available for paid contract work in order to expedite this - contact me for details. Otherwise I will get around to it when I have time.

- Installation
- Plugin variables
- Android & iOS
- Android only
- iOS only
- Post-install plugin variables
- Supported Cordova Versions
- Supported Mobile Platform Versions
- Migrating from cordova-plugin-firebase
- Breaking API changes
- Ionic 4+
- Ionic 3
- Build environment notes
- Remote Cloud Build
- Capacitor support
- Android-specific
- Specifying Android library versions
- AndroidX
- Google Play Services and Firebase libraries
- iOS-specific
- Specifying iOS library versions
- Cocoapods
- Out-of-date pods
- Strip debug symbols
- Cordova CLI builds
- Firebase config setup
- Disable data collection on startup
- Example project
- Reporting issues
- Reporting a bug or problem
- Requesting a new feature
- Cloud messaging
- Background notifications
- Foreground notifications
- Android notifications
- Android background notifications
- Android foreground notifications
- Android Notification Channels
- Android Notification Icons
- Android Notification Color
- Android Notification Sound
- Android cloud message types
- iOS notifications
- iOS background notifications
- iOS notification sound
- iOS critical notifications
- iOS badge number
- iOS actionable notifications
- iOS notification settings button
- Data messages
- Data message notifications
- Custom FCM message handling
- Android
- iOS
- Example
- InApp Messaging
- Google Tag Manager
- Android
- iOS
- Performance Monitoring
- Android Performance Monitoring Gradle plugin
- API
- Notifications and data messages
- getToken
- getId
- onTokenRefresh
- getAPNSToken
- onApnsTokenReceived
- onOpenSettings
- onMessageReceived
- grantPermission
- grantCriticalPermission
- hasPermission
- hasCriticalPermission
- unregister
- isAutoInitEnabled
- setAutoInitEnabled
- setBadgeNumber
- getBadgeNumber
- clearAllNotifications
- subscribe
- unsubscribe
- createChannel
- setDefaultChannel
- Default Android Channel Properties
- deleteChannel
- listChannels
- Analytics
- setAnalyticsCollectionEnabled
- isAnalyticsCollectionEnabled
- AnalyticsConsentMode
- AnalyticsConsentStatus
- setAnalyticsConsentMode
- logEvent
- setScreenName
- setUserId
- setUserProperty
- initiateOnDeviceConversionMeasurement
- Crashlytics
- setCrashlyticsCollectionEnabled
- didCrashOnPreviousExecution
- isCrashlyticsCollectionEnabled
- setCrashlyticsUserId
- sendCrash
- setCrashlyticsCustomKey
- logMessage
- logError
- Authentication
- isUserSignedIn
- signOutUser
- getCurrentUser
- reloadCurrentUser
- updateUserProfile
- updateUserEmail
- sendUserEmailVerification
- verifyBeforeUpdateEmail
- updateUserPassword
- sendUserPasswordResetEmail
- deleteUser
- createUserWithEmailAndPassword
- signInUserWithEmailAndPassword
- signInUserWithCustomToken
- signInUserAnonymously
- verifyPhoneNumber
- enrollSecondAuthFactor
- verifySecondAuthFactor
- listEnrolledSecondAuthFactors
- unenrollSecondAuthFactor
- setLanguageCode
- authenticateUserWithEmailAndPassword
- authenticateUserWithGoogle
- authenticateUserWithApple
- authenticateUserWithMicrosoft
- authenticateUserWithFacebook
- authenticateUserWithOAuth
- signInWithCredential
- linkUserWithCredential
- reauthenticateWithCredential
- unlinkUserWithProvider
- registerAuthStateChangeListener
- registerAuthIdTokenChangeListener
- useAuthEmulator
- getClaims
- Remote Config
- fetch
- activateFetched
- fetchAndActivate
- resetRemoteConfig
- getValue
- getInfo
- getAll
- setConfigSettings
- setDefaults
- Performance
- setPerformanceCollectionEnabled
- isPerformanceCollectionEnabled
- startTrace
- incrementCounter
- stopTrace
- Firestore
- addDocumentToFirestoreCollection
- setDocumentInFirestoreCollection
- updateDocumentInFirestoreCollection
- deleteDocumentFromFirestoreCollection
- documentExistsInFirestoreCollection
- fetchDocumentInFirestoreCollection
- fetchFirestoreCollection
- listenToDocumentInFirestoreCollection
- listenToFirestoreCollection
- removeFirestoreListener
- Functions
- functionsHttpsCallable
- Installations
- getInstallationId
- getInstallationToken
- getInstallationId
- registerInstallationIdChangeListener
- Miscellaneous
- registerApplicationDidBecomeActiveListener
- registerApplicationDidEnterBackgroundListener
- Debug mode
- Credits

Installation

Install the plugin by adding it to your project's config.xml:

``xml

`

or by running:

`
cordova plugin add cordova-plugin-firebasex
`

Plugin variables

The following Cordova plugin variables are supported by the plugin.
Note that these must be set at plugin installation time. If you wish to change plugin variables, you'll need to uninstall the plugin and reinstall it with the new variable values.

Plugin variables are initially set by specifying them during plugin installation, for example:
cordova plugin add cordova-plugin-firebasex --variable FIREBASE_ANALYTICS_WITHOUT_ADS=true

Once the plugin is installed, you can change the plugin variable values either by fully uninstalling/reinstalling the plugin, for example:
cordova plugin rm cordova-plugin-firebasex && cordova plugin add cordova-plugin-firebasex --variable FIREBASE_ANALYTICS_WITHOUT_ADS=false

Or you can manually edit the values in your project's package.json under cordova.plugins.cordova-plugin-firebasex and reinstall the plugin:
cordova plugin rm cordova-plugin-firebasex --nosave && cordova plugin add cordova-plugin-firebasex --nosave

$3

- FIREBASE_ANALYTICS_COLLECTION_ENABLED - whether to automatically enable Firebase Analytics data collection on app startup. Defaults to true.
- FIREBASE_PERFORMANCE_COLLECTION_ENABLED - whether to automatically enable Firebase Performance data collection on app startup. Defaults to true.
- FIREBASE_CRASHLYTICS_COLLECTION_ENABLED - whether to automatically enable Firebase Crashlytics data collection on app startup. Defaults to true.
- FIREBASE_FCM_AUTOINIT_ENABLED - whether to automatically enable FCM registration on app startup. Defaults to true.
- FIREBASE_ANALYTICS_WITHOUT_ADS - whether to disable advertising ID collection in Analytics. Defaults to false.
- Note that this is a post-install plugin variable so an additional step is required to activate the plugin variable the first time it is specified.
See Disable data collection on startup for more info.
- FIREBASE_MESSAGING_IMMEDIATE_PAYLOAD_DELIVERY - whether to deliver FCM messages immediately when the app is in the background. Defaults to false.
- If false, messages that arrive while the app is in the background/inactive are queued and delivered when the app is next brought to the foreground.
- If true, messages are delivered immediately when received, even if the app is in the background/inactive.
- Note: on modern iOS and Android devices, there is no guarantee that the message will be successfully delivered to the app because the OS may have paused the app's Cordova Webview process or the Webview may not exist at the time the message is received.
- GOOGLE_ANALYTICS_ADID_COLLECTION_ENABLED - determines whether Google Analytics collects Advertising IDs (ADIDs) for ad targeting and attribution purposes. If set to true, Google Analytics will collect ADIDs; if set to false, it will not collect ADIDs. Defaults to true.
- GOOGLE_ANALYTICS_DEFAULT_ALLOW_ANALYTICS_STORAGE - specifies the default setting for allowing Google Analytics to store analytics data. If set to true, Google Analytics is allowed to store analytics data; if set to false, it is not allowed to store analytics data by default.
- GOOGLE_ANALYTICS_DEFAULT_ALLOW_AD_STORAGE - specifies the default setting for allowing Google Analytics to store ad-related data. If set to true, Google Analytics is allowed to store ad-related data; if set to false, it is not allowed to store ad-related data by default. Defaults to true.
- GOOGLE_ANALYTICS_DEFAULT_ALLOW_AD_USER_DATA - specifies the default setting for allowing Google Analytics to collect user-related data for ad targeting and personalization. If set to true, Google Analytics is allowed to collect user-related data for ad targeting and personalization; if set to false, it is not allowed to collect such data by default. Defaults to true.
- GOOGLE_ANALYTICS_DEFAULT_ALLOW_AD_PERSONALIZATION_SIGNALS - specifies the default setting for allowing Google Analytics to collect signals related to ad personalization. If set to true, Google Analytics is allowed to collect ad personalization signals; if set to false, it is not allowed to collect such signals by default. Defaults to true.

$3

The following plugin variables are used to specify the Firebase SDK versions as Gradle dependencies on Android:

- ANDROID_PLAY_SERVICES_TAGMANAGER_VERSION
- ANDROID_PLAY_SERVICES_AUTH_VERSION
- ANDROID_FIREBASE_ANALYTICS_VERSION
- ANDROID_FIREBASE_MESSAGING_VERSION
- ANDROID_FIREBASE_CONFIG_VERSION
- ANDROID_FIREBASE_PERF_VERSION
- ANDROID_FIREBASE_AUTH_VERSION
- $ANDROID_FIREBASE_INAPPMESSAGING_VERSION
- ANDROID_FIREBASE_FIRESTORE_VERSION
- ANDROID_FIREBASE_FUNCTIONS_VERSION
- ANDROID_FIREBASE_INSTALLATIONS_VERSION
- ANDROID_FIREBASE_CRASHLYTICS_VERSION
- ANDROID_FIREBASE_CRASHLYTICS_NDK_VERSION
- ANDROID_GSON_VERSION
- ANDROID_FIREBASE_PERF_GRADLE_PLUGIN_VERSION
- ANDROID_FIREBASE_PERFORMANCE_MONITORING
See Specifying Android library versions for more info.

- ANDROID_ICON_ACCENT - sets the default accent color for system notifications. See Android Notification Color for more info.
- ANDROID_FIREBASE_CONFIG_FILEPATH - sets a custom filepath to google-services.json file as a path relative to the project root
- e.g. --variable ANDROID_FIREBASE_CONFIG_FILEPATH="resources/android/google-services.json"
- ANDROID_FIREBASE_PERFORMANCE_MONITORING - sets whether to add the Firebase Performance Monitoring Gradle plugin for Android to the build.
- e.g. --variable ANDROID_FIREBASE_PERFORMANCE_MONITORING=true
- Defaults to false if not specified.
- ANDROID_FIREBASE_PERF_GRADLE_PLUGIN_VERSION - overrides the default version of the Firebase Performance Monitoring Gradle plugin for Android
- ANDROID_GRPC_OKHTTP - sets version of GRPC OKHTTP library.

$3

- IOS_FIREBASE_SDK_VERSION - a specific version of the Firebase iOS SDK to set in the Podfile
- If not specified, the default version defined in elements in the plugin.xml will be used.
- IOS_FIREBASE_IN_APP_MESSAGING_VERSION - a specific version of the Firebase iOS InAppMessaging SDK to set in the Podfile
- If not specified, the default version defined in elements in the plugin.xml will be used.
- IOS_GOOGLE_SIGIN_VERSION - a specific version of the Google Sign In library to set in the Podfile
- If not specified, the default version defined in the element in the plugin.xml will be used.
- IOS_GOOGLE_TAG_MANAGER_VERSION - a specific version of the Google Tag Manager library to set in the Podfile
- If not specified, the default version defined in the element in the plugin.xml will be used.
- IOS_USE_PRECOMPILED_FIRESTORE_POD - if true, switches Podfile to use a pre-compiled version of the Firestore pod to reduce build time
- Defaults to false if not specified.
- If you set this option to true, you must ensure the environment variable SKIP_FIREBASE_FIRESTORE_SWIFT is set globally to a truthy value
- e.g. If using zsh: echo 'export SKIP_FIREBASE_FIRESTORE_SWIFT=1' >> ~/.zshrc && source ~/.zshrc
- This ensures the pre-built pod is compatible with the Cordova project environment (see here)
- Note that this is a post-install plugin variable so an additional step is required to activate the plugin variable the first time it is specified.
- If you're having issues building with Firestore, see here for suggested solutions.
- IOS_STRIP_DEBUG - prevents symbolification of all libraries included via Cocoapods. See Strip debug symbols for more info.
- e.g. --variable IOS_STRIP_DEBUG=true
- Defaults to false if not specified.
- SETUP_RECAPTCHA_VERIFICATION - automatically sets up reCAPTCHA verification for phone authentication on iOS. See verifyPhoneNumber for more info.
- e.g. --variable SETUP_RECAPTCHA_VERIFICATION=true
- Defaults to false if not specified.
- IOS_SHOULD_ESTABLISH_DIRECT_CHANNEL - If true Firebase Messaging will automatically establish a socket-based, direct channel to the FCM server.
- e.g. --variable IOS_SHOULD_ESTABLISH_DIRECT_CHANNEL=true
- Defaults to false if not specified.
- See shouldEstablishDirectChannelFIRMessaging(py)shouldEstablishDirectChannel>)
- Note: Firebase Messaging iOS SDK version 7.0 will be a breaking change where the SDK will no longer support iOS Direct Channel API.
- IOS_FIREBASE_CONFIG_FILEPATH - sets a custom filepath to GoogleService-Info.plist file as a path relative to the project root
- e.g. --variable IOS_FIREBASE_CONFIG_FILEPATH="resources/ios/GoogleService-Info.plist"
- IOS_ENABLE_APPLE_SIGNIN - enables the Sign In with Apple capability in Xcode.
- --variable IOS_ENABLE_APPLE_SIGNIN=true
- Ensure the associated app provisioning profile also has this capability enabled.
- IOS_ENABLE_CRITICAL_ALERTS_ENABLED - enables the critical alerts capability
- --variable IOS_ENABLE_CRITICAL_ALERTS_ENABLED=true
- See iOS critical notifications
- Ensure the associated app provisioning profile also has this capability enabled.
- IOS_FCM_ENABLED - allows to completely disable push notifications functionality of the plugin (not just the automatic initialization that is covered by FIREBASE_FCM_AUTOINIT_ENABLED variable).
- Defaults to true, if not specified; i.e. FCM is enabled by default.
- This can be handy if you are using this plugin for e.g. Crashlytics and handle push notifications using another plugin. Use --variable IOS_FCM_ENABLED=false in this case.
- IOS_ON_DEVICE_CONVERSION_ANALYTICS - whether to include the On-Device Conversion component of the Firebase SDK.
- Defaults to false if not specified.
- If true, the component will be included and initiateOnDeviceConversionMeasurement can be called at run-time to enable it.
- Note that this is a post-install plugin variable so an additional step is required to activate the plugin variable the first time it is specified.

$3

- Some of the plugin variables above are used to optionally include additional components of the Firebase SDKs.
- Since Cordova does not support using plugin variables to optionally include plugin dependencies, this plugin implements a custom npm post-install script to enable this behaviour.
- This script is executed automatically after the plugin is installed and will apply the plugin variables defined in your project's package.json to the plugin's plugin.xml file before Cordova parses the plugin.xml file.
- However, the first time you specify a new plugin variable, the post-install script will be executed before Cordova has added the plugin variable to the package.json file so the plugin variable will not be applied to the plugin.xml file.
- IMPORTANT: Therefore if you specify a plugin variable for the first time, you must reinstall the plugin for the plugin variable to be applied to the plugin.xml file:
- e.g. cordova plugin rm cordova-plugin-firebasex --nosave && cordova plugin add cordova-plugin-firebasex --nosave
- Note: you do not have to specify the plugin variable(s) again when reinstalling the plugin as they will be read from the package.json file.

Supported Cordova Versions

- cordova: >= 10
- cordova-android: >= 10
- cordova-ios: >= 6

Supported Mobile Platform Versions

The supported versions of Android and iOS depend on the version of the Firebase SDK included in the build.

See the Firebase iOS and Android release notes to determine the minimum support OS versions for the SDK version included in your build.
If you didn't explicity specify a version for the Firebase SDK using plugin variables at plugin installation time, you can find the current default version in the plugin's plugin.xml.

Migrating from cordova-plugin-firebase

This plugin is a fork of cordova-plugin-firebase which has been reworked to fix issues and add new functionality.
If you already have cordova-plugin-firebase installed in your Cordova project, you need to completely remove it before installing this plugin otherwise they will conflict and cause build errors in your project. The safest way of doing this is as follows:

rm -Rf platforms/android
cordova plugin rm cordova-plugin-firebase
rm -Rf plugins/ node_modules/
npm install
cordova plugin add cordova-plugin-firebasex
cordova platform add android

$3

IMPORTANT: Recent versions of cordova-plugin-firebasex have made breaking changes to the plugin API in order to fix bugs or add more functionality.
Therefore you can no longer directly substitute cordova-plugin-firebasex in place of cordova-plugin-firebase without making code changes.

You should be aware of the following breaking changes compared with cordova-plugin-firebase:

- Minimum supported Cordova versions
- cordova@10 (CLI)
- cordova-android@10 (Android platform)
- cordova-ios@6 (iOS platform)
- Migrated to AndroidX from legacy Android Support Library
- Migrated to Cocoapods to satisfy Firebase SDK dependencies on iOS
- onNotificationOpen() renamed to onMessageReceived()
- tap parameter is only set when user taps on a notification (not when a message is received from FCM)
- tap=foreground|background instead of tap=true|false
- hasPermission() receives argument as a boolean (rather than an object with isEnabled key)
- e.g. FirebasePlugin.hasPermission(function(hasPermission){
console.log("Permission is " + (hasPermission ? "granted" : "denied"));
});
- Adds support for foreground notifications and data notification messages

$3

Ionic Native provides a FirebaseX Typescript wrapper for using cordova-plugin-firebasex with Ionic v4, v5 and above.
Please see their documentation for usage.

First install the package.

`
ionic cordova plugin add cordova-plugin-firebasex
npm install @ionic-native/firebase-x
`

If you're using Angular, register it in your component/service's NgModule (for example, app.module.ts) as a provider.

`typescript
import { FirebaseX } from "@ionic-native/firebase-x/ngx";

@NgModule({
//declarations, imports...
providers: [
FirebaseX,
//other providers...
]
})
`

Then you're good to go.

`typescript
import { FirebaseX } from "@ionic-native/firebase-x/ngx";

//...

constructor(private firebase: FirebaseX)

this.firebase.getToken().then(token => console.log(The token is ${token}))
this.firebase.onMessageReceived().subscribe(data => console.log(FCM message: ${data}));
`

NOTE:

- This plugin provides only the Javascript API as documented below.
- The Typescript wrapper is owned and maintain by Ionic.
- Please report any issues against the Ionic Native repo, not this one.
- Any issues opened against this repo which relate to the Typescript wrapper will be closed immediately.

$3

The above PR does not work for Ionic 3 so you (currently) can't use the Ionic Native Firebase Typescript wrapper with Ionic 3.
(i.e. import { Firebase } from "@ionic-native/firebase" will not work).

To use cordova-plugin-firebasex with Ionic 3, you'll need to call its Javascript API directly from your Typescript app code, for example:

`typescript
(window).FirebasePlugin.getToken((token) => console.log(token: ${token}))
(window).FirebasePlugin.onMessageReceived((message) => {
if (message.tap) {
console.log(Notification was tapped in the ${message.tap});
}
});
`

If you want to make the onMessageReceived() JS API behave like the Ionic Native wrapper:

`javascript
onNotificationOpen() {
return new Observable(observer => {
(window as any).FirebasePlugin.onMessageReceived((response) => {
observer.next(response);
});
});
}
...
this.onNotificationOpen().subscribe(data => console.log(FCM message: ${data}));
`

See the cordova-plugin-firebasex-ionic3-test example project for a demonstration of how to use the plugin with Ionic 3.

Build environment notes

Remote Cloud Build

This plugin will not work with remote cloud build services that do not support Cordova hook scripts (e.g. Ionic Appflow).
The hook scripts used by this plugin are essential to configure the native platform projects for use with the Firebase SDK and therefore if they are not executed, the plugin will not work correctly: either the build will fail or the app containing the plugin will crash at runtime.

Even if the remote build service supports Cordova hook scripts, it is hard to diagnose the cause of build issue because the environment is not under your direct control.
Therefore a local build environment is highly recommended since you have full control and the ability to update/upgrade any components in the OS.
Support for using this plugin can only be offered when building projects in a local environment. (i.e. your own development machine).

However if you are unable to build locally and therefore must use a remote build environment, then VoltBuilder is recommended for use with this plugin as it supports Cordova hook scripts and its developers have explicitly tested building with this plugin to ensure compatibility.

Capacitor support

This plugin does not currently support Capacitor. If you want to use Firebase with Capacitor, you should use Capacitor Firebase or the Firebase JS SDK instead.

This plugin is designed to work with Cordova therefore relies on Cordova features such as hook scripts, plugin variables and project structure in order to manipulate the native platform projects for use with the Firebase SDK.

Android-specific

$3

This plugin depends on various components such as the Firebase SDK which are pulled in at build-time by Gradle on Android.
By default this plugin pins specific versions of these in its plugin.xml where you can find the currently pinned versions as 's, for example:

`xml

`

The Android defaults can be overridden at plugin installation time by specifying plugin variables as command-line arguments, for example:

cordova plugin add cordova-plugin-firebasex --variable ANDROID_FIREBASE_ANALYTICS_VERSION=17.0.0

Or you can specify them as plugin variables in your config.xml, for example:

`xml



`

The following plugin variables are used to specify the following Gradle dependency versions on Android:

- ANDROID_PLAY_SERVICES_TAGMANAGER_VERSION => com.google.android.gms:play-services-tagmanager
- ANDROID_PLAY_SERVICES_AUTH_VERSION => com.google.android.gms:play-services-auth
- ANDROID_FIREBASE_ANALYTICS_VERSION => com.google.firebase:firebase-analytics
- ANDROID_FIREBASE_MESSAGING_VERSION => com.google.firebase:firebase-messaging
- ANDROID_FIREBASE_CONFIG_VERSION => com.google.firebase:firebase-config
- ANDROID_FIREBASE_PERF_VERSION => com.google.firebase:firebase-perf
- ANDROID_FIREBASE_AUTH_VERSION => com.google.firebase:firebase-auth
- ANDROID_FIREBASE_FIRESTORE_VERSION => com.google.firebase:firebase-firestore
- $ANDROID_FIREBASE_FUNCTIONS_VERSION => com.google.firebase:firebase-functions
- $ANDROID_FIREBASE_INSTALLATIONS_VERSION => com.google.firebase:firebase-installations
- $ANDROID_FIREBASE_INAPPMESSAGING_VERSION => com.google.firebase:firebase-inappmessaging-display
- ANDROID_FIREBASE_CRASHLYTICS_VERSION => com.google.firebase:firebase-crashlytics
- ANDROID_FIREBASE_CRASHLYTICS_NDK_VERSION => com.google.firebase:firebase-crashlytics-ndk
- ANDROID_GSON_VERSION => com.google.code.gson:gson

For example:

cordova plugin add cordova-plugin-firebasex \
--variable ANDROID_PLAY_SERVICES_TAGMANAGER_VERSION=17.0.0 \
--variable ANDROID_PLAY_SERVICES_AUTH_VERSION=17.0.0 \
--variable ANDROID_FIREBASE_ANALYTICS_VERSION=17.0.0 \
--variable ANDROID_FIREBASE_MESSAGING_VERSION=19.0.0 \
--variable ANDROID_FIREBASE_CONFIG_VERSION=18.0.0 \
--variable ANDROID_FIREBASE_PERF_VERSION=18.0.0 \
--variable ANDROID_FIREBASE_AUTH_VERSION=18.0.0 \
--variable ANDROID_FIREBASE_CRASHLYTICS_VERSION=17.0.1 \
--variable ANDROID_FIREBASE_CRASHLYTICS_NDK_VERSION=17.0.1 \

$3

This plugin has been migrated to use AndroidX (Jetpack) which is the successor to the Android Support Library.
This is because the major release of the Firebase and Play Services libraries on 17 June 2019 were migrated to AndroidX.

The cordova-android@9 platform adds implicit support for AndroidX so (if you haven't already done so) you should update to this platform version:

cordova platform rm android && cordova platform add android@latest

and enable AndroidX by setting the following preference in your config.xml:

If you are unable to update from cordova-android@8, you can add cordova-plugin-androidx to your project which enables AndroidX in the Android platform project:

cordova plugin add cordova-plugin-androidx

If your project includes any plugins which are dependent on the legacy Android Support Library (to which AndroidX is the successor), you should add cordova-plugin-androidx-adapter to your project which will dynamically migrate any plugin code from the Android Support Library to AndroidX equivalents:

cordova plugin add cordova-plugin-androidx-adapter

Google Play Services and Firebase libraries

Your Android build may fail if you are installing multiple plugins that use the Google Play Services library.
This is caused by plugins installing different versions of the Google Play Services library.
This can be resolved by installing cordova-android-play-services-gradle-release which enables you to override the versions specified by other plugins in order to align them.

Similarly, if your build is failing because multiple plugins are installing different versions of the Firebase library,
you can try installing cordova-android-firebase-gradle-release to align these.

iOS-specific

Please ensure you have the latest Xcode release version installed to build your app - direct download links can be found here.

$3

This plugin depends on various components such as the Firebase SDK which are pulled in at build-time by Cocoapods on iOS.
This plugin pins specific versions of these in its plugin.xml where you can find the currently pinned iOS versions in the 's, for example:

Cordova does not natively support the use of plugin variables in the 's spec attribute, however this plugin uses a hook script to enable this behaviour by overriding the version specified in plugin.xml directly within the Podfile.
Therefore to override the version of the Firebase iOS SDK components set in the plugin.xml, you should define it using the IOS_FIREBASE_SDK_VERSION plugin variable when installing the plugin into your project.
For example:

cordova plugin add cordova-plugin-firebasex --variable IOS_FIREBASE_SDK_VERSION=9.1.0

$3

This plugin relies on Cordova support for the CocoaPods dependency manager in order to satisfy the iOS Firebase SDK library dependencies.

Please make sure you have cocoapods@>=1.11.2 installed in your iOS build environment - setup instructions can be found here.

If building your project in Xcode, you need to open YourProject.xcworkspace (not YourProject.xcodeproj) so both your Cordova app project and the Pods project will be loaded into Xcode.

You can list the pod dependencies in your Cordova iOS project by installing cocoapods-dependencies:

sudo gem install cocoapods-dependencies
cd platforms/ios/
pod dependencies

$3

If you receive a build error such as this:

None of your spec sources contain a spec satisfying the dependencies: Firebase/Analytics (~> 6.1.0), Firebase/Analytics (= 6.1.0, ~> 6.1.0).

Make sure your local Cocoapods repo is up-to-date by running pod repo update then run pod install in /your_project/platforms/ios/.

$3

Make sure cordova-plugin-firebasex is last plugin in cordova section of your package.json

`json
{
...
"cordova": {
"platforms": [
"browser",
"ios",
"android"
],
"plugins": {
...
"cordova-plugin-firebasex": {
...
}
}
},
....
}
`

$3

If your iOS app build contains too many debug symbols (i.e. because you include lots of libraries via a Cocoapods), you might get an error (e.g. issue #28) when you upload your binary to App Store Connect, e.g.:

ITMS-90381: Too many symbol files - These symbols have no corresponding slice in any binary [16EBC8AC-DAA9-39CF-89EA-6A58EB5A5A2F.symbols, 1B105D69-2039-36A4-A04D-96C1C5BAF235.symbols, 476EACDF-583B-3B29-95B9-253CB41097C8.symbols, 9789B03B-6774-3BC9-A8F0-B9D44B08DCCB.symbols, 983BAE60-D245-3291-9F9C-D25E610846AC.symbols].

To prevent this, you can set the IOS_STRIP_DEBUG plugin variable which prevents symbolification of all libraries included via Cocoapods (see here for more information):

cordova plugin add cordova-plugin-firebasex --variable IOS_STRIP_DEBUG=true

By default, this preference is set to false.

Note: if you enable this setting, any crashes that occur within libraries included via Cocopods will not be recorded in Crashlytics or other crash reporting services.

$3

- Older versions of the Firebase Inapp Messaging SDK and Google Tag Manager SDK components caused build issues) when building via the Cordova CLI.
- Therefore, the cli_build branch was kept in sync with master but without the above components.
- However, in recent versions, the Firebase Inapp Messaging SDK and Google Tag Manager SDK components no longer cause build issues when building via the Cordova CLI.
- Therefore, the cli_build branch is no longer maintained and the master branch should be used for Cordova CLI builds.

Firebase config setup

There's a handy installation and setup guide on medium.com.
However, if using this, remember this forked plugin is cordova-plugin-firebasex (not cordova-plugin-firebase).

Download your Firebase configuration files, GoogleService-Info.plist for iOS and google-services.json for android, and place them in the root folder of your cordova project.
Check out this firebase article for details on how to download the files.

`
- My Project/
platforms/
plugins/
www/
config.xml
google-services.json <--
GoogleService-Info.plist <--
...
`

Or you can set custom location for your platform configuration files using plugin variables in your config.xml:

`




`

IMPORTANT: The Firebase SDK requires the configuration files to be present and valid, otherwise your app will crash on boot or Firebase features won't work.

Disable data collection on startup

By default, analytics, performance and Crashlytics data will begin being collected as soon as the app starts up.
However, for data protection or privacy reasons, you may wish to disable data collection until such time as the user has granted their permission.

To do this, set the following plugin variables to false at plugin install time:

- FIREBASE_ANALYTICS_COLLECTION_ENABLED
- FIREBASE_PERFORMANCE_COLLECTION_ENABLED
- FIREBASE_CRASHLYTICS_COLLECTION_ENABLED
- GOOGLE_ANALYTICS_ADID_COLLECTION_ENABLED
- GOOGLE_ANALYTICS_DEFAULT_ALLOW_ANALYTICS_STORAGE
- GOOGLE_ANALYTICS_DEFAULT_ALLOW_AD_STORAGE
- GOOGLE_ANALYTICS_DEFAULT_ALLOW_AD_USER_DATA
- GOOGLE_ANALYTICS_DEFAULT_ALLOW_AD_PERSONALIZATION_SIGNALS

cordova plugin add cordova-plugin-firebasex \
--variable FIREBASE_ANALYTICS_COLLECTION_ENABLED=false \
--variable FIREBASE_PERFORMANCE_COLLECTION_ENABLED=false \
--variable FIREBASE_CRASHLYTICS_COLLECTION_ENABLED=false \
--variable GOOGLE_ANALYTICS_ADID_COLLECTION_ENABLED=false \
--variable GOOGLE_ANALYTICS_DEFAULT_ALLOW_ANALYTICS_STORAGE=false \
--variable GOOGLE_ANALYTICS_DEFAULT_ALLOW_AD_STORAGE=false \
--variable GOOGLE_ANALYTICS_DEFAULT_ALLOW_AD_USER_DATA=false \
--variable GOOGLE_ANALYTICS_DEFAULT_ALLOW_AD_PERSONALIZATION_SIGNALS=false

This will disable data collection (on both Android & iOS) until you call setAnalyticsCollectionEnabled, setPerformanceCollectionEnabled, setCrashlyticsCollectionEnabled and setAnalyticsConsentMode:

FirebasePlugin.setAnalyticsCollectionEnabled(true);
FirebasePlugin.setPerformanceCollectionEnabled(true);
FirebasePlugin.setCrashlyticsCollectionEnabled(true);
FirebasePlugin.setAnalyticsConsentMode({
ANALYTICS_STORAGE: "GRANTED",
AD_STORAGE: "GRANTED",
AD_USER_DATA: "GRANTED",
AD_PERSONALIZATION: "GRANTED",
});

Notes:

- Calling setXCollectionEnabled() will have no effect if the corresponding FIREBASE_X_COLLECTION_ENABLED variable is set to true.
- Calling setXCollectionEnabled(true|false) will enable/disable data collection during the current app session and across subsequent app sessions until such time as the same method is called again with a different value.

Example project

An example project repo exists to demonstrate and validate the functionality of this plugin:
https://github.com/dpa99c/cordova-plugin-firebasex-test

Please use this as a working reference.

Before reporting any issues, please (if possible) test against the example project to rule out causes external to this plugin.

Reporting issues

IMPORTANT: Please read the following carefully.
Failure to follow the issue template guidelines below will result in the issue being immediately closed.

Reporting a bug or problem

Before opening a bug issue, please do the following:

- _DO NOT_ open issues asking for support in using/integrating the plugin into your project
- Only open issues for suspected bugs/issues with the plugin that are generic and will affect other users
- I don't have time to offer free technical support: this is free open-source software
- Ask for help on StackOverflow, Ionic Forums, etc.
- Use the example project as a known working reference
- Any issues requesting support will be closed immediately.
- _DO NOT_ open issues related to the Ionic Typescript wrapper for this plugin
- This is owned/maintained by Ionic and is not part of this plugin
- Please raise such issues/PRs against Ionic Native instead.
- To verify an if an issue is caused by this plugin or its Typescript wrapper, please re-test using the vanilla Javascript plugin interface (without the Ionic Native wrapper).
- Any issue opened here which is obviously an Ionic Typescript wrapper issue will be closed immediately.
- _DO NOT_ open issues related to Remote Cloud Build environments such as Ionic Appflow as these are not supported
- If you are migrating from cordova-plugin-firebase to cordova-plugin-firebasex please make sure you have read the Migrating from cordova-plugin-firebase section.
- Read the above documentation thoroughly
- For example, if you're having a build issue ensure you've read through the build environment notes
- If an iOS CLI build is failing, ensure you've read the Cordova CLI builds section
- Check the CHANGELOG for any breaking changes that may be causing your issue.
- Check a similar issue (open or closed) does not already exist against this plugin.
- Duplicates or near-duplicates will be closed immediately.
- When creating a new issue
- Choose the "Bug report" template
- Fill out the relevant sections of the template and delete irrelevant sections
- _WARNING:_ Failure to complete the issue template will result in the issue being closed immediately.
- Reproduce the issue using the example project
- This will eliminate bugs in your code or conflicts with other code as possible causes of the issue
- This will also validate your development environment using a known working codebase
- If reproducing the issue using the example project is not possible, create an isolated test project that you are able to share
- Support cannot be offered to help resolve build issues in your own project.
- Include full verbose console output when reporting build issues
- If the full console output is too large to insert directly into the Github issue, then post it on an external site such as Pastebin and link to it from the issue
- Often the details of an error causing a build failure is hidden away when building with the CLI
- To get the full detailed console output, append the --verbose flag to CLI build commands
- e.g. cordova build ios --verbose
- Failure to include the full console output will result in the issue being closed immediately
- If the issue relates to the plugin documentation (and not the code), please of a documentation issue

Requesting a new feature

Before opening a feature request issue, please do the following:

- Check the above documentation to ensure the feature you are requesting doesn't already exist
- Check the list if open/closed issues to check if there's a reason that feature hasn't been included already
- Ensure the feature you are requesting is actually possible to implement and generically useful to other users than yourself
- Where possible, post a link to the documentation related to the feature you are requesting
- Include other relevant links, e.g.
- Stack Overflow post illustrating a solution
- Code within another Github repo that illustrates a solution

Cloud messaging

There are 2 distinct types of messages that can be sent by Firebase Cloud Messaging (FCM):

- Notification messages
- automatically displayed to the user by the operating system on behalf of the client app while your app is not running or is in the background
- if your app is in the foreground when the notification message arrives, it is passed to the client app and it is the responsibility of the client app to display it.
- have a predefined set of user-visible keys and an optional data payload of custom key-value pairs.
- Data messages
- Client app is responsible for processing data messages.
- Data messages have only custom key-value pairs.

Note: only notification messages can be sent via the Firebase Console - data messages must be sent via the FCM APIs.

Background notifications

If the notification message arrives while the app is in the background/not running, it will be displayed as a system notification.

If the user taps the system notification, this launches/resumes the app and the notification title, body and optional data payload is passed to the onMessageReceived callback.
When the onMessageReceived is called in response to a user tapping a system notification while the app is in the background/not running, it will be passed the property tap: "background".

By default, no callback is made to the plugin when the message arrives while the app is not in the foreground, since the display of the notification is entirely handled by the operating system.
However, there are platform-specific circumstances where a callback can be made, when a message arrives while the app is in the background or is inactive, that doesn't require user interaction to receive the message payload - see Android background notifications and iOS background notifications for details.

Foreground notifications

If the notification message arrives while the app is in running in the foreground, by default it will NOT be displayed as a system notification.
Instead the notification message payload will be passed to the onMessageReceived callback for the plugin to handle (tap will not be set).

If you include the notification_foreground key in the data payload, the plugin will also display a system notification upon receiving the notification messages while the app is running in the foreground.
For example:

`json
{
"name": "my_notification",
"notification": {
"body": "Notification body",
"title": "Notification title"
},
"data": {
"notification_foreground": "true"
}
}
`

When the onMessageReceived is called in response to a user tapping a system notification while the app is in the foreground, it will be passed the property tap: "foreground".

You can set additional properties of the foreground notification using the same key names as for Data Message Notifications.

Android notifications

Notifications on Android can be customised to specify the sound, icon, LED colour, etc. that's displayed when the notification arrives.

$3

If the notification message arrives while the app is in the background/not running, it will be displayed as a system notification.

If the user then taps the system notification, the app will be brought to the foreground and onMessageReceived will be invoked again, this time with tap: "background" indicating that the user tapped the system notification while the app was in the background.

If a notification message arrives while the app is in the background or inactive, it will be queued until the next time the app is resumed into the foreground. This is to ensure the Cordova application running in the Webview is in a state where it can receive the notification message.
Upon resuming, each queued notification will be sent to the onMessageReceived callback without the tap property, indicating the message was received without user interaction.

If you wish to attempt to immediately deliver the message payload to the onMessageReceived callback when the app is in the background or inactive (the default behaviour of this plugin prior to v18), you can set the FIREBASE_MESSAGING_IMMEDIATE_PAYLOAD_DELIVERY plugin variable to true at plugin install time:

cordova plugin add cordova-plugin-firebasex --variable FIREBASE_MESSAGING_IMMEDIATE_PAYLOAD_DELIVERY=true

However there is no guarantee that the message will be delivered successfully, since the Cordova application running in the Webview may not be in a state where it can receive the notification message.


In addition to the title and body of the notification message, Android system notifications support specification of the following notification settings:

- Icon
- Sound
- Color accent
- Channel ID (Android 8.0 (O) and above)
- This channel configuration enables you to specify:
- Sound
- Vibration
- LED light
- Badge
- Importance
- Visibility
- See createChannel for details.

Note: on tapping a background notification, if your app is not running, only the data section of the notification message payload will be delivered to onMessageReceived.
i.e. the notification title, body, etc. will not. Therefore if you need the properties of the notification message itself (e.g. title & body) to be delivered to onMessageReceived, you must duplicate these in the data section, e.g.:

`json
{
"name": "my_notification",
"notification": {
"body": "Notification body",
"title": "Notification title"
},
"data": {
"notification_body": "Notification body",
"notification_title": "Notification title"
}
}
`

$3

If the notification message arrives while the app is in the foreground, by default a system notification won't be displayed and the data will be passed to onMessageReceived.

However, if you set the notification_foreground key in the data section of the notification message payload, this will cause the plugin to display system notification when the message is received while your app is in the foreground. You can customise the notification using the same keys as for Android data message notifications.

$3

- Android 8 (O) introduced notification channels.
- Notification channels are configured by the app and used to determine the sound/lights/vibration settings of system notifications.
- By default, this plugin creates a default channel with default properties
- These can be overridden via the setDefaultChannel function.
- The plugin enables the creation of additional custom channels via the createChannel function.

First you need to create a custom channel with the desired settings, for example:

`javascript
var channel = {
id: "my_channel_id",
sound: "mysound",
vibration: true,
light: true,
lightColor: parseInt("FF0000FF", 16).toString(),
importance: 4,
badge: true,
visibility: 1,
};

FirebasePlugin.createChannel(
channel,
function () {
console.log("Channel created: " + channel.id);
},
function (error) {
console.log("Create channel error: " + error);
}
);
`

Then reference it from your message payload:

`json
{
"name": "my_notification",
"notification": {
"body": "Notification body",
"title": "Notification title"
},
"android": {
"notification": {
"channel_id": "my_channel_id"
}
}
}
`

#### Android 7 and below

- the channel referenced in the message payload will be ignored
- the sound setting of system notifications is specified in the notification message itself - see Android Notification Sound.

$3

By default the plugin will use the default app icon for notification messages.

#### Android Default Notification Icon

To define a custom default notification icon, you need to create the images and deploy them to the /platforms/android/app/src/main/res/ folders.
The easiest way to create the images is using the Image Asset Studio in Android Studio or using the Android Asset Studio webapp.

The icons should be monochrome transparent PNGs with the following sizes:

- mdpi: 24x24
- hdpi: 36x36
- xhdpi: 48x48
- xxhdpi: 72x72
- xxxhdpi: 96x96

Once you've created the images, you need to deploy them from your Cordova project to the native Android project.
To do this, copy the drawable-DPI image directories into your Cordova project and add entries to the section of your config.xml, where src specifies the relative path to the images files within your Cordova project directory.

For example, copy thedrawable-DPI image directories to /res/android/ and add the following to your config.xml:

`xml







`

The default notification icon images must be named notification_icon.png.

You then need to add a block to the config.xml which will instruct Firebase to use your icon as the default for notifications:

`xml





`

#### Android Large Notification Icon

The default notification icons above are monochrome, however you can additionally define a larger multi-coloured icon.

NOTE: FCM currently does not support large icons in system notifications displayed for notification messages received in the while the app is in the background (or not running).
So the large icon will currently only be used if specified in data messages or foreground notifications.

The large icon image should be a PNG-24 that's 256x256 pixels and must be named notification_icon_large.png and should be placed in the drawable-xxxhdpi resource directory.
As with the small icons, you'll need to add a entry to the section of your config.xml:

`xml



`

#### Android Custom Notification Icons

You can define additional sets of notification icons in the same manner as above.
These can be specified in notification or data messages.

For example:

`xml






`

When sending an FCM notification message, you will then specify the icon name in the android.notification section, for example:

`json
{
"name": "my_notification",
"notification": {
"body": "Notification body",
"title": "Notification title"
},
"android": {
"notification": {
"icon": "my_icon"
}
},
"data": {
"notification_foreground": "true"
}
}
`

You can also reference these icons in data messages, for example:

`json
{
"name": "my_data",
"data": {
"notification_foreground": "true",
"notification_body": "Notification body",
"notification_title": "Notification title",
"notification_android_icon": "my_icon"
}
}
`

$3

On Android Lollipop (5.0/API 21) and above you can set the default accent color for the notification by adding a color setting.
This is defined as an ARGB colour>) which the plugin sets by default to #FF00FFFF (cyan).
Note: On Android 7 and above, the accent color can only be set for the notification displayed in the system tray area - the icon in the statusbar is always white.

You can override this default by specifying a value using the ANDROID_ICON_ACCENT plugin variable during plugin installation, for example:

cordova plugin add cordova-plugin-firebasex --variable ANDROID_ICON_ACCENT=#FF123456

You can override the default color accent by specifying the colour key as an RGB value in a notification message, e.g.:

``json
{
"name": "my_notification",
"notification": {
"body": "Notification body",
"title": "Notification title"