[GH-ISSUE #333] Duplicate: IOS: Critical Alerts not registered / implemented #260

New issue

Closed

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

BreizhHardware commented

2026-05-07 00:22:23 +02:00

Owner

Originally created by @AligningEntropy on GitHub (Jun 19, 2022).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/333

Background

In IOS, notifications can be sent with a special criticalAlert priority which enables these alerts to bypass the users mute switch and Do Not Disturb settings. However, due to the disrupting nature of these notifications, Apple restricts the use of this priority and requires developers request a special entitlement (issued by Apple) and user setting authorization.

To be approved for this entitlement (I believe) one must reasonably state why such alerts are needed; consequently, it is imperative to highlight how these notifications will be limited to specific alerts, designated by the user, which are time sensitive, high urgency, and for serious events or something along those lines.

Current state / issue

Presently, when a message is published with the priority of 5 (.critical) it does not act any different than one with a priority of 4 (.timeSensitive) on the end user device alert-wise.

How to fix

The following 2 links document the steps required to enable this functionality.

Stackoverflow question where both answers are helpful here.
Medium article going over the steps similar to the link above here.

Example of an application that uses this feature

Here is an example of an application that uses the critical alert functionality.

Originally created by @AligningEntropy on GitHub (Jun 19, 2022). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/333 # Background In IOS, notifications can be sent with a special `criticalAlert` priority which enables these alerts to bypass the users mute switch and Do Not Disturb settings. However, due to the disrupting nature of these notifications, Apple restricts the use of this priority and requires developers request a special entitlement (issued by Apple) and user setting authorization. To be approved for this entitlement (I believe) one must reasonably state why such alerts are needed; consequently, it is imperative to highlight how these notifications will be limited to specific alerts, designated by the user, which are time sensitive, high urgency, and for serious events or something along those lines. # Current state / issue Presently, when a message is published with the priority of 5 (`.critical`) it does not act any different than one with a priority of 4 (`.timeSensitive`) on the end user device alert-wise. # How to fix The following 2 links document the steps required to enable this functionality. - Stackoverflow question where both answers are helpful [here](https://stackoverflow.com/questions/66057840/ios-how-do-you-implement-critical-alerts-for-your-app-when-you-dont-have-an-en/68522623#68522623). - Medium article going over the steps similar to the link above [here](https://medium.com/bandyliuk-code/how-to-implement-ios-critical-alerts-july-2021-f3bfbcc87d3f). # Example of an application that uses this feature [Here](https://support.pagerduty.com/docs/mobile-app-settings#ios-critical-alerts) is an example of an application that uses the critical alert functionality.

BreizhHardware closed this issue

2026-05-07 00:22:23 +02:00

BreizhHardware commented

2026-05-07 00:22:24 +02:00

Author

Owner

@AligningEntropy commented on GitHub (Jun 19, 2022):

Took too long to post so now this is a duplicate of https://github.com/binwiederhier/ntfy/issues/332
Moved the content of this message into a comment on that thread and will close this accordingly.

@AligningEntropy commented on GitHub (Jun 19, 2022): Took too long to post so now this is a duplicate of https://github.com/binwiederhier/ntfy/issues/332 Moved the content of this message into a comment on that thread and will close this accordingly.