Firebase 与 GCM 的向后兼容性 [英] Firebase Backward compatibility with GCM

查看:41
本文介绍了Firebase 与 GCM 的向后兼容性的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个项目通过第三方服务使用推送通知,该服务在后台使用 GCM.

我可以访问设备令牌,但我看不到将这些令牌导入 Firebase 云消息传递的方法.我知道对于 iOS,有一种方法可以导入 APNs 令牌,但我找不到在 Android 上执行此操作的方法.

有没有办法向 GCM 注册令牌发送推送通知或将它们导入 Firebase?

谢谢!

解决方案

同意@TimCasteljins,帖子有点不清楚,具体是你想在哪里将注册令牌导入FCM.p>

但是,如果您指的是在 FCM 中使用它们,则无需导入它们.正如 Tim Casteljins 在评论中提到的那样,您仍然可以使用 FCM 向这些令牌发送推送通知.只要你使用对应的 Sender ID 和 Server Key.

如果您打算使用 FCM,为什么不直接迁移到 FCM 完全?

I have a project that uses push notifications via a 3rd party service that uses GCM under the hood.

I have access to the device tokens, but I see no way to import those to the Firebase Cloud Messaging. I know that for iOS, there is a way to import APNs tokens, but I can't find a way to do that for Android.

Is there a way to send push notifications to GCM registered tokens or to import them to Firebase?

Thanks!

解决方案

Agreeing with @TimCasteljins, the post is a bit unclear, specifically where you want to import the registration tokens to FCM.

However, if you are referring to use them in FCM, there is no need to import them. As what was also mentioned by Tim Casteljins in the comments, you may still send push notifications to those tokens using FCM. So long as you use the corresponding Sender ID and Server Key.

If you are planning to use FCM, why not just Migrate to FCM completely?

这篇关于Firebase 与 GCM 的向后兼容性的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