Firebase 云消息传递 sendToDevice 工作正常,但 sendMulticast 对于相同的令牌列表失败

本文介绍了Firebase 云消息传递 sendToDevice 工作正常,但 sendMulticast 对于相同的令牌列表失败的处理方法,对大家解决问题具有一定的参考价值

问题描述

对于某些类型的消息,我想通过存储在我的实时数据库中的 FIRToken 与主题来定位用户.我使用 async/await 加载这些令牌,然后决定是否要将通知发送到主题而不是较小的用户列表.数据加载代码按预期工作.但奇怪的是,如果我使用 .sendMulticast(payload),列表中所有令牌的通知都会失败.另一方面,如果我使用 .sendToDevice(adminFIRTokens, payload) 通知会成功发送给我的所有用户.现在我的列表有 2 个令牌,使用 sendMulticast 我有 2 次失败,使用 sendToDevice 我有 2 次成功.我错过了 sendMulticast 应该做什么的重点吗?根据 文档:发送消息到多个设备:

For certain types of messages, I want to target users by FIRTokens vs topic, which are stored in my real-time database. I load these tokens with async/await and then decide if I want to send notifications to a topic vs a smaller list of users. The data loading code works as expected. But what's odd is that if I use .sendMulticast(payload), the notifications fail for all tokens in the list. On the other hand if I use .sendToDevice(adminFIRTokens, payload) the notification goes successfully to all my users. Right now my list has 2 tokens and with sendMulticast I have 2 failures and with sendToDevice I have 2 successes. Am I missing the point of what sendMulticast is supposed to do? According to the docs: Send messages to multiple devices:

REST API 和 Admin FCM API 允许您将消息多播到设备注册令牌列表.每次调用最多可以指定 500 个设备注册令牌.

The REST API and the Admin FCM APIs allow you to multicast a message to a list of device registration tokens. You can specify up to 500 device registration tokens per invocation.

所以两者都应该在逻辑上起作用.那么为什么一个失败而另一个工作呢?实际上,使用 sendToDevice 我在响应中得到了一个 multicastId

So both should logically work. Then why does one fail and the other work? In fact with sendToDevice I get a multicastId in the response!

以下是一些控制台输出:

Here are some console outputs:

  1. sendToDevice:

Sent filtered message notification successfully: 
{ 
  results: 
    [ 
      { messageId: '0:1...45' }, 
      { messageId: '16...55' } 
    ], 
    canonicalRegistrationTokenCount: 0, 
    failureCount: 0, 
    successCount: 2, 
    multicastId: 3008...7000 
} 

  1. 发送多播:

List of tokens that caused failures: dJP03n-RC_Y:...MvPkTbuV,fDo1S8jPbCM:...2YETyXef 

发送通知的云端功能:

functions.database
  .ref("/discussionMessages/{autoId}/")
  .onCreate(async (snapshot, context) => {
    // console.log("Snapshot: ", snapshot);

    try {
      const groupsRef = admin.database().ref("people/groups");
      const adminUsersRef = groupsRef.child("admin");
      const filteredUsersRef = groupsRef.child("filtered");
      const filteredUsersSnapshot = await filteredUsersRef.once("value");
      const adminUsersSnapshot = await adminUsersRef.once("value");
      var adminUsersFIRTokens = {};
      var filteredUsersFIRTokens = {};

      if (filteredUsersSnapshot.exists()) {
        filteredUsersFIRTokens = filteredUsersSnapshot.val();
      }
      if (adminUsersSnapshot.exists()) {
        adminUsersFIRTokens = adminUsersSnapshot.val();
      }

      const topicName = "SpeechDrillDiscussions";
      const message = snapshot.val();
      const senderName = message.userName;
      const senderCountry = message.userCountryEmoji;
      const title = senderName + " " + senderCountry;
      const messageText = message.message;
      const messageTimestamp = message.messageTimestamp.toString();
      const messageID = message.hasOwnProperty("messageID")
        ? message.messageID
        : undefined;
      const senderEmailId = message.userEmailAddress;
      const senderUserName = getUserNameFromEmail(senderEmailId);

      const isSenderFiltered = filteredUsersFIRTokens.hasOwnProperty(
        senderUserName
      );

      var payload = {
        notification: {
          title: title,
          body: messageText,
          sound: "default",
        },
        data: {
          messageID: messageID,
          messageTimestamp: messageTimestamp,
        },
      };

      if (isSenderFiltered) {
        adminFIRTokens = Object.values(adminUsersFIRTokens);
        // payload.tokens = adminFIRTokens; //Needed for sendMulticast
        return (
          admin
            .messaging()
            .sendToDevice(adminFIRTokens, payload)
            // .sendMulticast(payload)
            .then(function (response) {
              if (response.failureCount === 0) {
                console.log(
                  "Sent filtered message notification successfully:",
                  response
                );
              } else {
                console.log(
                  "Sending filtered message notification failed for some tokens:",
                  response
                );
              }
              // if (response.failureCount > 0) {
              //   const failedTokens = [];
              //   response.responses.forEach((resp, idx) => {
              //     if (!resp.success) {
              //       failedTokens.push(adminFIRTokens[idx]);
              //     }
              //   });
              //   console.log(
              //     "List of tokens that caused failures: " + failedTokens
              //   );
              // }

              return true;
            })
        );
      } else {
        payload.topic = topicName;
        return admin
          .messaging()
          .send(payload)
          .then(function (response) {
            console.log("Notification sent successfully:", response);
            return true;
          });
      }
    } catch (error) {
      console.log("Notification sent failed:", error);
      return false;
    }
  });

