-
Notifications
You must be signed in to change notification settings - Fork 43
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
Firebase support - internal dependencies #83
Comments
We really need to work this out. I have no knowledge on that part of the module. Do you know who started the implementation of it on Android? @jvandijk Jeroen, maybe you know something or someone? |
I haven't tested this, but as far as I can see this has been completely abstracted away by the OneSignal library itself. This still supports both GCM & FCM, it's just up to you to configure one in the OneSignal user interface and only use the OneSignal app id. In the past you also had to put in a Google project number, but is now fetched automatically to support both GCM & FCM. |
Hey hello @jvandijk. Perhaps, I am wrong, but what about the following; not sure, but this module seems that it is not using FCM SDK, but according to Google we should remove / update the following:
I noticed part of the above code in the following link: Reference: https://developers.google.com/cloud-messaging/android/android-migrate-fcm |
Got it to work:
removed all stuffs from manifest like @antonioduran says and now I get inside the console
Unfortunately I think that we cannot completely remove GCM because is built in inside ti.playservices module. |
In case you would like to test it with FCM, here is the module. |
Hello. As you know google will be deprecated GCM in April 11th, so this module is working with GCM, but does anybody know whether this module will have support for firebase? I mean to update all the internal dependencies of the module to firebase.
Thanks.
The text was updated successfully, but these errors were encountered: