mirror of
https://github.com/binwiederhier/ntfy.git
synced 2026-05-09 16:35:53 +02:00
[GH-ISSUE #1080] iOS push notification says "New message" only since 27th of March #757
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#757
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 @lost-carrier on GitHub (Mar 31, 2024).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1080
🐞 Describe the bug
My self-hosted instance was running fine for some time, but on Thu I updated 2.9.0 to 2.10.0. Since about then ALL push notifications only show "New message" instead of the actual content.
💻 Components impacted
Updated to Ntfy 2.10.0 but reverted back to 2.9.0 and issue persists. Ntfy running in Docker behind Traefik.
iPhone is 14 Pro iOS 17.4. Ntfy App v1.3.
💡 Screenshots and/or logs
🔮 Additional context
"upstream-base-url" and "base-url" are set correctly according to https://ntfy.sh/docs/config/#ios-instant-notifications . This whole thingy was working up to 2024-03-27. Also I've checked and I can reach my self-hosted ntfy just fine from my phone (wifi and mobile network).
@lost-carrier commented on GitHub (Apr 1, 2024):
Hm... updated iOS to 17.4.1 and it's working again... still no clue why, but I guess this can be closed.
@PaddeK commented on GitHub (Apr 6, 2024):
I am using self-hosted version 2.10.0 and i have the same problem on my iOS 17.4.1 device. Any clue what to do here to get it working again?
@PaddeK commented on GitHub (Apr 8, 2024):
Everything has been fine again since this weekend. But I don't know why, because I haven't changed anything. The usual steps like container restart etc had no immediate effect. Sorry I couldn't be more helpful in finding the problem.
@joaomirandas commented on GitHub (Sep 11, 2024):
Same here! No content on notifications.
@tazz4843 commented on GitHub (Sep 17, 2024):
Can repro. It works sometimes for me on some channels for a few days before all channels begin failing. It would really help if we had access to the logs but I can't see a way to get to them.
@sametguzeldev commented on GitHub (Sep 19, 2024):
I can confirm I am having the same issue. Maybe it is related to iOS update to 18?
@tazz4843 commented on GitHub (Sep 19, 2024):
I ran iOS 18 from the moment the first dev beta was available to RC1 and today. I was able to get notification content during most of that period, this issue only began around two to three weeks ago.
As well, when it began failing, it started only partially failing, where some channels would provide content and others would not, before slowly transitioning into all channels not providing content.
@sametguzeldev commented on GitHub (Sep 20, 2024):
I just removed the app completely from my iPhone and reinstalled it. That solved the problem for me!
@tazz4843 commented on GitHub (Sep 20, 2024):
Overnight this morning the issue just suddenly disappeared and I now have message content again.
@mdlaat commented on GitHub (Jan 28, 2025):
It also suddenly stopped working for me. Notification only show "new message".
I'm following in case someone has a solution.
@vkarlsen commented on GitHub (Apr 22, 2025):
This can be caused by an expired (or otherwise invalid) TLS certificate on the server. The "ping" comes from the upstream_base_url, while the notification itself is fetched from the base_url. The iOS app silently fails on invalid TLS certs on base_url. In this case, the app knows there should be a notification, but it can't fetch it.