推荐答案

我认为这是使用不同负载结构的问题.

I think it's an issue of using a different payload structure.

这是旧版本(没有 iOS 特定信息):

This is the old one (without iOS specific info):

var payload = {
    notification: {
      title: title,
      body: messageText,
      sound: "default",
    },
    data: {
      messageID: messageID,
      messageTimestamp: messageTimestamp,
    },
  };

而这是新版本(apns 有 iOS 特定信息)

Whereas this is the new version (apns has iOS specific info)

var payload = {
    notification: {
      title: title,
      body: messageText,
    },
    data: {
      messageID: messageID,
      messageTimestamp: messageTimestamp,
    },
    apns: {
      payload: {
        aps: {
          sound: "default",
        },
      },
    },
  };

使用新结构,sendsendMulticast 都可以正常工作.这将无法发送或给出错误,例如有效载荷中不支持 apns 密钥.

With the new structure, both send and sendMulticast are working properly. Which would fail to send or give errors like apns key is not supported in payload.

新功能:

functions.database
  .ref("/discussionMessages/{autoId}/")
  .onCreate(async (snapshot, context) => {
    // console.log("Snapshot: ", snapshot);

    try {
      const groupsRef = admin.database().ref("people/groups");
      const adminUsersRef = groupsRef.child("admin");
      const filteredUsersRef = groupsRef.child("filtered");
      const filteredUsersSnapshot = await filteredUsersRef.once("value");
      const adminUsersSnapshot = await adminUsersRef.once("value");
      var adminUsersFIRTokens = {};
      var filteredUsersFIRTokens = {};

      if (filteredUsersSnapshot.exists()) {
        filteredUsersFIRTokens = filteredUsersSnapshot.val();
      }
      if (adminUsersSnapshot.exists()) {
        adminUsersFIRTokens = adminUsersSnapshot.val();
      }

      // console.log(
      //   "Admin and Filtered Users: ",
      //   adminUsersFIRTokens,
      //   " ",
      //   filteredUsersFIRTokens
      // );

      const topicName = "SpeechDrillDiscussions";
      const message = snapshot.val();

      // console.log("Received new message: ", message);

      const senderName = message.userName;
      const senderCountry = message.userCountryEmoji;
      const title = senderName + " " + senderCountry;
      const messageText = message.message;
      const messageTimestamp = message.messageTimestamp.toString();
      const messageID = message.hasOwnProperty("messageID")
        ? message.messageID
        : undefined;
      const senderEmailId = message.userEmailAddress;
      const senderUserName = getUserNameFromEmail(senderEmailId);

      const isSenderFiltered = filteredUsersFIRTokens.hasOwnProperty(
        senderUserName
      );

      console.log(
        "Will attempt to send notification for message with message id: ",
        messageID
      );

      var payload = {
        notification: {
          title: title,
          body: messageText,
        },
        data: {
          messageID: messageID,
          messageTimestamp: messageTimestamp,
        },
        apns: {
          payload: {
            aps: {
              sound: "default",
            },
          },
        },
      };
      console.log("Is sender filtered? ", isSenderFiltered);

      if (isSenderFiltered) {
        adminFIRTokens = Object.values(adminUsersFIRTokens);
        console.log("Sending filtered notification with sendMulticast()");
        payload.tokens = adminFIRTokens; //Needed for sendMulticast
        return admin
          .messaging()
          .sendMulticast(payload)
          .then((response) => {
            console.log(
              "Sent filtered message (using sendMulticast) notification: ",
              JSON.stringify(response)
            );
            if (response.failureCount > 0) {
              const failedTokens = [];
              response.responses.forEach((resp, idx) => {
                if (!resp.success) {
                  failedTokens.push(adminFIRTokens[idx]);
                }
              });
              console.log(
                "List of tokens that caused failures: " + failedTokens
              );
            }
            return true;
          });
      } else {
        console.log("Sending topic message with send()");
        payload.topic = topicName;
        return admin
          .messaging()
          .send(payload)
          .then((response) => {
            console.log(
              "Sent topic message (using send) notification: ",
              JSON.stringify(response)
            );
            return true;
          });
      }
    } catch (error) {
      console.log("Notification sent failed:", error);
      return false;
    }
  });

这篇关于Firebase 云消息传递 sendToDevice 工作正常,但 sendMulticast 对于相同的令牌列表失败的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,WP2

admin_action_{$_REQUEST[‘action’]}

do_action( "admin_action_{$_REQUEST[‘action’]}" )动作钩子::在发送“Action”请求变量时激发。Action Hook: Fires when an ‘action’ request variable is sent.目录锚点:#说明#源码说明(Description)钩子名称的动态部分$_REQUEST['action']引用从GET或POST请求派生的操作。源码(Source)更新版本源码位置使用被使用2.6.0 wp-admin/admin.php:...

日期:2020-09-02 17:44:16 浏览:1166

admin_footer-{$GLOBALS[‘hook_suffix’]}

do_action( "admin_footer-{$GLOBALS[‘hook_suffix’]}", string $hook_suffix )操作挂钩:在默认页脚脚本之后打印脚本或数据。Action Hook: Print scripts or data after the default footer scripts.目录锚点:#说明#参数#源码说明(Description)钩子名的动态部分,$GLOBALS['hook_suffix']引用当前页的全局钩子后缀。参数(Parameters)参数类...

日期:2020-09-02 17:44:20 浏览:1067

customize_save_{$this->id_data[‘base’]}

do_action( "customize_save_{$this->id_data[‘base’]}", WP_Customize_Setting $this )动作钩子::在调用WP_Customize_Setting::save()方法时激发。Action Hook: Fires when the WP_Customize_Setting::save() method is called.目录锚点:#说明#参数#源码说明(Description)钩子名称的动态部分,$this->id_data...

日期:2020-08-15 15:47:24 浏览:804

customize_value_{$this->id_data[‘base’]}

apply_filters( "customize_value_{$this->id_data[‘base’]}", mixed $default )过滤器::过滤未作为主题模式或选项处理的自定义设置值。Filter Hook: Filter a Customize setting value not handled as a theme_mod or option.目录锚点:#说明#参数#源码说明(Description)钩子名称的动态部分,$this->id_date['base'],指的是设置...

日期:2020-08-15 15:47:24 浏览:895

get_comment_author_url

过滤钩子:过滤评论作者的URL。Filter Hook: Filters the comment author’s URL.目录锚点:#源码源码(Source)更新版本源码位置使用被使用 wp-includes/comment-template.php:32610...

日期:2020-08-10 23:06:14 浏览:929

network_admin_edit_{$_GET[‘action’]}

do_action( "network_admin_edit_{$_GET[‘action’]}" )操作挂钩:启动请求的处理程序操作。Action Hook: Fires the requested handler action.目录锚点:#说明#源码说明(Description)钩子名称的动态部分$u GET['action']引用请求的操作的名称。源码(Source)更新版本源码位置使用被使用3.1.0 wp-admin/network/edit.php:3600...

日期:2020-08-02 09:56:09 浏览:875

network_sites_updated_message_{$_GET[‘updated’]}

apply_filters( "network_sites_updated_message_{$_GET[‘updated’]}", string $msg )筛选器挂钩:在网络管理中筛选特定的非默认站点更新消息。Filter Hook: Filters a specific, non-default site-updated message in the Network admin.目录锚点:#说明#参数#源码说明(Description)钩子名称的动态部分$_GET['updated']引用了非默认的...

日期:2020-08-02 09:56:03 浏览:861

pre_wp_is_site_initialized

过滤器::过滤在访问数据库之前是否初始化站点的检查。Filter Hook: Filters the check for whether a site is initialized before the database is accessed.目录锚点:#源码源码(Source)更新版本源码位置使用被使用 wp-includes/ms-site.php:93910...

日期:2020-07-29 10:15:38 浏览:830

WordPress 的SEO 教学:如何在网站中加入关键字(Meta Keywords)与Meta 描述(Meta Description)?

你想在WordPress 中添加关键字和meta 描述吗?关键字和meta 描述使你能够提高网站的SEO。在本文中,我们将向你展示如何在WordPress 中正确添加关键字和meta 描述。为什么要在WordPress 中添加关键字和Meta 描述?关键字和说明让搜寻引擎更了解您的帖子和页面的内容。关键词是人们寻找您发布的内容时,可能会搜索的重要词语或片语。而Meta Description则是对你的页面和文章的简要描述。如果你想要了解更多关于中继标签的资讯,可以参考Google的说明。Meta 关键字和描...

日期:2020-10-03 21:18:25 浏览:1713

谷歌的SEO是什么

SEO (Search Engine Optimization)中文是搜寻引擎最佳化,意思近于「关键字自然排序」、「网站排名优化」。简言之,SEO是以搜索引擎(如Google、Bing)为曝光媒体的行销手法。例如搜寻「wordpress教学」,会看到本站的「WordPress教学:12个课程…」排行Google第一:关键字:wordpress教学、wordpress课程…若搜寻「网站架设」,则会看到另一个网页排名第1:关键字:网站架设、架站…以上两个网页,每月从搜寻引擎导入自然流量,达2万4千:每月「有机搜...

日期:2020-10-30 17:23:57 浏览:1306