-
-
Notifications
You must be signed in to change notification settings - Fork 3
Question: Compatibility with nativescript/firebase? #3
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
Comments
@lambourn this plugin does not use firebase at all! It only uses platform push notifications system. |
@farfromrefug ok - so it just needs the Firebase Messaging dependency on Android (include.gradle and PushMessagingService) to access the native messaging tier which always uses FCM on Android, right? |
@lambourn The thing is more that this plugin does not handle the registration of the device to your firebase instance. So your firebase instance does not know which device to send the notification to. |
Hi @farfromrefug - ok, makes sense. We use the same approach already: we combine the token with a registration ID on the server side. Previously we used Eddie's nativescript-firebase-plugin which allows to use both: Firebase Crashlytics & Analytics & "Firebase-less" Push Notifications. Now as we moved to the rewritten nativescript/firebase plugin, we need a replacement for the "Firebase-less" Push Notifications and will give your plugin a try. Will ping back here, maybe raise a PR to synchronize the Firebase Messaging version in the include.gradle /and remove that pesky jcenter() repo entry) |
Hi, does this plug-in work with nativescript 8 |
@pjabang1 yes it does |
@farfromrefug do you happen to know if your push plugin is compatible with the rewritten https://github.com./NativeScript/firebase plugin - which is missing the non-firebase messaging that was originally part of Eddie's version, see NativeScript/firebase#7
I suspect the firebase versions do not match but I haven't tried it yet.
The question might sound silly, but we have a use case were we use Firebase Analytics and Firebase Crashlytics but non-Firebase Push Messaging.
The text was updated successfully, but these errors were encountered: