Firebase Cloud Messaging(FCM)诊断会告诉我们什么? [英] What does Firebase Cloud Messaging (FCM) Diagnostics tell us?

问题描述

我在Android应用中实施FCM取得了一定的成功，但是，控制将消息传递到设备所需的时间是一个挑战，并且会受到诸多因素的影响(FCM本身，覆盖范围，wifi/3g心跳，优先级，困倦，闲置等).

I've had reasonable success implementing FCM in my Android App, however getting control of how long it takes to get a message delivered to the device is proving a bit of a challenge and subject to a raft of factors (FCM itself, coverage, wifi/3g heartbeat, priority, sleepiness, idleness, etc, etc).

很明显，即时推送功能不错，但是一段时间内位于同一位置的同一设备上的同一版本的App会有很大的不同(有时我将其移动并且消息会通过) . FCM诊断非常有用，这里有一些示例；

Obviously, instant push-through is good, however there is quite a variation with the same version of the App on the same device sitting in exactly the same place over a period of time (sometimes I move it and messages burst through). FCM diagnostics are quite useful, and here are some examples;

消息0:1485 ...完美(盗窃)

MESSAGE 0:1485... PERFECT (BURGLAR APPREHENDED)

Current Status  Acknowledged
Collapse Key    n/a
TTL     2,419,200
TIME        CURRENT STATUS
Jan 31, 5:33 PM Device connected
Feb 1, 4:44 PM  Accepted
Feb 1, 4:44 PM  Delivered
Feb 1, 4:45 PM  Acknowledged

消息0:14860 ...速度变慢(电视带走盗窃声)

MESSAGE 0:14860... A BIT SLOWER (BURGLAR GOT AWAY WITH TV)

Current Status  Acknowledged
Collapse Key    n/a
TTL     2,419,200
TIME        CURRENT STATUS
Feb 3, 11:04 AM Device connected
Feb 3, 11:30 AM Accepted
Feb 3, 11:30 AM Delivered
Feb 3, 11:42 AM Acknowledged

消息0:1485 ...延迟(保时捷和电视消失了)

MESSAGE 0:1485... DELAYED (BURGLAR GOT AWAY WITH THE PORSCHE AND TV)

Current Status  Acknowledged
Collapse Key    n/a
TTL     2,419,200
TIME        CURRENT STATUS
Jan 25, 9:42 PM Device connected
Jan 26, 3:57 AM Accepted
Jan 26, 3:57 AM Delivered
Jan 26, 3:58 AM Device disconnected
Jan 26, 4:15 AM Device connected
Jan 26, 4:15 AM Sent on reconnect
Jan 26, 4:15 AM Acknowledged

因此，我可以看到发生了什么，但是我并没有多少运气来确定原因.在大多数日子里，它都很辉煌(已经有几个月了)，第二天却不是.

So, I can see what happened but I haven't had much luck establishing exactly why. Most days it's brilliant (and had been for months), the next day it isn't.

我的具体问题:是否可以更深入地访问FCM交易的状态??

My specific question: Is there any deeper access to status of the FCM transaction..?

我特别想知道我的优先级"参数是否真正通过并由FCM处理.如下所示，发送到FCM的典型json代码段

I'm particularly interested in finding out whether my "priority" parameter is actually getting through and being processed by FCM. Typical json snippet sent to FCM shown below

{"priority":"high","to":"dI3au0W8te...N7F","data":{"msgsndr":"ADMIN","msgtext":"URGENT: UNAUTHORISED ENTRY IN PROGRESS"}}

最受赞赏的任何提示

推荐答案

是否可以更深入地访问FCM交易的状态?

AFAIK，就是这样.诊断中没有可用的 deeper 详细信息.但是，如果您在后台遇到问题并需要进一步的帮助，建议您与 Firebase支持联系.

AFAIK, that's about it. No deeper details are available from the diagnostics. However if you're having trouble and need of further assistance on what's happening in the background, I suggest you contact Firebase Support.

对于priority，只要您正确声明，就可以肯定它会始终通过.

For the priority, fairly sure that it will always get through so long as you declared it properly.

这篇关于Firebase Cloud Messaging(FCM)诊断会告诉我们什么?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！