mirror of
https://github.com/binwiederhier/ntfy.git
synced 2026-05-09 08:26:00 +02:00
[GH-ISSUE #1235] iOS: Enable critical alerts #872
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#872
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 @miklos-szel on GitHub (Dec 10, 2024).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1235
💡 Idea
Since this app is all about notifications please enable the option to send Critical Alerts and Time-Sensitive Notifications bypassing DND and other settings.
I.e. Home Assistant:
💻 Target components
IOS app
@federicotravaini commented on GitHub (Jan 4, 2025):
absolutely agree, having critical notifications is a "must"
hope it will be implemented
@Nikto655 commented on GitHub (Jan 15, 2025):
any word on critical alerts? It's been years now and still nothing.
@aaronellington commented on GitHub (Feb 10, 2025):
+1 This feature would also enable ntfy to fill my use-case.
@d0x7 commented on GitHub (Mar 2, 2025):
Are there plans to integrate this? The lack of it was the same reason I didn’t use Ntfy the first time I needed it for something.
@bradenterpstra01 commented on GitHub (Mar 27, 2025):
According to an article by Pushover, it took them nearly two years to implement this. Not because their developers couldn't, but because Apple has to approve your app for it.
https://blog.pushover.net/posts/2020/2/ios-critical-alerts
Apple states: "Critical alerts require a special entitlement issued by Apple."
https://developer.apple.com/documentation/usernotifications/unauthorizationoptions/criticalalert
@d0x7 commented on GitHub (Mar 27, 2025):
I don’t wanna say they’re lying, but it’s definitely feasible. I’m now using iGotify to push to apple devices, which is both an app that has the critical alerts entitlement, as well as an server that you have to run, where Gotify (the self hosted application where you send your notifications to) passes the notifications to, as an endpoint. It doesn’t have many users (20 reviews on the App Store), yet it acquired the critical alerts entitlement.
Can only recommend it to anyone else having this problem. I’m sorry for the advertisement and hope it’s okay as it’s also all open source and completely free to use with no paid version whatsoever.
@Terabyte1385 commented on GitHub (Jun 6, 2025):
Is this planned? From what I hear, it's pretty easy to get the entitlements - however, the app should meet some criteria, which I'm not sure an app specifically designed for doing just notifications, like ntfy, meets. Usually, apps with critical alerts are full-fledged apps with some feature with critical notifications needs, such as in Home Assistant or Apple Home (security system, leak or smoke alerts), or things like weather alerts and others of the sort. Especially granted the possibility of triggering these critical alerts easily and potentially repetitively in a way that could be used to disturb users, I believe it'll take more convincing to have Apple provide the entitlement - but it's not impossible, and hoping to see it come to ntfy.
If not critical alerts, at least Time Sensitive. Those don't require entitlements.
@kholisrag commented on GitHub (Jul 26, 2025):
+1
@louis123562 commented on GitHub (Aug 22, 2025):
+1
I switched from bark to ntfy.sh, because it is available for Android, but it does not have Critical Alerts on iOS :(
If possible, i would like to do the entitlement for ntfy.sh - please contact me.
@ITCMD commented on GitHub (Mar 23, 2026):
+1 on this
@dodofarm commented on GitHub (Mar 23, 2026):
+1 from my end as well
I have to rely on PagerDuty for now because Pushover doesn't seem to alarm as reliably.
@ITCMD commented on GitHub (Mar 26, 2026):
Not to derail the conversation, but we're in the process of moving to pushover from ntfy because of this issue. What reliability issues do you have? The ability to not even notify on low or very low, standard notif on normal, critical on high, and critical/keeps alarming on urgent is nice with pushover (like ntfy does on Android)
@dodofarm commented on GitHub (Mar 26, 2026):
I can't recall the exact details since this was some time ago but I tried at 2 distinct moments to use the Pushover iOS app with critical alerts and I believe they were either too quiet or not "critical" enough (e.g. didn't work in sleep mode or something similar like being unreliable and sometimes not paging).
In the end I had to use PagerDuty, I really wanted Pushover to work but it just didn't fulfill the needs. I can test again in a bit and report back.
@louis123562 commented on GitHub (Mar 27, 2026):
I am using bark for a while now; the critical alerts on iOS are really critical, trust me. They will shoot up whatever focus or sleep mode is enabled.