As of April 12th, you must go to Progress SupportLink to create new support cases or to access existing cases. Please, bookmark the SupportLink URL and use the new portal to contact the support team.
Google extended the deprecation deadline for GCM from April 11th to May 29th - https://developers.google.com/cloud-messaging/android/android-migrate-fcm
As of April 10, 2018, Google has deprecated GCM. The GCM server and client APIs are deprecated and will be removed as soon as May 29, 2019.
On April 11, Google Cloud Messaging (GCM) is being decommissioned by Google in favour of Firebase Cloud Messaging (FCM). This will affect all users of Android push. This has been known for some time, and in our documentation (https://devcenter.kinvey.com/android/guides/push), we have been instructing users to set up push using the Firebase Console (https://console.firebase.google.com/). Kinvey is compatible with Firebase, and will continue to work after the GCM decommissioning date, which is April 11, 2019.
Existing apps that use GCM will continue to be backwards-compatible with Firebase. However, a requirement of this backwards compatibility as defined by Google is that developers add Firebase to their existing GCM project in the Google Console if it does not already exist. This should require only a few steps by your developer on the Firebase Console. If your Google project already has a Firebase project added to it, you do not need to take any action right now. If you don't have a Firebase project added, you need to add it before Thursday, April 11, 2019. Failure to do so will result in your Android users failing to receive push notifications after the above date.
For reference, the official Google documentation for migration can be found here: https://developers.google.com/cloud-messaging/android/android-migrate-fcm. Currently, only step 1 is required in order to insure that android users continue to receive push notifications.
Please contact Kinvey support if you have any questions.
2 people like this