FCM 不可靠的消息传递，有一些消息传递延迟 [重复]

Posted 2023-02-24

【中文标题】FCM 不可靠的消息传递，有一些消息传递延迟 [重复]

【英文标题】：FCM unreliable messaging with some messaging delays [duplicate]

【发布时间】：2016-08-28 10:45:49

【问题描述】：

我的问题是，当我使用从 Firebase 获得的 InstanceID 从服务器向特定客户端发送消息时，我并不总是收到消息。 大多数时候我什至没有收到消息，有时我会在 5-10 分钟后收到一条消息到 android 设备。

public class MessagingService extends FirebaseMessagingService

public static final String SERVICE_RESULT = "at.ideafactory.spotted.Firebase.REQUEST_PROCESSED";
public static final String SERVICE_MESSAGE = "at.ideafactory.spotted.Firebase.REQUEST_MSG";

private LocalBroadcastManager broadcastManager = LocalBroadcastManager.getInstance(this);

@Override
public void onMessageReceived(RemoteMessage remoteMessage)
    notifyMainActivity(remoteMessage.getData().get("obj_location"));



public void notifyMainActivity(String data)
    if(data != null && data.length() != 0 && !data.equals(""))
        Intent intent = new Intent(SERVICE_RESULT);
        intent.putExtra(SERVICE_MESSAGE, data);
        broadcastManager.sendBroadcast(intent);
    

谁能帮我解决我的问题？ 你知道是否可以在设备上检查通知是否可用？

亲切的问候

【问题讨论】：

您还应该在标题中添加“和一些消息延迟”。

建议标题：FCM 不可靠的消息传递，有一些延迟。

这很可能是由unrealistic heartbeat intervals in GCM/FCM 引起的。考虑Pushy，这是一种可靠的推送通知服务，它极大地提高了Android 上的通知速度和可靠性。全面披露 - 我在 Pushy 工作。

【参考方案1】：

您能否使用 Firebase here 提供的代码进行测试，看看您在发送消息时是否收到通知？ 当我用这段代码测试 FCM 时，我立即收到了通知。问题可能出在您的服务器端或应用的其他部分。

/**
 * Copyright 2016 Google Inc. All Rights Reserved.
 *
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 * http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */

package com.google.firebase.quickstart.fcm;

import android.app.NotificationManager;
import android.app.PendingIntent;
import android.content.Context;
import android.content.Intent;
import android.media.RingtoneManager;
import android.net.Uri;
import android.support.v4.app.NotificationCompat;
import android.util.Log;

import com.google.firebase.messaging.FirebaseMessagingService;
import com.google.firebase.messaging.RemoteMessage;

public class MyFirebaseMessagingService extends FirebaseMessagingService 

    private static final String TAG = "MyFirebaseMsgService";

    /**
     * Called when message is received.
     *
     * @param remoteMessage Object representing the message received from Firebase Cloud Messaging.
     */
    // [START receive_message]
    @Override
    public void onMessageReceived(RemoteMessage remoteMessage) 
        // [START_EXCLUDE]
        // There are two types of messages data messages and notification messages. Data messages are handled
        // here in onMessageReceived whether the app is in the foreground or background. Data messages are the type
        // traditionally used with GCM. Notification messages are only received here in onMessageReceived when the app
        // is in the foreground. When the app is in the background an automatically generated notification is displayed.
        // When the user taps on the notification they are returned to the app. Messages containing both notification
        // and data payloads are treated as notification messages. The Firebase console always sends notification
        // messages. For more see: https://firebase.google.com/docs/cloud-messaging/concept-options
        // [END_EXCLUDE]

        // TODO(developer): Handle FCM messages here.
        Log.d(TAG, "From: " + remoteMessage.getFrom());

        // Check if message contains a data payload.
        if (remoteMessage.getData().size() > 0) 
            Log.d(TAG, "Message data payload: " + remoteMessage.getData());
        

        // Check if message contains a notification payload.
        if (remoteMessage.getNotification() != null) 
            Log.d(TAG, "Message Notification Body: " + remoteMessage.getNotification().getBody());
        

        // Also if you intend on generating your own notifications as a result of a received FCM
        // message, here is where that should be initiated. See sendNotification method below.
    
    // [END receive_message]

    /**
     * Create and show a simple notification containing the received FCM message.
     *
     * @param messageBody FCM message body received.
     */
    private void sendNotification(String messageBody) 
        Intent intent = new Intent(this, MainActivity.class);
        intent.addFlags(Intent.FLAG_ACTIVITY_CLEAR_TOP);
        PendingIntent pendingIntent = PendingIntent.getActivity(this, 0 /* Request code */, intent,
                PendingIntent.FLAG_ONE_SHOT);

        Uri defaultSoundUri= RingtoneManager.getDefaultUri(RingtoneManager.TYPE_NOTIFICATION);
        NotificationCompat.Builder notificationBuilder = new NotificationCompat.Builder(this)
                .setSmallIcon(R.drawable.ic_stat_ic_notification)
                .setContentTitle("FCM Message")
                .setContentText(messageBody)
                .setAutoCancel(true)
                .setSound(defaultSoundUri)
                .setContentIntent(pendingIntent);

        NotificationManager notificationManager =
                (NotificationManager) getSystemService(Context.NOTIFICATION_SERVICE);

        notificationManager.notify(0 /* ID of notification */, notificationBuilder.build());
    

【参考方案2】：

现在我注意到我从应用服务器发送到 FCM 服务的 JSON 对象中有一个“优先级”属性。

默认值：“优先级”：“正常”

我已将“优先级”设置为“高”，现在我可以在设备上实时接收服务器发送的消息。

【讨论】：

更新谷歌播放服务后。 fcm 是不现实的。甚至已经将优先级设置为高并延迟 0