[GH-ISSUE #1112] Android app: Timestamp ignored in notifications #782

New issue

Closed

opened 2026-05-07 00:27:27 +02:00 by BreizhHardware · 1 comment

BreizhHardware commented

2026-05-07 00:27:27 +02:00

Owner

Originally created by @voruti on GitHub (May 22, 2024).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1112

🐞 Describe the bug
While setting up the Android app & integrations with it on my smartphone, I noticed that the timestamp isn't set for Android notifications from the ntfy app.
In my case (see screenshot below) I receive the notification in Automate (similar to Tasker) via the broadcast intent and show it as Android notification. When creating the Android notification I set the timestamp to be the one I receive from the broadcasts extras.
The problem becomes noticeable when notifications from ntfy get delayed (because of lack of internet connection or similar). After receiving the (delayed) notification, ntfy creates an Android notification with the current timestamp - not with the one that is attached to the ntfy notification - while my Automate integration creates an Android notification with the correct timestamp of the moment the ntfy notification originally was sent.

💻 Components impacted
Android app

💡 Screenshots and/or logs

🔮 Additional context
In the screenshot above I cut off the internet connection (wifi) to my smartphone, sent the test message "triggered" to the topic, waited 3 minutes and then turned wifi back on. Both notifications appeared immediately, but they show different timestamps.

Originally created by @voruti on GitHub (May 22, 2024). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1112 :lady_beetle: **Describe the bug** While setting up the Android app & integrations with it on my smartphone, I noticed that the timestamp isn't set for Android notifications from the ntfy app. In my case (see screenshot below) I receive the notification in [Automate](https://play.google.com/store/apps/details?id=com.llamalab.automate) (similar to [Tasker](https://play.google.com/store/apps/details?id=net.dinglisch.android.taskerm)) via the broadcast intent and show it as Android notification. When creating the Android notification I set the timestamp to be the one I receive from the broadcasts extras. The problem becomes noticeable when notifications from ntfy get delayed (because of lack of internet connection or similar). After receiving the (delayed) notification, ntfy creates an Android notification with the current timestamp - not with the one that is attached to the ntfy notification - while my Automate integration creates an Android notification with the correct timestamp of the moment the ntfy notification originally was sent. :computer: **Components impacted** Android app :bulb: **Screenshots and/or logs** ![](https://github.com/binwiederhier/ntfy/assets/45130096/eb748b40-b57f-4369-9bcd-21d6611875bc) :crystal_ball: **Additional context** In the screenshot above I cut off the internet connection (wifi) to my smartphone, sent the test message "triggered" to the topic, waited 3 minutes and then turned wifi back on. Both notifications appeared immediately, but they show different timestamps.

BreizhHardware

2026-05-07 00:27:27 +02:00

closed this issue
added the
🪲 bug

android-app
labels

BreizhHardware commented

2026-05-07 00:27:28 +02:00

Author

Owner

@binwiederhier commented on GitHub (Feb 4, 2026):

Done in github.com/binwiederhier/ntfy-android@6c4f5e8810

@binwiederhier commented on GitHub (Feb 4, 2026): Done in https://github.com/binwiederhier/ntfy-android/commit/6c4f5e881015adf8a6986947c1ae181045c75aac

BreizhHardware referenced this issue

2026-05-07 01:02:01 +02:00

[PR #782] [MERGED] Fix: refresh web push pref on standalone change #1419