New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why are people still using this outdated library? #2390
Comments
Probably legacy projects. |
Legacy project is one reason. An attempt to move to the FCM SDK 100% was made but to perform specific tasks like getDeliveredNotifications or removeDeliveredNotifications, it didn't suffice due to the creating background app handling requirement. We wish we could just utilize FCM since there is a lot of notification handling on our app, but until then, we're happy with what it offers. |
in FCM you are not able to show notification while receive them in foreground mode, you will need to use this one lib or other to show local notification |
I'm just curious because I only use Firebase Cloud Messaging (FCM) for Firebase notification messages, and it's already sufficient for sending remote push notifications. However, I see that many people are still using older versions of the React Native library. Can anyone explain why this might be the case?
The text was updated successfully, but these errors were encountered: