Android - FirebaseApp / Firebase-Initialization is not starting

Question

I want to implement the Firebase-Messaging plugin into my Android-App. I've started with the "quickstart-android-master/messaging"-example from github: https://github.com/firebase/quickstart-android/tree/master/messaging

This works for me! Log-Output:

D/FirebaseApp﹕ com.google.firebase.auth.FirebaseAuth is not linked. Skipping initialization.
D/FirebaseApp﹕ Initialized class com.google.firebase.iid.FirebaseInstanceId.
D/FirebaseApp﹕ com.google.firebase.crash.FirebaseCrash is not linked. Skipping initialization
D/FirebaseApp﹕ Initialized class com.google.android.gms.measurement.AppMeasurement.
I/FirebaseInitProvider﹕ FirebaseApp initialization successful

But if I want to implement the Plugin "com.google.firebase:firebase-messaging:9.0.2" into my app, the FirebaseApp isn't initialized! So the FirebaseApp plugin isn't starting! - No Log or token received!

I've also added apply plugin to build.gradle file in "app"-directory:

    apply plugin: 'com.android.application'

android {
  // ...
}

dependencies {
  // ...
  compile 'com.google.firebase:firebase-messaging:9.0.2'
}

// ADD THIS AT THE BOTTOM
apply plugin: 'com.google.gms.google-services'

And the google-services plugin to build.gradle in the "root" directory:

buildscript {
    // ...
    dependencies {
        // ...
        classpath 'com.google.gms:google-services:3.0.0'
    }
}

Problems could be:

AndroidAnnotations, Proguard, Product flavors...

