簡體   English   中英

Android / Firebase-在GCM事件中解析時間戳時出錯-空時間戳

[英]Android/Firebase - Error while parsing timestamp in GCM event - Null timestamp

我正在構建一個將接收推送通知的Android應用。 我已經安裝了Firebase Cloud Messaging,並且可以正常工作,因此我可以將以下有效負載發送到有效令牌,並接收通知和數據。

使用網址https://fcm.googleapis.com/fcm/send

{
 "to":"<valid-token>",
 "notification":{"body":"BODY TEXT","title":"TITLE TEXT","sound":"default"},
 "data":{"message":"This is some data"}
}

我的應用正確接收並可以處理它。

唯一的不足是調試中引發了以下異常:

Error while parsing timestamp in GCM event
    java.lang.NumberFormatException: Invalid int: "null"
        at java.lang.Integer.invalidInt(Integer.java:138)
        ...

它不會崩潰的應用程序,只是看起來不整潔。

我嘗試將timestamp項添加到主要有效負載,通知,數據中,還嘗試了諸如time變體,但似乎無法擺脫異常(和Google一樣,我可能找不到回答)。

我如何通過時間戳,以便它不再抱怨?

編輯:這是我的onMessageReceived方法,但是我認為異常在到達這里之前就拋出了

@Override
public void onMessageReceived(RemoteMessage remoteMessage) {
    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());
        //TODO Handle the data
    }

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

預先感謝克里斯

盡管notification顯然是受支持的元素(根據Firebase Web文檔),但我可以擺脫異常的唯一方法是將其完全刪除,並僅使用data部分,然后在我的應用中創建通知(而是而不是讓Firebase進行通知)。

我使用此網站計算出如何發出通知: https : //www.androidhive.info/2012/10/android-push-notifications-using-google-cloud-messaging-gcm-php-and-mysql/

我的通知現在如下所示:

    $fields = array("to" => "<valid-token>",
                    "data" => array("data"=>
                                        array(
                                            "message"=>"This is some data",
                                            "title"=>"This is the title",
                                            "is_background"=>false,
                                            "payload"=>array("my-data-item"=>"my-data-value"),
                                            "timestamp"=>date('Y-m-d G:i:s')
                                            )
                                    )
                    );
    ...
    <curl stuff here>
    ...
    curl_setopt($ch, CURLOPT_POSTFIELDS, json_encode($fields));

我的onMessageReceived看起來像這樣:

@Override
public void onMessageReceived(RemoteMessage remoteMessage) {
    Log.d(TAG, "From: " + remoteMessage.getFrom());

    // Check if message contains a data payload.
    if (remoteMessage.getData().size() > 0) {
        Log.e(TAG, "Data Payload: " + remoteMessage.getData().toString());

        try {
            JSONObject json = new JSONObject(remoteMessage.getData().toString());
            handleDataMessage(json);
        } catch (Exception e) {
            Log.e(TAG, "Exception: " + e.getMessage());
        }
    }
}

調用handleDataMessage如下所示:

private void handleDataMessage(JSONObject json) {
    Log.e(TAG, "push json: " + json.toString());

    try {
        JSONObject data = json.getJSONObject("data");

        String title = data.getString("title");
        String message = data.getString("message");
        boolean isBackground = data.getBoolean("is_background");
        String timestamp = data.getString("timestamp");
        JSONObject payload = data.getJSONObject("payload");

        // play notification sound
        NotificationUtils notificationUtils = new NotificationUtils(getApplicationContext());
        notificationUtils.playNotificationSound();

        if (!NotificationUtils.isBackgroundRunning(getApplicationContext())) {
            // app is in foreground, broadcast the push message
            Intent pushNotification = new Intent(ntcAppManager.PUSH_NOTIFICATION);
            pushNotification.putExtra("message", message);
            LocalBroadcastManager.getInstance(this).sendBroadcast(pushNotification);

        } else {
            // app is in background, show the notification in notification tray
            Intent resultIntent = new Intent(getApplicationContext(), MainActivity.class);
            resultIntent.putExtra("message", message);

            showNotificationMessage(getApplicationContext(), title, message, timestamp, resultIntent);
        }
    } catch (JSONException e) {
        Log.e(TAG, "Json Exception: " + e.getMessage());
    } catch (Exception e) {
        Log.e(TAG, "Exception: " + e.getMessage());
    }
}

然后調用showNotificationMessage

/**
 * Showing notification with text only
 */
private void showNotificationMessage(Context context, String title, String message, String timeStamp, Intent intent) {
    notificationUtils = new NotificationUtils(context);
    intent.setFlags(Intent.FLAG_ACTIVITY_NEW_TASK | Intent.FLAG_ACTIVITY_CLEAR_TASK);
    notificationUtils.showNotificationMessage(title, message, timeStamp, intent);
}

然后是notificationUtils.showNotificationMessage

public void showNotificationMessage(String title, String message, String timeStamp, Intent intent) {
    showNotificationMessage(title, message, timeStamp, intent, null);
}

