<legend id='LeTdV'><style id='LeTdV'><dir id='LeTdV'><q id='LeTdV'></q></dir></style></legend>
        <i id='LeTdV'><tr id='LeTdV'><dt id='LeTdV'><q id='LeTdV'><span id='LeTdV'><b id='LeTdV'><form id='LeTdV'><ins id='LeTdV'></ins><ul id='LeTdV'></ul><sub id='LeTdV'></sub></form><legend id='LeTdV'></legend><bdo id='LeTdV'><pre id='LeTdV'><center id='LeTdV'></center></pre></bdo></b><th id='LeTdV'></th></span></q></dt></tr></i><div id='LeTdV'><tfoot id='LeTdV'></tfoot><dl id='LeTdV'><fieldset id='LeTdV'></fieldset></dl></div>

        <small id='LeTdV'></small><noframes id='LeTdV'>

        <tfoot id='LeTdV'></tfoot>

          <bdo id='LeTdV'></bdo><ul id='LeTdV'></ul>

        Firebase 与 GCM 的向后兼容性

        Firebase Backward compatibility with GCM(Firebase 与 GCM 的向后兼容性)
          • <small id='eDJad'></small><noframes id='eDJad'>

          • <tfoot id='eDJad'></tfoot>
              <bdo id='eDJad'></bdo><ul id='eDJad'></ul>

                <i id='eDJad'><tr id='eDJad'><dt id='eDJad'><q id='eDJad'><span id='eDJad'><b id='eDJad'><form id='eDJad'><ins id='eDJad'></ins><ul id='eDJad'></ul><sub id='eDJad'></sub></form><legend id='eDJad'></legend><bdo id='eDJad'><pre id='eDJad'><center id='eDJad'></center></pre></bdo></b><th id='eDJad'></th></span></q></dt></tr></i><div id='eDJad'><tfoot id='eDJad'></tfoot><dl id='eDJad'><fieldset id='eDJad'></fieldset></dl></div>
                  <legend id='eDJad'><style id='eDJad'><dir id='eDJad'><q id='eDJad'></q></dir></style></legend>
                    <tbody id='eDJad'></tbody>
                  本文介绍了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 的向后兼容性的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持跟版网!

                  本站部分内容来源互联网,如果有图片或者内容侵犯了您的权益,请联系我们,我们会在确认后第一时间进行删除!

                  相关文档推荐

                  When does a FCM token expire?(FCM 令牌何时到期?)
                  Firebase Cloud Messaging (FCM) - Launch Activity when user clicks the notification with extras(Firebase Cloud Messaging (FCM) - 当用户点击带有附加功能的通知时启动活动)
                  Implement Firebase inside of a Library(在库中实现 Firebase)
                  Receiving the FCM notifications multiple times on Nougat(在 Nougat 上多次接收 FCM 通知)
                  Push Notifications are delivered but didReceiveRemoteNotification is never called Swift(推送通知已交付,但 didReceiveRemoteNotification 从未被称为 Swift)
                  Firebase FCM MismatchSenderID(Firebase FCM 不匹配SenderID)
                      <bdo id='m2EOx'></bdo><ul id='m2EOx'></ul>
                      1. <tfoot id='m2EOx'></tfoot>

                          <i id='m2EOx'><tr id='m2EOx'><dt id='m2EOx'><q id='m2EOx'><span id='m2EOx'><b id='m2EOx'><form id='m2EOx'><ins id='m2EOx'></ins><ul id='m2EOx'></ul><sub id='m2EOx'></sub></form><legend id='m2EOx'></legend><bdo id='m2EOx'><pre id='m2EOx'><center id='m2EOx'></center></pre></bdo></b><th id='m2EOx'></th></span></q></dt></tr></i><div id='m2EOx'><tfoot id='m2EOx'></tfoot><dl id='m2EOx'><fieldset id='m2EOx'></fieldset></dl></div>
                        1. <small id='m2EOx'></small><noframes id='m2EOx'>

                            <tbody id='m2EOx'></tbody>
                            <legend id='m2EOx'><style id='m2EOx'><dir id='m2EOx'><q id='m2EOx'></q></dir></style></legend>