[TIMOB-25404] Upgrade titanium module for android push notifications to use google firebase sdk
| GitHub Issue | n/a |
|---|---|
| Type | New Feature |
| Priority | None |
| Status | Open |
| Resolution | Unresolved |
| Affected Version/s | n/a |
| Fix Version/s | n/a |
| Components | n/a |
| Labels | n/a |
| Reporter | Wei Kong |
| Assignee | Unknown |
| Created | 2017-10-17T18:42:27.000+0000 |
| Updated | 2019-04-02T20:06:39.000+0000 |
Description
Based on this https://developers.google.com/cloud-messaging/faq, gcm sdk will no longer receive any new features. It is recommended to upgrade to firebase sdk.
The differences between GCM and FCM setup is outlined here .
https://developers.google.com/cloud-messaging/android/android-migrate-fcm
Since there is are differences in how devices subscribe/register/unregister for Push Notifications, the Titanium Module for Push Notifications should be enhanced to support developers using FCM to send push notifications to Titanium Apps in Android.
Relevant ticket. https://techweb.axway.com/jira/browse/MBAAS-4896
[~wkong] We don't expect developers will upgrade to the new module immediately, is there a fall back mechanism to use GCM for apps using the older version of the module. It would be good to know the test results that you were talking about -- with and without the changes in the module.