Android Timestamp Showing- 26-Jan-1970 in Some Android Device

[Akilramki]

If we Trigger the Multiple Schedule Notification from Firebase.We getting wrong TimeStamp from Some Android Device (26-1-1970) Currently Noted Devices: Samsung Galaxy’s , Nokia 4.1 , One Plus

Output :

{"collapseKey": "com.firebasetest", "data": {}, "from": "606529", "messageId": "0:16588086484686%3c41be66e66", "notification": {"android": [Object], "body": "HURRY!", "title": "Flat off"}, "sentTime": 2147483647, "ttl": 2419200}

sentTime": 2147483647

console.log(moment(2147483647).format('DD-MMM-YYYY')); // "26-Jan-1970"

[google-oss-bot]

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

[argzdev]

Hi @Akilramki, thanks for reporting. Could you answer some questions below:

1. Could you provide more details how to reproduce this issue, such as how many scheduled notifications to trigger before experiencing this behavior?
2. How are you retrieving the timestamp in your android devices?
3. Also any chance you could share code snippets or MCVE? It'll greatly help us investigating this further.

Thanks!

[Akilramki]

Hi @argzdev ,thanks for supporting

1.Could you provide more details how to reproduce this issue, such as how many scheduled notifications to trigger before experiencing this behavior? we trigger 3 schedule notifications to all devices, it’s scheduled on 1 ,2 and 3 PM, 1 o clock notification received to all device, 2 o clock schedule notification received to samsung device at 2.56 o clock, but we getting wrong sendTime timestamp (26-Jan-1970 02.01.23) from firebase.

2.How are you retrieving the timestamp in your android devices? { "image":"https://www.verywellmind.com/thmb/utB197ZQ8ZtUvjdNwB7B6x5dyRM=/1000x1000/smart/filters:no_upscale()/BestOnlineTherapyServices_V7-9d78415a9c5b4663a6b542acae6d5c61.jpg", "title":"Best Offer", "body":"HURRY UP", "sentTime":2147483647, "data":{ "message":"Test", "title":"Test" } }

[argzdev]

Thanks for the extra details, @Akilramki. Is this issue 100% consistent on these devices (Samsung Galaxy’s , Nokia 4.1 , One Plus)? Are you able to reproduce this issue on emulators? Is there a specific Android version this issue is present on?

[google-oss-bot]

Hey @Akilramki. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

[google-oss-bot]

Since there haven't been any recent updates here, I am going to close this issue.

@Akilramki if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this.