Update from 11 to 17 and my notifications stopped working.

[torbentschechne]

Hey there,

I updated cordova-android from 9 to 13 and cordova-plugin-firebasex from 11.0.3-cli to 17.0.0.

Then I went to the package.json and updated the versions as shown here (https://github.com/dpa99c/cordova-plugin-firebasex/blob/master/plugin.xml#L80) to this:

"cordova-plugin-firebasex": {
                "FIREBASE_ANALYTICS_COLLECTION_ENABLED": "true",
                "FIREBASE_PERFORMANCE_COLLECTION_ENABLED": "true",
                "FIREBASE_CRASHLYTICS_COLLECTION_ENABLED": "true",
                "FIREBASE_FCM_AUTOINIT_ENABLED": "true",
                "FIREBASE_ANALYTICS_WITHOUT_ADS": "false",
                "GOOGLE_ANALYTICS_ADID_COLLECTION_ENABLED": "true",
                "GOOGLE_ANALYTICS_DEFAULT_ALLOW_ANALYTICS_STORAGE": "true",
                "GOOGLE_ANALYTICS_DEFAULT_ALLOW_AD_STORAGE": "true",
                "GOOGLE_ANALYTICS_DEFAULT_ALLOW_AD_USER_DATA": "true",
                "GOOGLE_ANALYTICS_DEFAULT_ALLOW_AD_PERSONALIZATION_SIGNALS": "true",
                "ANDROID_ICON_ACCENT": "#FF00FFFF",
                "ANDROID_FIREBASE_PERFORMANCE_MONITORING": "false",
                "ANDROID_PLAY_SERVICES_TAGMANAGER_VERSION": "18.1.0",
                "ANDROID_PLAY_SERVICES_AUTH_VERSION": "21.2.0",
                "ANDROID_FIREBASE_ANALYTICS_VERSION": "22.1.0",
                "ANDROID_FIREBASE_MESSAGING_VERSION": "24.0.1",
                "ANDROID_FIREBASE_CONFIG_VERSION": "22.0.0",
                "ANDROID_FIREBASE_PERF_VERSION": "21.0.1",
                "ANDROID_FIREBASE_AUTH_VERSION": "23.0.0",
                "ANDROID_FIREBASE_INAPPMESSAGING_VERSION": "21.0.0",
                "ANDROID_FIREBASE_FIRESTORE_VERSION": "25.1.0",
                "ANDROID_FIREBASE_FUNCTIONS_VERSION": "21.0.0",
                "ANDROID_FIREBASE_IID_VERSION": "21.1.0",
                "ANDROID_FIREBASE_INSTALLATIONS_VERSION": "18.0.0",
                "ANDROID_FIREBASE_CRASHLYTICS_VERSION": "19.1.0",
                "ANDROID_FIREBASE_CRASHLYTICS_NDK_VERSION": "19.1.0",
                "ANDROID_GSON_VERSION": "2.11.0",
                "ANDROID_FIREBASE_PERF_GRADLE_PLUGIN_VERSION": "1.4.2",
                "ANDROID_GRPC_OKHTTP": "1.68.0"
            }

Then I reinstalled the plugin cordova plugin rm cordova-plugin-firebasex --nosave && cordova plugin add cordova-plugin-firebasex --nosave

I also downloaded the google-services.json and GoogleService-Info.plist and replaced the downloaded ones with the ones in the project. After setting the right JDK and Gradle versions, I compiled the app.

However, the in app notifications are not working. I opened the app and went to the home screen. Then I simulated to send me a message, but no notification is popping up. I am not that familiar with Cordova/Android development and now questioning myself: What else could I've forgotten? Can anybody help?

[dpa99c]

Hi @torbentschechne, you can try building the example project and use its built-in messaging client to send a test message as described in the documentation.
Note that you'll need to change the package ID in config.xml to one which you have a google-services.json for, before adding the android platform.

[dpa99c]

Sorry, forgot to reply as been busy with other stuff.

So to clarify:

• legacy app build (cordova-android@9, firebasex@11) receives notifications
• new app build (cordova-android@13, FirebaseX@17) doesn't

That correct? If so, problem is app-side, not server-side

I may have time to take a look later this week if you still need me to

[torbentschechne]

Yep, exactly. But the new app build does receive notifications when I trigger a notification with your "sendMessage" script. I wanted to build the legacy app today from my mac (because the current app build of the legacy app is from another computer), as I wanted to see if it may be related to my mac. But here I struggle, because I always get

A problem occurred evaluating script.
> No usable Android build tools found. Highest 34.x installed version is 29.0.3; Recommended version is 34.0.0.

Independent on the <preference name="android-targetSdkVersion" value="29.0.3" /> or <preference name="android-compileSdkVersion" value="29.0.3" /> I also downgraded the cordova-cli to 11 and then to 10, but I have no idea why the process needs 34 ;-)

It would be great if you can take a look at it this week. How can I contact you besides here, because I would need some details from you (hourly rate etc.) to see if that makes sense. ;-)

[torbentschechne]

Hey @dpa99c,

I was able to build different versions today, and the update from

• cordova-android: 9.0.0 to "cordova-android": "^10.1.2"
• "cordova-plugin-firebasex": "^11.0.3-cli" to "cordova-plugin-firebasex": "^12.1.0",

<preference name="android-targetSdkVersion" value="30" />
<preference name="GradleVersion" value="6.9" />

worked fine. Also the update from worked fine and notifications were displayed on the home screen:

• "cordova-android": "^10.1.2" to "cordova-android": "^11.0.0"
• "cordova-plugin-firebasex": "^12.1.0" to "cordova-plugin-firebasex": "^14.0.0",

<preference name="android-targetSdkVersion" value="32" />

Then I updated

• "cordova-android": "^11.0.0" to "cordova-android": "^12.0.1"
• "cordova-plugin-firebasex": "^14.0.0" to "cordova-plugin-firebasex": "^15.0.0", (I also tried 16.0.0)

with

<preference name="android-targetSdkVersion" value="33" />
<preference name="GradleVersion" value="7.6.4" />
<preference name="GradlePluginGoogleServicesEnabled" value="true" />

and

<config-file target="AndroidManifest.xml" parent="/*">
    <uses-permission android:name="android.permission.POST_NOTIFICATIONS" />
</config-file>

and since then, I do not get Notifications anymore on an Android 13 and 15. So somewhere there must be the issue, but I don't see anything in the changelogs which can cause this or if I missed something in config.xml. So it would be really helpful if you could take a look at this in this week.

[dpa99c]

Hi Torben,

I had some urgent stuff today but now it's done.
Drop me a email on [email protected]
You can Google Chat with me there or we can work out another way. I'm in the UK so my timezone is GMT. Let's take it from there but I'm hopeful I can help you out.