yes, I've created it on firebase console! And I also have used my package-name in the example. — Manuel Schmitzberger, Jun 09 '16 at 11:34
Are you simply judging firebase initialization through the logs or did you try to get the instance in the app ? — Shubhank, Jun 09 '16 at 11:39
Could it be a conflict with AndroidAnnotations (http://androidannotations.org/) ? — Manuel Schmitzberger, Jun 09 '16 at 11:39
@Shubhank, I go trough the logs. If I want to get the Token in the Activity, I get this error: "FirebaseApp with name [DEFAULT] doesn't exist." — Manuel Schmitzberger, Jun 09 '16 at 11:41
would you try creating the app from scratch? here is a [tutorial](http://shubhank101.github.io/iOSAndroidChaosOverFlow/2016/06/Implementing-FCM-(-Firebase-Cloud-Messaging-)-in-Android-App) i did for it — Shubhank, Jun 09 '16 at 11:42
Or there could be also a problem with "proguard", but I'm not sure. And I've tested everything... — Manuel Schmitzberger, Jun 09 '16 at 11:46
Assuming that you have added the google-services.json file to your project. It may be the device has an old version of Google Play services. — Arthur Thompson, Jun 10 '16 at 20:50
Thx Arthur, for your comment. Yes I've added the google-service.json file. And you are right, this could be a problem, but the example APP from github works on this phone. — Manuel Schmitzberger, Jun 11 '16 at 08:09

Manuel Schmitzberger · Accepted Answer · 2019-02-21T06:03:44.357

20

My problem was the "Manifest Merger". If I use the

xmlns:tools="http://schemas.android.com/tools"

and

tools:node="replace"

in the Application Tag of the Manifest, the FirebaseApp will not be initialized!

If you use replace attr on tools:node it will replace your lower priority declaration with the annotated one (see more here). You should use merge or merge only attributes instead.

So what I've exactly done:

This doesn't work:

<application
            android:name="xxx"
            android:icon="@mipmap/ic_launcher"
            android:label="@string/application_name"
            android:theme="@style/Theme.TemplateStyle"
            tools:node="replace">

this works:

<application
            android:name="xxx"
            android:icon="@mipmap/ic_launcher"
            android:label="@string/application_name"
            android:theme="@style/Theme.TemplateStyle">
            <!-- tools:node="replace"-->

If you want to overwrite or replace some attributes, use tools:replace instead!

edited Feb 21 '19 at 06:03

answered Jun 15 '16 at 09:21

Manuel Schmitzberger

5,162
3
36
45

So I have to remove tool in order to fine working of firebase? – Pritish Joshi Jun 29 '16 at 09:34
1

Currently i have updated to tools:replace="android:name" instead of tools:node="replace". hope that help – Shubham AgaRwal Jun 30 '16 at 16:43
1

@ManuelSchmitzberger Hi Manuel, could you please tell us what is this 'Manifest Merger' and where do we find these lines please? – fralbo Jul 02 '16 at 14:59
@2ndGAB you can find the link for the description in the answer above. Normally you don't need this so called "Manifest Merger", only if you're using "productFlavors", you want to override a SDK Manifest or something like that. It is declared in the AndroidManifest! – Manuel Schmitzberger Jul 04 '16 at 04:47
2

I dont get it, in Manifest what needs to be added actually? Can you give complete example?? – Jawad Amjad Aug 24 '16 at 06:45
1

where i can find tools:node="replace" i don;t have thin in my menifest file – Darshan Khatri Sep 08 '18 at 13:30
@DarshanKhatri, if you don't use the node-tool in your Manifest, then this should not be your problem! – Manuel Schmitzberger Sep 10 '18 at 07:43
2

Yes You are right ,I have Solved it by just reinstalling the app :) – Darshan Khatri Sep 11 '18 at 09:46

score 0 · Answer 2 · answered Dec 17 '18 at 06:43

In my case these permissions were missing in Android Manifest file:

<permission
        android:name="com.app.appname.permission.C2D_MESSAGE"
        android:protectionLevel="signature" />

   <uses-permission android:name="com.app.appname.permission.C2D_MESSAGE" />
    <uses-permission android:name="com.google.android.c2dm.permission.RECEIVE" />

score 0 · Answer 3 · answered Feb 20 '19 at 22:21

0

This close the issue for me:

implementation 'com.google.firebase:firebase-crash:16.2.1'
implementation 'com.google.firebase:firebase-auth:16.1.0'

answered Feb 20 '19 at 22:21

Ashot

399
4
7

score 0 · Answer 4 · answered Jan 16 '20 at 07:09

0

In my case I was missing permission <uses-permission android:name="android.permission.INTERNET"/> then reinstall the app

answered Jan 16 '20 at 07:09

NullPointerException

3,978
4
34
52

score 0 · Answer 5 · answered Mar 18 '21 at 14:16

Another sign there are problems are logcat lines like this

FirebaseAuth: [GetAuthDomainTask] Error getting project config. Failed with INVALID_CERT_HASH 400
FirebaseAuth: [SmsRetrieverHelper] SMS verification code request failed: unknown status code: 17093 null

Check google-service.json, it should have your apk sha1 in it:

apk: sha1

SHA1: 4E:AA:54:E0:08:93:C6:CB:7B:8C:74:1E:2A:55:E7:60:XX:XX:XX:XX

google-service.json:

            "certificate_hash": "4eaa54e00893c6cb7b8c741e2a55e760a5XXXXXX"

Delete the whole Android project in firebase, add it again and add your apk sha1. If your sha1 key changes (ie new app) delete the Android project again and start fresh.

In the past, in anger, I added sha256 and also tried setting up Android Device Verification, SafetyNet etc, none of these are needed.

score -1 · Answer 6 · edited Aug 25 '16 at 12:35

-1

I had the same problem, add the following:

com.google.firebase:firebase-core before com.google.firebase:firebase-messaging

dependences {

    compile 'com.google.firebase:firebase-core:9.4.0'
    compile 'com.google.firebase:firebase-messaging:9.4.0'

}

edited Aug 25 '16 at 12:35

DanielBarbarian

5,093
12
35
44

answered Aug 25 '16 at 12:19

tehuelche

31
2

4

this does not help to me – pellyadolfo Sep 30 '16 at 19:31

Android - FirebaseApp / Firebase-Initialization is not starting

6 Answers6

So what I've exactly done:

Linked