public void showNotificationMessage(final String title, final String message, final String timeStamp, Intent intent, String imageUrl) {
    // Check for empty push message
    if (TextUtils.isEmpty(message))
        return;


    // notification icon
    final int icon = R.mipmap.ic_launcher;

    intent.setFlags(Intent.FLAG_ACTIVITY_CLEAR_TOP | Intent.FLAG_ACTIVITY_SINGLE_TOP);
    final PendingIntent resultPendingIntent =
            PendingIntent.getActivity(
                    mContext,
                    0,
                    intent,
                    PendingIntent.FLAG_CANCEL_CURRENT
            );

    final NotificationCompat.Builder mBuilder = new NotificationCompat.Builder(
            mContext);

    final Uri alarmSound = Uri.parse(ContentResolver.SCHEME_ANDROID_RESOURCE
            + "://" + mContext.getPackageName() + "/raw/notification");


    showSmallNotification(mBuilder, icon, title, message, timeStamp, resultPendingIntent, alarmSound);
    playNotificationSound();

}

private void showSmallNotification(NotificationCompat.Builder mBuilder, int icon, String title, String message, String timeStamp, PendingIntent resultPendingIntent, Uri alarmSound) {

    NotificationCompat.InboxStyle inboxStyle = new NotificationCompat.InboxStyle();

    inboxStyle.addLine(message);

    Notification notification;
    notification = mBuilder.setSmallIcon(icon).setTicker(title).setWhen(0)
            .setAutoCancel(true)
            .setContentTitle(title)
            .setContentIntent(resultPendingIntent)
            .setSound(alarmSound)
            .setStyle(inboxStyle)
            .setWhen(getTimeMilliSec(timeStamp))
            .setSmallIcon(R.mipmap.ic_launcher)
            .setLargeIcon(BitmapFactory.decodeResource(mContext.getResources(), icon))
            .setContentText(message)
            .build();

    NotificationManager notificationManager = (NotificationManager) mContext.getSystemService(Context.NOTIFICATION_SERVICE);
    notificationManager.notify(ntcAppManager.NOTIFICATION_ID, notification);
}

在上面的鏈接中有更多詳細信息,需要進行很多處理,但是至少異常已消失,並且我可以控制通知。

我已經將com.google.firebase:firebase-messaging更新為17.3.4,問題消失了。

我遇到了同樣的錯誤,我通過向有效負載添加ttl值來解決。

{
   "to":"<valid-token>",
   "notification":{"body":"BODY TEXT","title":"TITLE TEXT","sound":"default"},
   "data":{"message":"This is some data"},
   "ttl": 3600
}

我遇到了同樣的問題,我只是在通知中設置了“ body”參數,而錯誤卻消失了。

對我有用的是:

不僅將firebase-messaging升級, firebase-messaging所有Firebase庫升級到最新版本。 android/app/build.gradle

dependencies {
    implementation "com.google.firebase:firebase-core:16.0.0"  // upgraded
    implementation "com.google.firebase:firebase-analytics:16.0.0"  // upgraded
    implementation 'com.google.firebase:firebase-messaging:17.3.4'  // upgraded

    // ...

    implementation "com.google.firebase:firebase-invites:16.0.0"  // upgraded

    // ...
}

並非所有版本都為17.x版

下面的格式(沒有通知正文,也沒有任何數組)為我修復了時間戳異常:

{
  "to": "eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee",
  "data":  {
      "message": "message",
      "title": "hello",
  }
}

經過http://pushtry.com/的良好測試

我包含長“ eeee ...”的唯一原因是令牌的確切大小。

更換

 "notification" : {
    "title" : "title !",
    "body" : "body !",
    "sound" : "default"
  },
  "condition" : "'xxx' in topics",
  "priority" : "high",
  "data" : {
....

通過(刪除通知):

{
  "condition" : "'xxxx' in topics",
  "priority" : "high",
  "data" : {
    "title" : "title ! ",
     "body" : "BODY",
 ......
}

然后在您的代碼上:替換:

 @Override
        public void onMessageReceived(RemoteMessage remoteMessage) { 
           remoteMessage.getNotification().getTitle();
           remoteMessage.getNotification().getBody();

        }

通過

@Override
    public void onMessageReceived(RemoteMessage remoteMessage) { 
       remoteMessage.getData().get("title");
       remoteMessage.getData().get("body");

    }

就我而言,我的錯誤是“ AndrodManifest.xml”

我錯過了一項服務(實際上Android Studio的firebase助手未獲得我的許可。:))

原版的

<service android:name=".fcm.MyFirebaseInstanceIDService">
        <intent-filter>
            <action android:name="com.google.firebase.INSTANCE_ID_EVENT" />
        </intent-filter>
    </service>
</application>

    <service android:name=".fcm.MyFirebaseInstanceIDService">
        <intent-filter>
            <action android:name="com.google.firebase.INSTANCE_ID_EVENT" />
        </intent-filter>
    </service>
    <service android:name=".fcm.MyFirebaseMessagingService">
        <intent-filter>
            <action android:name="com.google.firebase.MESSAGING_EVENT" />
        </intent-filter>
    </service>
</application>

暫無
暫無

聲明:本站的技術帖子網頁,遵循CC BY-SA 4.0協議,如果您需要轉載,請注明本站網址或者原文地址。任何問題請咨詢:yoyou2525@163.com.

 
粵ICP備18138465號  © 2020-2024 STACKOOM.COM