GCM 到 FCM 迁移离子 v1
GCM to FCM migration ionic v1
我有一个 ionic v1 应用程序。我已经阅读并重新阅读了有关 GCM 到 FCM 迁移的信息，但我仍然不能 100% 确定我的（未迁移的）应用程序在 4 月 11 日之后仍会收到推送通知。我已将服务器迁移到 FCM。我相信该应用程序应该仍然可以使用，但需要对其进行验证。
基于此link，您需要更新客户端代码并迁移到 FCM。
Existing deployed client-side apps receiving notifications will continue to work for the foreseeable future. But from mid-april, you:
- won't be able to compile code using the old client-side APIs on a newer SDK/Google Play Services anymore
- won't be able to call the GCM REST API to send messages anymore
To compile against the new SDK/Google Play Services, you will need to make changes to your client app to migrate to Firebase Cloud Messaging from GCM. This involves changes to the build.gradle, to AndroidManifest.xml and to your code, as described in Migrate a GCM Client App for Android to Firebase Cloud Messaging.
But aside from those changes, you don't need to get new tokens for all users. The existing tokens from GCM will continue to work.
我有一个 ionic v1 应用程序。我已经阅读并重新阅读了有关 GCM 到 FCM 迁移的信息，但我仍然不能 100% 确定我的（未迁移的）应用程序在 4 月 11 日之后仍会收到推送通知。我已将服务器迁移到 FCM。我相信该应用程序应该仍然可以使用，但需要对其进行验证。
基于此link，您需要更新客户端代码并迁移到 FCM。
Existing deployed client-side apps receiving notifications will continue to work for the foreseeable future. But from mid-april, you:
- won't be able to compile code using the old client-side APIs on a newer SDK/Google Play Services anymore
- won't be able to call the GCM REST API to send messages anymore
To compile against the new SDK/Google Play Services, you will need to make changes to your client app to migrate to Firebase Cloud Messaging from GCM. This involves changes to the
build.gradle, toAndroidManifest.xmland to your code, as described in Migrate a GCM Client App for Android to Firebase Cloud Messaging.But aside from those changes, you don't need to get new tokens for all users. The existing tokens from GCM will continue to work.