I finished my first advanced @expo Module, and I had to handle Android background notifications in it. However, we can only register a single FirebaseMessagingService subclass. So here is my solution to keep using expo-notifications (because they are a god-sent): - Add expo-notifications as a dependency in my project (package.json AND build.gradle) - Remove ExpoFirebaseMessagingService from the merged manifest using tools:node="remove" in my manifest - Subclass ExpoFirebaseMessagingService, delegating it all notifications I do not want to handle myself, and picking and handling those I care about - Declare my subclass in the manifest If there is a better way to do it, or one that also works on iOS (keeping expo-notifications and still register my own delegate), I'd love for you to share it!

Discover #LifecycleService tips for #FirebaseMessagingService with #Kotlin coroutines. By @github_skydoves droidcon.com/2024/09/24/expl…

Thanks, @KotlinWeekly for featuring my recent article, 'Exploring Lifecycle-Aware Service and FirebaseMessagingService on Android', this week! You’ll explore LifecycleService and how to apply similar approaches to FirebaseMessagingService. proandroiddev.com/exploring-…

Exploring Lifecycle-Aware Service and FirebaseMessagingService on Android. By @github_skydoves #AndroidDev proandroiddev.com/exploring-…

This is a feature that I contributed to skydoves' library before I started X. I'm honored that he wrote an article explaining it. Thanks @github_skydoves I highly recommend using this library if you need to manage lifecycle-coupled tasks within your FirebaseMessagingService!

I just published a new article, 'Exploring Lifecycle-Aware Service and FirebaseMessagingService on Android'. In this article, you’ll explore LifecycleService and how you can apply the approaches to manage task lifecycle in your FirebaseMessagingService. skydoves.medium.com/explorin…

Firebase Android KTX 0.2.0 has been released. It contains a new package, `Firebase Messaging Lifecycle KTX`, which allows you to implement a a lifecycle-aware version of FirebaseMessagingService. github.com/skydoves/firebase…

More reliable FCM background messages on Android 🔥 The Cloud Messaging SDK for Android now keeps the FirebaseMessagingService active for up to 20 seconds, so your code has a better chance of handling background messages. Watch @puf break it down → goo.gle/3QVljUK

When using Firebase FCM in Android , the onMessageReceived() function within the FirebaseMessagingService class is only called if the message is received when the app is in foreground. On the background the onMessageReceived() is not called but the notifcations are sent to ...

💡So if for some reason you can’t yet target Android 13, at least make sure that you’re not creating a Notification Channel in your FirebaseMessagingService. Consider creating it on app startup. (6/7) developer.android.com/develo…

Most common FCM implementations only create a Notification Channel in their FirebaseMessagingService, which means it might take a while for users to see the permission request in that case. (5/7)

PendingIntentなんてFirebaseMessagingServiceの中でしか作ってないから余裕だぜ〜とおもってたらデバイスのFirmwareアップデートにつかってるNordic SemiconductorのDFUライブラリがPendingIntentつかってました、ありがとうございました。

Firebase Cloud Messaging version 20.0.0 で nullability annotation が充実して FirebaseMessagingService の onNewToken() の引数が non-null になったのか。よいね。

今日はFirebaseMessagingServiceと和解しかけた(してない)

Question for the @Firebase team. Anyone knows how often firebase updates the token of FirebaseMessagingService ??

今日はFCMのアプデしてた。FirebaseInstanceIdServiceってdeprecatedになったのか。FirebaseMessagingServiceにまとまってスッキリしたなー。

あれ..FirebaseMessagingServiceがpublic abstract fun zzd(p0: Intent!)を実装しろやとか言ってくる...

FirebaseMessagingServiceを継承すればGCMと同じようなNotification作成ができる。 #shibuya_apk