Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-23677] Android: GCM is eventually being deprecated for FCM

GitHub Issuen/a
TypeStory
PriorityHigh
StatusClosed
ResolutionDone
Resolution Date2018-04-17T13:31:45.000+0000
Affected Version/sn/a
Fix Version/sn/a
ComponentsAndroid
Labelscloudpush
ReporterAshraf Abu
AssigneeHans Knöchel
Created2016-07-25T13:52:45.000+0000
Updated2018-08-23T12:40:34.000+0000

Description

GCM [https://developers.google.com/cloud-messaging/faq] is going to be eventually deprecated for FCM [https://firebase.google.com/docs/cloud-messaging/] We should be prepared for this and look and identify what different projects/parts we need to update.

Attachments

FileDateSize
Screen_Shot_2016-10-19_at_3_31_33_PM.png2016-10-19T22:41:20.000+000064272
Screen_Shot_2016-10-19_at_3_36_09_PM.png2016-10-19T22:42:31.000+000030894
Screen_Shot_2016-10-19_at_3_36_44_PM.png2016-10-19T22:43:10.000+000019301
Screen_Shot_2016-10-19_at_3_38_23_PM.png2016-10-19T22:44:24.000+000046895
Screenshot_20161007-222415.png2016-10-07T16:30:15.000+000072777
Screen Shot 2016-10-07 at 10.22.24 PM.png2016-10-07T16:30:28.000+000051267
Screen Shot 2016-10-19 at 2.22.46 PM.png2016-10-19T08:32:46.000+000066747
Screen Shot 2016-10-19 at 2.30.10 PM.png2016-10-19T08:32:46.000+000067670

Comments

  1. Ashraf Abu 2016-07-25

    Related docs https://docs.appcelerator.com/arrowdb/latest/#!/api/PushNotifications http://docs.appcelerator.com/platform/latest/#!/api/Modules.CloudPush https://wiki.appcelerator.org/display/guides2/Configuring+push+services
  2. Aminul Islam 2016-10-07

    Hi [~cng] , I have tested FCM for android push notification. It's working as expected. https://developers.google.com/cloud-messaging/gcm#senderid [^Screenshot_20161007-222415.png] [^Screen Shot 2016-10-07 at 10.22.24 PM.png] We need to update our documentation. http://docs.appcelerator.com/platform/latest/#!/guide/Configuring_push_services
  3. Aminul Islam 2016-10-19

    Hi [~cng] and [~wkong], Workaround : 1. Create a sample test project. 2. Inculde sample code : [push](https://gist.github.com/aminulaust/3946931bf2221a3b0c0a34516603679b) , ti.cloud and ti.cloudpush 3. Now create a [firebase project :](https://console.firebase.google.com) 4. Copy *Project ID* from firebase. 5. Then copy Web API Key from firebase. !Screen Shot 2016-10-19 at 2.22.46 PM.png|thumbnail! 6. Finally configure your Appcelerator Dashboard with Project ID and Web API Key.!Screen Shot 2016-10-19 at 2.30.10 PM.png|thumbnail! 7. Now send push notification. Thanks
  4. Ingo Muschenetz 2016-10-19

    [~adesai] FYI. [~emerriman] Any chance you could confirm this?
  5. Aditya Desai 2016-10-19

    Question - Will the workaround suggested by [~aislam] work with a GCM id or FCM id?
  6. Ingo Muschenetz 2016-10-19

    I think we need to confirm that, which it would be great if [~emerriman] or [~wkong] could assist.
  7. Aminul Islam 2016-10-19

    Hi [~adesai], The workaround suggested by me was FCM id. Please take a look on firebase console screenshot : !Screen Shot 2016-10-19 at 2.22.46 PM.png|thumbnail!
  8. Aditya Desai 2016-10-19

    Thanks [~aislam]. If [~emerriman] can confirm this, then this may be a second alternative that we can suggest to the Enedis team as well. (Providing them with GCM keys created with our account being the first).
  9. Eric Merriman 2016-10-19

    Hello all, Confirmed. We have two ways that you can push using FCM: 1) The method described by [~aislam] above - this is the simplest. Simply create a new project in Firebase console, and use the "Server key (legacy token)" as "GCM API Key". Then add the "SenderID" to the "GCM Sender ID" and you can push. Of course you must follow the other steps listed to create a mobile app and create and register users, subscribe for push, etc.. 2) You can import a project into Firebase. Basically similar, the end result will be a new key is generated. The steps for this are: 2.1) Log into Firebase console 2.2) Choose "Import Google Project" from the project menu 2.3) Select "Project Settings" from the gear menu 2.4) Select the "CLOUD MESSAGING" Tab and use the key and sender ID as previously described If you return to the Older google API console, you will see two new keys are added to the project.
  10. John Goodland 2016-10-25

    Hi - Following the steps given by Aminul I get an error in the console whilst running (see below). This is a new project that has never had google play services enabled. Using Titanium SDK 5.5.1 GA and latest versions of ti.cloud and ti.cloudpush. [ERROR] : GooglePlayServicesUtil: The Google Play services resources were not found. Check your project configuration to ensure that the resources are included.
  11. Eric Merriman 2016-10-25

    Hello [~johngoodland] We have seen this as well, and after investigating it seems to be a Google bug. See: https://code.google.com/p/google-plus-platform/issues/detail?id=755 And on stack overflow: http://stackoverflow.com/questions/18068627/logcat-message-the-google-play-services-resources-were-not-found-check-your-pr Seems to be affecting many Google devs.
  12. Hans Knöchel 2018-04-17

    FCM is already supported since a while, see https://github.com/hansemannn/titanium-firebase-cloud-messaging for details (including support for both iOS and Android).
  13. Eric Merriman 2018-08-06

    Closed as completed. If this is in error, please reopen.
  14. Paul Ryan 2018-08-23

    Comment from above states that FCM is supported, but link is to a module maintained by Hans, not an Axway project. Does this have any official support from Axway other than Hans being on the Appcelerator development team and is this / has this code been rolled up into the core product?

JSON Source