mirror of
https://github.com/binwiederhier/ntfy.git
synced 2026-05-09 16:35:53 +02:00
[GH-ISSUE #997] Android app: Irrelevant or unknown message. Discarding. #697
Labels
No labels
ai-generated
android-app
android-app
android-app
🪲 bug
build
build
dependencies
docs
enhancement
enhancement
🔥 HOT
in-progress 🏃
ios
prio:low
prio:low
pull-request
question
🔒 security
server
server
unified-push
web-app
website
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ntfy#697
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @pcrockett on GitHub (Jan 3, 2024).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/997
🐞 Describe the bug
I'm using ntfy.sh to set up the UnifiedPush flavor of Molly on /e/OS (fork of LineageOS).
I've already gotten it working perfectly on a different GrapheneOS device. However when following the exact same setup on the /e/OS device, I get
Irrelevant or unknown message. Discarding.messages in the ntfy logs (below).These "irrelevant or unknown messages" happen when the phone should receive a push message.
The Molly app obviously never receives the notification.
💻 Components impacted
Android app
💡 Screenshots and/or logs
There are several "Connection failed" errors with Java stack traces along with "Scheduling a restart in 10 seconds (via alarm manager)" afterward. I figure that is pretty standard for a person who is moving around in a city all day long.
🔮 Additional context
The service that is sending the push notifications to ntfy.sh is a self-hosted instance of MollySocket (which is currently working without issue for my GrapheneOS device).
@binwiederhier commented on GitHub (Feb 2, 2026):
This is a normal message that happens for the "open" event. I could have just ignored it and not logged. But it's normal.