Android / Firebase - 在GCM事件中解析时间戳时出错 - 空时间戳

时间:2018-06-11 10:32:11

标签: android firebase push-notification timestamp firebase-cloud-messaging

我正在构建一个可以接收推送通知的Android应用。我已经安装了Firebase云消息传递并且非常有效,因此我可以将以下有效负载发送到有效令牌并接收通知和数据。

使用网址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但似乎无法摆脱异常(和谷歌我可能,我找不到答案)。

如何传递时间戳让它停止抱怨?

编辑:这是我的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());
    }
}

提前致谢, 克里斯

8 个答案:

答案 0 :(得分:13)

即使notification显然是受支持的元素(根据Firebase网络文档),我摆脱异常的唯一方法是完全删除它,并仅使用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);
}

上面的链接中提供了更多详细信息,并且进行了大量处理,但至少有例外情况已经消失,我控制了通知。

答案 1 :(得分:0)

我遇到了同样的错误,我通过向有效负载添加ttl值来解决。

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

答案 2 :(得分:0)

我遇到了同样的问题,我只是在通知中设置了“ body”参数,而错误却消失了。

答案 3 :(得分:0)

我已将com.google.firebase:firebase-messaging更新为17.3.4,问题消失了。

答案 4 :(得分:0)

对我有用的东西

不仅将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

答案 5 :(得分:0)

在我的情况下,我的错误是“ 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>

答案 6 :(得分:0)

下面的格式(没有通知主体,也没有任何数组)为我修复了时间戳异常:

@Configuration

使用http://pushtry.com/

正常测试

我添加长“ eeee ...”的唯一原因是令牌的确切大小。

答案 7 :(得分:0)

替换

 "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");

    }