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.
:computer: Components impacted
Android app
:bulb: Screenshots and/or logs
This is a log of the ntfy Android app. The log shows up to 1,000 entries.
Device info:
--
ntfy: 1.16.0 (fdroid)
OS: 4.9.337-perf+
Android: 12 (SDK 32)
Model: FP3
Product: lineage_FP3
--
Settings:
{
"autoDeleteSeconds": 2592000,
"autoDownloadMaxSize": 1048576,
"broadcastEnabled": true,
"connectionProtocol": "ws",
"darkMode": -1,
"defaultBaseUrl": "",
"lastSharedTopics": [],
"minPriority": 1,
"mutedUntil": 0,
"recordLogs": true
}
Logs
--
[logs omitted for brevity]
1704265076343 2024-01-03 07:57:56.343 D NtfyWsConnection ntfy.sh/ANONYMIZED_TOPIC (gid=1): Opening https://ntfy.sh/ANONYMIZED_TOPIC/ws?since=none with listener ID 22 ...
1704265076978 2024-01-03 07:57:56.978 D NtfyWsConnection ntfy.sh/ANONYMIZED_TOPIC (gid=1, lid=22): Opened connection
1704265076978 2024-01-03 07:57:56.978 D NtfyWsConnection ntfy.sh/ANONYMIZED_TOPIC (gid=1, lid=22): Received message: {"id":"ANONYMIZED_ID","time":1704265078,"event":"open","topic":"ANONYMIZED_TOPIC"}
1704265076978 2024-01-03 07:57:56.978 D NtfyWsConnection ntfy.sh/ANONYMIZED_TOPIC (gid=1, lid=22): Irrelevant or unknown message. Discarding.
[logs omitted for brevity]
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.
:crystal_ball: 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).
:lady_beetle: 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.
:computer: Components impacted
Android app
:bulb: 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.
:crystal_ball: 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).