![](\"images/logo.png\"){kind=logo}
\n\n \n
![\"License\"](\"https://img.shields.io/badge/License-Apache%202.0-blue.svg\"){kind=icon}
\n\n\n# Version 1.2.1-dev\n\nStable release:\n\n[](https://badge.fury.io/js/cordova-plugin-local-notification)\n\nA notification is a message you display to the user outside of your app's normal UI. When you tell the system to issue a notification, it first appears as an icon in the notification area. To see the details of the notification, the user opens the notification drawer. Both the notification area and the notification drawer are system-controlled areas that the user can view at any time.\n\n![](\"images/android-notification-example.png\")
\n\n### Notification components\n\n- Header area\n- Content area\n- Action area\n\n### How notifications may be noticed\n\n- Showing a status bar icon\n- Appearing on the lock screen\n- Playing a sound or vibrating\n- Peeking onto the current screen\n- Blinking the device's LED\n\n### Supported platforms\n\n- Android 7.0+ (minimum version by cordova-android 13.0.0) with a minimum WebView Version 60 (Android 8 is shipped with a WebView version 58 and must be updated with Google Play Store before)\n- iOS 11.3+ (minimum version by cordova-ios 7.0.0)\n\n### Installation\n\nThe plugin can be installed via [Cordova-CLI][CLI] and is publicly available on [NPM][npm].\n\n#### NPM\n\nExecute from the projects root folder:\n\n $ cordova plugin add cordova-plugin-local-notification\n\nInstall a specific version:\n\n $ cordova plugin add cordova-plugin-local-notification@VERSION\n\n#### Git\nInstall the latest head version:\n\n $ cordova plugin add https://github.com/katzer/cordova-plugin-local-notifications.git\n\nInstall from a branch:\n\n $ cordova plugin add https://github.com/katzer/cordova-plugin-local-notifications.git#branch\n\nInstall from a tag:\n\n $ cordova plugin add https://github.com/katzer/cordova-plugin-local-notifications.git#v1.0.0\n\nInstall from a specific commit:\n\n $ cordova plugin add https://github.com/katzer/cordova-plugin-local-notifications.git#5e4f131\n\n#### Local\nInstall from local source:\n\n $ cordova plugin add ![](\"images/ios-notification.png\")
\n\nYou have always to set an unique ID for every notification. The plugin does not automatically set an ID. If you do not set an ID, it will default to `1`. If you reuse an ID of a previous scheduled notification, the previous one will be canceled.\n\nThe plugin allows to schedule multiple notifications at once:\n\n```js\ncordova.plugins.notification.local.schedule([\n {\n id: 1,\n title: 'My first notification'\n },\n {\n id: 2,\n title: 'My second notification'\n }\n]);\n```\n\n## Notification Limits\nOn each platform are limits about how much notifications can be scheduled:\n\n- iOS: 64\n- Android: 500\n\nRepeating notifications count as 1 notification.\n\n## Properties\nA notification does have a set of configurable properties. See [all properties](#properties-1).\n\n## Permissions\nOn iOS and Android 13+ permissions must be requested from the user before notifications can be posted. This is done automatically, when scheduling a notification. If you want do it manually, you can use [requestPermission](#requestpermission). Please keep in mind, that the user can still change the permission later in the system. If you want to check, if you have still the permission to post notifications, use [hasPermission](#haspermission).\n\n![](\"images/ios-request-permission.png\")
\n![](\"images/android-request-permission.png\")
\n\nOn Android, the permissions must be requested since Android 13. In earlier versions no permissions must be granted.\n\n## Android specials\n\n### Notification channels\nSince Android 8 notification channels must be created to post noitifications. A [default channel](#default-channel) will be created for you, if you do not create one. You can also create your own channel by [createChannel](#createchannel) or when [scheduling a notification](#create-channel-by-posting-a-notification). For deleting a channel use [deleteChannel](#deletechannel).\n\n### Inexact alarms since Android 12\nSince Android 12 alarms will be scheduled inexact by default. On Android 12 (API level 31) and higher, the system invokes the alarm within one hour of the supplied trigger time, unless any battery-saving restrictions are in effect such as battery saver or Doze. Most apps can schedule tasks and events using inexact alarms to complete several common use cases. If your app's core functionality depends on a precisely-timed alarm — such as for an alarm clock app or a calendar app — then it's OK to use an exact alarm instead.\n\nSee [Schedule exact alarms](#android-schedule-exact-alarms), if you want use exact alarms.\n\nSee [Android documentation](https://developer.android.com/develop/background-work/services/alarms/schedule) for more information.\n\n### App hibernation / App unused\nIf your app runs on Android 12 and newer and the user doesn't interact with your app for 3 months, the system places your app in a hibernation state which will cancel all pending notifications and revokes permissions. When the user interacts with your app again, the app exits hibernation and the notifications will be re-scheduled. It doesn't count as app usage if the user dismisses a notification. If the app is hibernated, the user will get informed about it:\n\n![](\"images/android-app-hibernation-notification.png\")
\n\nThe documentation says that permissions are also revoked, but testing the hibernation behavior on an Android 15 emulator showed, that the app keeps the permission to post notifications.\n\n#### Notes\n- Android introduced this behavior in Android 11 and additionally backported this to Android 6 to 10 through the Google Play Store but only the permissions are revoked and not the pending notifications. Because permissions are only needed since Android 13, this does not affect this plugin. Since Android 12 notifications are also canceled besides revoking the permissions.\n- You can manually test the hibernation behavior, see [App hibernation > Manually invoke hibernation behavior](https://developer.android.com/topic/performance/app-hibernation#manually-invoke).\n- To see a complete list, what counts as app usage and what not, see [App hibernation > App usage](https://developer.android.com/topic/performance/app-hibernation#app-usage).\n- 3 months are based on executing `adb shell device_config get permissions \\ auto_revoke_unused_threshold_millis2` which will return `7776000000` milliseconds on an Android 15 Emulator which are nearly 3 months (~2.96 months).\n\n#### Manage App hibernation\n\nYou can get the status of the setting by calling [getUnusedAppRestrictionsStatus](#getunusedapprestrictionsstatus). To redirect the user to the setting, call [openManageUnusedAppRestrictions](#openmanageunusedapprestrictions). Before opening the setting, you can inform the user about this behavior and explain which setting he has to deactivate. When opening the settings, the system will not scroll to the right entry and the setting is named differently on different Android versions:\n\nSample Android 12:\n\n![](\"images/android-app-hibernation-settings-android-12.png\")
\n\nOn other Android versions it is named differently:\n\nAndroid 13/14:\n\n![](\"images/android-app-hibernation-settings-android-13-14.png\")
\n\nAndroid 15:\n\n![](\"images/android-app-hibernation-settings-android-15.png\")
\n\n### Doze and Standby\n\nAndroid has two power-saving features that extend battery life for users by managing how apps behave when a device isn't connected to a power source: Doze and App Standby. Doze reduces battery consumption by deferring background CPU and network activity for apps when the device is unused for long periods of time. App Standby defers background network activity for apps with no recent user activity.\n\nTo fire notifications when the device is in doze mode, you can schedule notifications with the property [androidAllowWhileIdle](#property-androidallowwhileidle).\n\nApp Standby does not affect you when showing a notification.\n\nYou can read everything about it in the [Android documentatation](https://developer.android.com/training/monitoring-device-state/doze-standby).\n\n### Alarm rescheduling\n\n#### App Update\nAndroid removes all alarms when the app is updated. The plugin reschedules all alarms by a [BroadcastReceiver](https://developer.android.com/develop/background-work/background-tasks/broadcasts) listening to [ACTION_MY_PACKAGE_REPLACED](https://developer.android.com/reference/android/content/Intent#ACTION_MY_PACKAGE_REPLACED).\n\n#### Device reboot\nAndroid removes all alarms when the device reboots. The plugin reschedules all alarms by a [BroadcastReceiver](https://developer.android.com/develop/background-work/background-tasks/broadcasts) listening to [ACTION_BOOT_COMPLETED](https://developer.android.com/reference/android/content/Intent#ACTION_BOOT_COMPLETED), but only after the device has been unlocked.\n\n#### User grants exact alarms\nIf you use [SCHEDULE_EXACT_ALARM](#exact-alarms-user-grants-permission) for scheduling exact alarms and the user permits the permission in the \"Alarms & Reminders\", inexact alarms will be rescheduled as exact alarms. This is done by a [BroadcastReceiver](https://developer.android.com/develop/background-work/background-tasks/broadcasts) listening to [ACTION_SCHEDULE_EXACT_ALARM_PERMISSION_STATE_CHANGED](https://developer.android.com/reference/android/app/AlarmManager#ACTION_SCHEDULE_EXACT_ALARM_PERMISSION_STATE_CHANGED). This action will not be called if the user revokes the permission. All exact alarms will be canceled then.\n\n[](README.md#android-15-alarms-get-canceled-on-force-stop)\n#### Android 15: Alarms get canceled on `Force stop`\nSince Android 15 all pending alarms will get canceled if the user force stops an app, this is a change by Google, see https://developer.android.com/about/versions/15/behavior-changes-all#enhanced-stop-states. The alarms will be re-registered, if the user starts the app again. If the user clears the app from the app stack the alarms will not get canceled.\n\nKeep in mind, that force stopping is only known by advised users and if they do it, they have a reason to do this and they should be aware, that the app will no longer function correctly as the System also states when clicking on `Force stop` by showing an alert with the message `If you force stop an app, it may misbehave.`\n\n## Actions\n\nYou can add actions, which can be a button or an input to a notification. Before you can use them you have to pre-define them:\n\n```javascript\ncordova.plugins.notification.local.addActions('YES_NO_CATEGORY', [\n {\n id: 'YES_ACTION',\n title: 'Yes'\n },\n {\n id: 'NO_ACTION',\n title: 'No'\n }\n]);\n```\n\nThen you have to assign the defined actions when scheduling a notification:\n\n```javascript\ncordova.plugins.notification.local.schedule({\n id: 1,\n title: 'Justin Rhyss',\n text: 'Do you want to go see a movie tonight?',\n actions: 'YES_NO_CATEGORY'\n});\n```\n\n\n ![](\"images/ios-actions.png\")
\n ![](\"images/android-actions.png\")
\n
![](\"images/ios-actions-with-input.png\")
| ![](\"images/android-actions-with-input-not-clicked.png\")
![](\"images/android-actions-with-input-clicked.png\")
|\n\nOS native documentation:\n- Android: https://developer.android.com/develop/ui/views/notifications/build-notification#reply-action\n\n### Handle action events\nYou can subscribe to an action event.\n\nExample:\n\n```javascript\ncordova.plugins.notification.local.addActions('YES_NO_CATEGORY', [\n { id: 'YES_ACTION', title: 'Yes' },\n { id: 'NO_ACTION', title: 'No' }\n]);\n```\n\nYou have to subscribe to the action id:\n\n```javascript\ncordova.plugins.notification.local.on('YES_ACTION', (notification, eopts) => {\n // Your code\n});\n```\n\nTo unsubcribe see [Events](#events).\n\n### Action properties\n\nActions do have a set of configurable properties. Not all of them are supported across all platforms.\n\n| Property | Type | Android | iOS |\n| :----------- | :----------- | :------ | :-- |\n| id | button+input | x | x |\n| title | button+input | x | x |\n| launch | button+input | x | x |\n| ui | button+input | | x |\n| needsAuth | button+input | | x |\n| icon | button+input | x | |\n| emptyText | input | x | x |\n| submitTitle | input | | x |\n| editable | input | x | |\n| choices | input | x | |\n| defaultValue | input | | |\n\n\n## Triggers\n\nNotifications may trigger immediately or depend on calendar or location.\n\n### Fixed date\nTrigger at a fixed date:\n\n```js\ncordova.plugins.notification.local.schedule({\n id: 1,\n title: 'Design team meeting',\n text: '3:00 - 4:00 PM',\n trigger: { at: new Date(2017, 10, 27, 15) }\n});\n```\n\n| Property | Type | Value | Android | iOS |\n| :------------ | :------ | :--------------- | :------ | :-- |\n| at | Date | | x | x |\n\n### Relative\nRelative from now:\n\n```js\ncordova.plugins.notification.local.schedule({\n id: 1,\n title: 'Design team meeting',\n trigger: { in: 1, unit: 'hour' }\n});\n```\n\n| Property | Type | Value | Android | iOS |\n| :------------ | :------ | :--------------- | :------ | :-- |\n| in | Int | | x | x |\n| unit | String | `second`, `minute`, `hour`, `day`, `week`, `month`, `quarter`, `year` | x | x |\n\n### Repeating\n\nRepeat relative from now:\n\n```js\ncordova.plugins.notification.local.schedule({\n id: 1,\n title: 'Design team meeting',\n trigger: { every: 'day', count: 5 } // count is only supported by Android\n});\n```\n\n| Property | Type | Value | Android | iOS | Note |\n| :------------ | :------ | :--------------- | :------ | :-- | :--- |\n| before | Date | | x | | |\n| firstAt | Date | | x | | |\n| count | Int | | x | | |\n| every | String | `minute`, `hour`, `day`, `week`, `month`, `quarter` ![](\"images/android-icon.svg\"){kind=icon}
, `year` | x | x | |\n\nTrigger every time the date matches:\n\n```js\ncordova.plugins.notification.local.schedule({\n id: 1,\n title: 'Happy Birthday!!!',\n trigger: { every: { month: 10, day: 27, hour: 9, minute: 0 } }\n});\n```\n\n| Property | Type | Value | Android | iOS | Note |\n| :------------ | :------ | :--------------- | :------ | :-- | :--- |\n| before | Date | | x | | |\n| after | Date | | x | | |\n| count | Int | | x | | |\n| every | Object | `minute`, `hour`, `day`, `weekday`, `weekdayOrdinal` ![](\"images/apple-icon.svg\"){kind=icon}
, `week` , `weekOfMonth`, `month`, `quarter` | x | x | |\n\n### Location based\n iOS only\n\nTo trigger when the user enters a region:\n\n```js\ncordova.plugins.notification.local.schedule({\n id: 1,\n title: 'Welcome to our office',\n trigger: {\n type: 'location',\n center: [x, y],\n radius: 15,\n notifyOnEntry: true\n }\n});\n```\n\n| Property | Type | Value | Android | iOS | Note |\n| :------------ | :------ | :--------------- | :------ | :-- | :--- |\n| center | Array | `[lat, long]` | | x | |\n| radius | Int | | | x | |\n| notifyOnEntry | Boolean | | | x | |\n| notifyOnExit | Boolean | | | x | |\n| single | Boolean | | | x | |\n\n## Progress\n Android only\n\nNotifications can include an animated progress indicator that shows users the status of an ongoing operation.\n\n```js\ncordova.plugins.notification.local.schedule({\n id: 1,\n title: 'Sync in progress',\n text: 'Copied 2 of 10 files',\n androidProgressBar: {\n value: 20, // Default 0\n maxValue: 100, // Default 100\n indeterminate: false // Default false\n }\n});\n```\n\n\n ![](\"images/android-progress.png\")
\n
Android only\n\nSplit the text by line breaks if the message comes from a single person and just too long to show in a single line.\n\n```js\ncordova.plugins.notification.local.schedule({\n id: 1,\n title: 'The Big Meeting',\n text: '4:15 - 5:15 PM\\nBig Conference Room',\n androidSmallIcon: 'res://ic_menu_my_calendar',\n androidLargeIcon: 'res://large_icon'\n});\n```\n\n\n ![](\"images/android-inbox.png\")
\n
Android only\n\nInstead of displaying multiple notifications, you can create one notification that summarizes them all.\n\n```js\ncordova.plugins.notification.local.schedule({\n id: 15,\n title: 'Chat with Irish',\n androidLargeIcon: 'res://large_icon',\n androidMessages: [\n { person: 'Me', message: 'I miss you' },\n { person: 'Irish', message: 'I miss you more!' },\n { person: 'Me', message: 'I always miss you more by 10%' }\n ]\n});\n```\n\n\n ![](\"images/android-chat.png\")
\n
Android only\n\nYour app can present multiple notifications as a single group:\n\n- A parent notification displays a summary of its child notifications.\n- The child notifications are presented without duplicate header information.\n\n```js\ncordova.plugins.notification.local.schedule([\n {\n id: 1,\n title: 'Design team meeting',\n ...\n },\n {\n id: 2,\n androidSummary: 'me@gmail.com',\n androidGroup: 'email',\n androidGroupSummary: true\n },\n {\n id: 3,\n title: 'Please take all my money',\n ...,\n androidGroup: 'email'\n },\n {\n id: 4,\n title: 'A question regarding this plugin',\n ...,\n androidGroup: 'email'\n },\n {\n id: 5,\n title: 'Wellcome back home',\n ...,\n androidGroup: 'email'\n }\n]);\n```\n\n\n ![](\"images/android-stack.png\")
\n
![](\"images/android-alarms-and-reminders-in-app-settings.png\")
| After declaring `SCHEDULE_EXACT_ALARM` as permission, your app have a new entry in the app settings called `Alarms & reminders`, where the user can enable/disable exact alarms. |\n| ![](\"images/android-alarms-and-reminders-setting.png\")
| Clicking on this entry will open the setting to enable/disable exact alarms. This screen will also been shown if you call [openAlarmSettings](#openalarmsettings) |\n\nOn Android 12 `SCHEDULE_EXACT_ALARM` is pre-granted. On Android 13 and newer the user has to permit this in the \"Alarms & Reminders\" setting, which you can open by [openAlarmSettings](#openalarmsettings). You can use the [resume](https://cordova.apache.org/docs/en/12.x/cordova/events/events.html#resume) event of Cordova to check if exact alarms are permitted by [canScheduleExactAlarms](#canscheduleexactalarms). If you have already posted inexact alarms, before the user granted the exact alarm permission, inexact alarms will be automatically rescheduled by this plugin as exact alarms. The downside is, when the user revokes the exact alarm permission, your app will be killed and all exact alarms will be canceled without rescheduling them as inexact alarms. You have to reschedule them the next time the user starts your app. You can read everything about it in the [Android documentation](https://developer.android.com/about/versions/14/changes/schedule-exact-alarms).\n\n### Exact alarms: Define your app as a Calender or Alarm Clock app\nThis is a very special case you should think about. When you declare your app as a calendar or alarm clock app, the app have to fullfill the requirements and must be approved by Google in the Play Store. Google could remove the app from the store if the app is found to be misusing the permission.\n\nCalendar or alarm clock apps need to send calendar reminders, wake-up alarms, or alerts when the app is no longer running. These apps can request the [USE_EXACT_ALARM](https://developer.android.com/reference/android/Manifest.permission#USE_EXACT_ALARM) permission. The `USE_EXACT_ALARM` permission will be granted on install, and apps holding this permission will be able to schedule exact alarms just like apps with the `SCHEDULE_EXACT_ALARM` permission. The advantage is, that this permission can't be revoked by the user.\n\nTo declare the `USE_EXACT_ALARM` permission in the `AndroidManifest.xml`, you can do this with your `config.xml`.\n\nFirst add the Android xml namespace to your `widget` tag:\n\n```xml\n Android only\n\nChecks if the user has enabled the \"Alarms & Reminders\"-setting. If not, the notificiatons will be scheduled inexact, which is still ok and will only be delayed by some minutes.\n- On Android 11 and older, this method will always return `true` in the `successCallback`.\n- On Android 12 the permission is granted by default\n- On Android 13 and newer, the permission is not granted by default and have to be explicitly enabled by the user.\n\n### createChannel\n Android only\n\nCreates a channel, if it not already exists. A channel is not changeable, after it is created. This is a restriction by Android.\nIf a notification does not specify a [androidChannelId](#property-androidchannelid) a [default channel](#default-channel) will be used.\n\nFor setting the channel, use [androidChannelId](#property-androidchannelid) when scheduling a notification.\n\nOverview of all properties for a channel:\n\n```js\ncordova.plugins.notification.local.createChannel({\n androidChannelId: \"my_channel_01\", // string, to separate something in the id, use \"_\" instead of \"-\"\n androidChannelName: \"My Channel Name\", // string, defaults to \"Default Channel\"\n androidChannelDescription: \"Description of channel\", // string (optional)\n androidChannelImportance: \"IMPORTANCE_DEFAULT\", // string (optional)\n androidChannelEnableLights: true, // boolean (optional), default is false\n androidChannelEnableVibration: true, // boolean (optional), default is false\n sound: 'www/audio/ring.mp3', // string (optional)\n androidChannelSoundUsage: 5 // int (optional), default is USAGE_NOTIFICATION\n }, successCallback, this)\n```\n\nProperty documentation:\n- [androidChannelId](#property-androidchannelid)\n- [androidChannelImportance](#property-androidchannelimportance)\n- [androidChannelEnableLights](#property-androidchannelenablelights)\n- [androidChannelEnableVibration](#property-androidchannelenablevibration)\n- [sound](#property-sound)\n- [androidChannelSoundUsage](#property-androidchannelsoundusage)\n\n### deleteChannel\n Android only\n\nDeletes a Android channel.\n\nExample:\n\n```javascript\ncordova.plugins.notification.local.deleteChannel(\"my_channel_id\", successCallback, this)\n```\n\nThese will delete all associated notificiations for this channel. If you create a new channel with the same id, the deleted channel will be un-deleted with all of the same settings it had before it was deleted, see [NotificationManagerCompat.deleteNotificationChannel](https://developer.android.com/reference/androidx/core/app/NotificationManagerCompat#deleteNotificationChannel(java.lang.String))\n\n### getDefaults\n\nReturns the default values all properties on each platform.\n\nExample:\n\n```js\ncordova.plugins.notification.local.getDefaults();\n```\n\n### getUnusedAppRestrictionsStatus\n\nReturns the status of unused app restrictions also called [app hibernation](#app-hibernation--app-unused), which was introduced in Android 11 and is backported to Android 6 through the Google Play Store. From Android 6 to 11, only permissions gets revoked, what does not affect notifications, because notifications needs requesting permissions only since Android 13. But because since Android 12 also notifications get canceled, the status is relevant for Android 12 and later. When unused app restrictions are active, it will return `API_30_BACKPORT` (on Android 6 to 10), `API_30` on Android 11 or `API_31`on Android 12 and later. If it is disabled, `DISABLED` will be returned.\n\nSample:\n\n```javascript\ncordova.plugins.notification.local.getUnusedAppRestrictionsStatus(\n (status) => {\n // Shortcode for getting possibile status codes for status\n const statusCodes = cordova.plugins.notification.local.androidUnusedAppRestrictionsStatusCodes;\n\n // app hibernation is active on Android 12 and later\n if (status == statusCodes.API_31) {\n\n }\n },\n this\n);\n```\n\nPossible status codes:\n\n| Name | Value | Description |\n| :---------------------- | :-------- | ----------------------- |\n| ERROR | 0 | The status of Unused App Restrictions could not be retrieved from this app e.g. if the user is in locked device boot mode. Check the logs for the reason. |\n| FEATURE_NOT_AVAILABLE | 1 | There are no available Unused App Restrictions for this app. This would happen on devices older then Android 6, but this plugin supports minimum Android 7. |\n| DISABLED | 2 | Any available Unused App Restrictions on the device are disabled for this app. In other words, this app is exempt from having its permissions automatically removed or being hibernated. |\n| API_30_BACKPORT | 3 | Unused App Restrictions introduced by Android API 30 (Android 11), and since made available on earlier (API 23-29 = Android 6 to 10) devices are enabled for this app: permission auto-reset. Note: This value is only used on API 29 (Android 10) or earlier devices. |\n| API_30 | 4 | Unused App Restrictions introduced by Android API 30 (Android 11) are enabled for this app: permission auto-reset. Note: This value is only used on API 30 (Android 11) or later devices. |\n| API_31 | 5 | Unused App Restrictions introduced by Android API 31 (Android 12) are enabled for this app: permission auto-reset and app hibernation. Note: This value is only used on API 31 (Android 12) or later devices. |\n\n### hasPermission\nChecks if the app has permissions to post notifications.\n\n```js\ncordova.plugins.notification.local.hasPermission(function (granted) { ... });\n```\n\n### iOSClearBadge\nClears the badge.\n\n### openAlarmSettings\n Android only. Since Android 12 (SDK 31).\n\nOpens the `Alarms & reminders` setting as an Activity when running on Android 12 (SDK 31) or later, where the user can enable exact alarms.\n\n\n\nThis is only available, if [SCHEDULE_EXACT_ALARM](#exact-alarms-user-grants-permission) is declared as permission in the `AndroidManifest.xml`.\n\nThis method will not wait for the user to be returned back to the app. For this, the `resume`-event can be used. The callback will just return `OK`, after starting the activity.\n- If the user grants permission, already inexact scheduled notifications will be rescheduled as exact alarms.\n- If exact alarms were already granted and the user revokes it, the app will be killed and all scheduled notifications will be canceled. The app have to schedule the notifications as inexact alarms again, when the app is opened the next time, see https://developer.android.com/develop/background-work/services/alarms/schedule#using-schedule-exact-permission.\n- On Android older then 12, it will just call the `successCallback`, without doing anything. \n\n### openManageUnusedAppRestrictions\n\nOpens the unused app restriction settings directly in your app. The `successCallback` will be called if the user returns to your app.\n\nSample:\n\n```javascript\ncordova.plugins.notification.local.openManageUnusedAppRestrictions((result) => {\n // User has returned from the settings\n}, this);\n```\n\nYou can check in the `successCallback` what the user selected, by calling [getUnusedAppRestrictionsStatus](#getunusedapprestrictionsstatus).\n\n### openNotificationSettings\nOpens the notifications settings of the app on Android 8 and newer. This method will not wait for the user to be returned back to the app. For this, the `resume`-event can be used.\n- On Android, the callback will just return \"OK\", after starting the activity.\n- On Android older then 8, it opens the app details.\n- On iOS it's not possible to open the notification settings, it will open the app settings.\n\n### requestPermission\nRequest permission to post notifications. This is called automatically by the plugin when scheduling notifications, but you can also request it manually before scheduling notifications:\n\n```js\ncordova.plugins.notification.local.requestPermission(function (granted) { ... });\n```\n\nIf this method is called, a dialog will be shown to the user to ask for the permission.\n\n\n\n\nThe user can still allow/deny the permission through the system settings.\n\nTo check if permissions are granted, without calling this method, use [hasPermission](#haspermission).\n\n### setDefaults\n\nChanges default values of properties.\n\nExample:\n\n```js\ncordova.plugins.notification.local.setDefaults({\n androidChannelId: \"my_channel_01\",\n title: \"My default Title\"\n});\n```\n\n## Properties\n\n### Changed properties\nList of changed properties on newer plugin versions.\n\n#### Changes since version `1.1.0`\n\nThere were some properties renamed. You can still use the old ones, but you will get a deprecation warning in the log and they will be removed in future versions.\n\n| Old Property | New Property |\n| :---------------------- | :-------------------------- |\n| autoClear | androidAutoCancel |\n| badge | badgeNumber |\n| channelDescription | androidChannelDescription |\n| channelId | androidChannelId |\n| channelImportance | androidChannelImportance |\n| channelName | androidChannelName |\n| clock | Use for `clock: boolean` = `androidShowWhen: boolean` and for `clock: 'chronometer'` = `androidUsesChronometer: true` |\n| color | androidColor |\n| defaults | androidDefaults |\n| description | androidChannelDescription |\n| foreground | iOSForeground |\n| group | androidGroup |\n| groupSummary | androidGroupSummary |\n| icon | androidLargeIcon |\n| iconType | androidLargeIconType |\n| importance | androidChannelImportance |\n| lockscreen | androidLockscreen |\n| mediaSession | *Property was removed* |\n| onlyAlertOnce | androidOnlyAlertOnce |\n| prio | Use `androidChannelImportance`, `androidAlarmType` and `androidAllowWhileIdle` instead. |\n| priority | Use `androidChannelImportance`, `androidAlarmType` and `androidAllowWhileIdle` instead. |\n| progressBar | androidProgressBar |\n| smallIcon | androidSmallIcon |\n| sticky | androidOngoing |\n| soundUsage | androidChannelSoundUsage |\n| ongoing | androidOngoing |\n| summary | androidSummary |\n| text as Array | androidMessages |\n| timeoutAfter | androidTimeoutAfter |\n| titleCount | androidTitleCount |\n| wakeup | androidWakeUpScreen |\n\n##### Changes on androidProgressBar\nThe default value changed from:\n\n```json\n{enabled: false, value:0, maxValue:100, indeterminate:false}\n```\n\nto\n\n`null`\n\nThe property `androidProgressBar.enabled` is not supported anymore.\nJust set `androidProgressBar: null` to disable the progressbar.\n\n##### Changes on sound\nThe property `sound` takes no longer additionally a boolean, now only a string, which points to a sound file.\n- The value `sound: true` is replaced with `sound: 'default'`\n- The value `sound: false` is replaced with `sound: null`\n\n### Changes since version `1.1.1`\n\nThere were some properties renamed. You can still use the old ones, but you will get a deprecation warning in the log and they will be removed in future versions.\n\n| Old Property | New Property | Reason |\n| :---------------------- | :---------------------------- | ----------------------- |\n| vibrate | androidChannelEnableVibration | The vibration cannot be controlled on iOS. So this is a Android only property and can only be set on a channel. See [androidChannelEnableVibration](#property-androidchannelenablevibration)|\n\n### Common properties\n\nThese properties can be used on all platforms, but some may behave differently on each platform.\n\n| Property | Default | Comment |\n| :----------------------| :-----------------|:--------------------------|\n| [actions](#actions) | `[]` | Actions of a notification |\n| [attachments](#property-attachments) | `[]` | List of resources, to attach to the notification. |\n| [badgeNumber](#property-badgenumber) | Android: `1`, iOS: `-1` | Sets the badge for the application. The behaviour differs on Android and iOS. |\n| data | `null` | Custom data for the notification. Can be used, when the notification is send back to the app, e.g. by clicking on it. |\n| [id](#property-id) | `1` | ID of a notification as number. |\n| launch | `true` | If a click on the notification should launch the app. |\n| [priority](#property-priority) | `0` (=PRIORITY_DEFAULT) | Deprecated. Use [androidChannelImportance](#property-androidchannelimportance), [androidAlarmType](#property-androidalarmtype) and [androidAllowWhileIdle](#property-androidallowwhileidle) |\n| silent | `false` | iOS: Don't show a notification, make no sound, no vibration, when app is in foreground. Android: Don't show a notification (Does not create a Builder. Must be tested if that works) |\n| text | `\"\"` | Text of the notification. Android features: 1. If the text contains line breaks (`\\n`) the notification style [NotificationCompat.InboxStyle](https://developer.android.com/reference/androidx/core/app/NotificationCompat.InboxStyle) will be used. 2. If the text is longer then 44 chars, the notifications style [NotificationCompat.BigTextStyle](https://developer.android.com/reference/androidx/core/app/NotificationCompat.BigTextStyle) will be used. |\n| [sound](#property-sound) | `default` | Sets the sound of a notification. On iOS it also turns on/off the vibration. |\n| title | `\"\"` (Sets the app name) | Title of the notification. Has to be a String. If it is empty, the app name will be used. |\n| [trigger](#triggers) | `{at: new Date(), type : \"calendar\"}`| Notifications may trigger depend on time or location (iOS only) |\n\n### Android properties\n\nThese properties are only available on Android.\n\n| Property | Default | Comment |\n| :----------------------| :-----------------|:--------------------------|\n| [androidAlarmType](#property-androidalarmtype) | `RTC_WAKEUP` | |\n| [androidAllowWhileIdle](#property-androidallowwhileidle) | `false` | Alarm will be allowed to execute even when the system is in low-power idle (a.k.a. doze) modes. |\n| androidAutoCancel | `true` | Make this notification automatically dismissed when the user touches it |\n| androidChannelDescription | `null` | Sets the `description` of a [notification channel](#notification-channels). |\n| [androidChannelEnableLights](#property-androidchannelenablelights) | `false` | Can be `true` or `false`and sets whether notifications posted to a [notification channel](#android-channels) should display notification lights, on devices that support that feature. |\n| [androidChannelEnableVibration](#property-androidchannelenablevibration) | `false` | Enables the vibration of a channel. |\n| [androidChannelId](#property-androidchannelid) | `default_channel` | Specifies the channel id to be posted on. |\n| androidChannelImportance | `IMPORTANCE_DEFAULT` | Sets the [importance](#property-androidchannelimportance) of a [notification channel](#notification-channels) |\n| androidChannelName | `Default channel` | Set the `channelName` for the notification to be posted on. See [Android Notification Channels](#notification-channels) for more information. |\n| androidChannelSoundUsage | `5` (=USAGE_NOTIFICATION) | Sets the [androidChannelSoundUsage](#property-androidchannelsoundusage) of a [notification channel](#notification-channels). |\n| [androidColor](#property-androidcolor) | `null` | The notification background color for the small icon in the notification style. |\n| [androidGroup](#grouping) | `null` | Set this notification to be part of a group of notifications sharing the same key. Grouped notifications may display in a cluster or stack on devices which support such rendering. To make this notification the summary for its group, also call setGroupSummary(boolean). A sort order can be specified for group members by using setSortKey(String) (not implemented yet). Calls [Notification.Builder#setGroup(java.lang.String)](https://developer.android.com/reference/android/app/Notification.Builder#setGroup(java.lang.String)) |\n| [androidGroupSummary](#grouping) | `false` | Set this notification to be the group summary for a group of notifications. Grouped notifications may display in a cluster or stack on devices which support such rendering. Requires a group key also be set using setGroup(String). The group summary may be suppressed if too few notifications are included in the group. Calls [Notification.Builder#setGroupSummary(boolean)](https://developer.android.com/reference/android/app/Notification.Builder#setGroupSummary(boolean)) |\n| [androidLargeIcon](#property-androidlargeicon) | `null` | Add a large icon to the notification content view. |\n| androidLargeIconType | `square` | Can be `square` or `circle` |\n| androidLockscreen | `true` | If the entire notification should be shown on all lockscreens and while screen sharing. If the value is `true`, [Notification#VISIBILITY_PUBLIC](https://developer.android.com/reference/android/app/Notification#VISIBILITY_PUBLIC) will be set, otherwise [Notification#VISIBILITY_SECRET](https://developer.android.com/reference/android/app/Notification#VISIBILITY_SECRET). Sets [Notification#visibility](https://developer.android.com/reference/android/app/Notification#visibility). |\n| androidMessages | `null` | Array of messages to [summarize](#summarizing) notifications. [NotificationCompat.MessagingStyle](https://developer.android.com/reference/androidx/core/app/NotificationCompat.MessagingStyle) will be used. |\n| androidOngoing | `false` | Set whether this is an ongoing notification. Ongoing notifications cannot be dismissed by the user on locked devices, or by notification listeners, and some notifications (call, device management, media) cannot be dismissed on unlocked devices. |\n| androidOnlyAlertOnce | `false` | Set this flag if you would only like the sound, vibrate and ticker to be played if the notification is not already showing (see [documentation](https://developer.android.com/reference/android/app/Notification.Builder#setOnlyAlertOnce(boolean))). |\n| androidProgressBar | `null` | See [documentation](#progress) |\n| androidShowWhen | `true` | If the Notification should show the when date. Before Version 1.1.0 called `clock`. |\n| [androidSmallIcon](#property-androidsmallicon) | `res://ic_popup_reminder` (=Bell icon) | Set the small icon resource, which will be used to represent the notification in the status bar. |\n| [androidSummary](#property-androidsummary) | `null` | |\n| androidTimeoutAfter | `0` | Specifies a duration in milliseconds after which this notification should be canceled, if it is not already canceled. `0` means no automatic cancellation. |\n| androidTitleCount | `%n%` | Additional text added to the title for displaying the number of messages if there is more than one. Only used, if using MessagingStyle. Use `%n%` in the string for specifying the location of the number. |\n| androidUsesChronometer | `false` | Show the Notification#when field as a stopwatch. Instead of presenting when as a timestamp, the notification will show an automatically updating display of the minutes and seconds since when. Useful when showing an elapsed time (like an ongoing phone call). Was former handeld by `clock: 'chronometer'` |\n| androidWakeUpScreen | `true` | If the screen should go on, when a notification arrives |\n| androidDefaults | `0` | Android 7 only. Sets the default notification options that will be used only on Android 7. Bitwise-or of: DEFAULT_SOUND, DEFAULT_VIBRATE, DEFAULT_LIGHTS. |\n| led | `false` | Android 7 only. Can be a Hex-String like `#FF00FF` or `{color: '#FF00FF', on: 500, off: 500}` and sets the led of a notification. Replaced by [androidChannelEnableLights](#property-androidchannelenablelights). |\n\n### iOS properties\n\nThese properties are only available on iOS.\n\n| Property | Default value | Comment |\n| :--------------------------------------- | :-------------------- | :------------------------ |\n| [iOSForeground](#property-iosforeground) | `true` | Displays a notification banner, when app is in foreground. |\n\n#### Some notes:\n- A progressbar is natively not supported by iOS, [see Stackoverflow](https://stackoverflow.com/questions/48500532/progress-view-in-local-notification/48500734#48500734)\n- The vibration cannot be turned off separately. It can only be turned off, if no sound is set.\n\n### Default values\n\nDefault values for the properties can be get by [getDefaults](#getdefaults).\nValues can be changed by [setDefaults](#setdefaults)\n\n### Available properties\n\n#### Property `androidAllowWhileIdle`\nDefault: `false`\n\nAlarm will be allowed to execute even when the system is in low-power idle (a.k.a. doze) modes.\n\nThis type of alarm must only be used for situations where it is actually required that the alarm go off while in idle -- a reasonable example would be for a calendar notification that should make a sound so the user is aware of it. When the alarm is dispatched, the app will also be added to the system's temporary power exemption list for approximately 10 seconds to allow that application to acquire further wake locks in which to complete its work.\n\nThis executes [AlarmManager.setAndAllowWhileIdle](https://developer.android.com/reference/android/app/AlarmManager#setAndAllowWhileIdle(int,%20long,%20android.app.PendingIntent)) or [AlarmManager.setExactAndAllowWhileIdle](https://developer.android.com/reference/android/app/AlarmManager#setExactAndAllowWhileIdle(int,%20long,%20android.app.PendingIntent)) depending on [canScheduleExactAlarms](#canscheduleexactalarms).\n\n#### Property `androidAlarmType`\nDefault: `RTC_WAKEUP`\n\nIf the alarm should be scheduled on a specific time or in relevance to the time, when the device was booted and if the alarm should wakeup the device cpu (not the screen). See also the Android documentation [Choose an alarm type](https://developer.android.com/develop/background-work/services/alarms/schedule#type).\n\n| Value | Support | Description |\n|:-----------------|:--------|:------------|\n| [RTC_WAKEUP](https://developer.android.com/reference/android/app/AlarmManager#RTC_WAKEUP) | x | Alarm time in `System.currentTimeMillis()` (wall clock time in UTC), which will wake up the device (the CPU not the screen) when it goes off. |\n| [RTC](https://developer.android.com/reference/android/app/AlarmManager#RTC) | x | Alarm time in `System.currentTimeMillis()` (wall clock time in UTC). This alarm does not wake the device up; if it goes off while the device is asleep, it will not be delivered until the next time the device wakes up. |\n| [ELAPSED_REALTIME_WAKEUP](https://developer.android.com/reference/android/app/AlarmManager#ELAPSED_REALTIME_WAKEUP) | - | Alarm time in `SystemClock.elapsedRealtime()` (time since boot, including sleep), which will wake up the device (the CPU, not the screen) when it goes off. |\n| [ELAPSED_REALTIME](https://developer.android.com/reference/android/app/AlarmManager#ELAPSED_REALTIME) | - | Alarm time in `SystemClock.elapsedRealtime()` (time since boot, including sleep). This alarm does not wake the device up; if it goes off while the device is asleep, it will not be delivered until the next time the device wakes up. |\n\n#### Property `androidChannelEnableLights`\nDefault: `false`\n\nCan be `true` or `false`and sets whether notifications posted to a [notification channel](#notification-channels) should display notification lights, on devices that support that feature.\n\nAndroid documentation: https://developer.android.com/reference/android/app/NotificationChannel#enableLights(boolean)\n\n#### Property `androidChannelEnableVibration`\nDefault: `false`\n\nSets the vibration of a [notification channel](#notification-channels) by setting [NotificationChannel#enableVibration(boolean)](https://developer.android.com/reference/android/app/NotificationChannel#enableVibration(boolean)). On Android 7 this sets the vibration of a notification directly.\n\n#### Property `androidChannelId`\nDefault: `default_channel`\n\nSets the `channelId` for the notification to be posted on. Use [Snake Case](https://en.wikipedia.org/wiki/Snake_case) for the id, which means, the id should be written in lowercase and words should be separated by underscores (`_`) and not hyphens (`-`) or whitespaces.\n\n#### Property `androidChannelImportance`\nDefault: `\"IMPORTANCE_DEFAULT\"`\n\nThe property can have one of the following values:\n\n| Value | Description |\n|:-----------------|:------------|\n| [IMPORTANCE_NONE](https://developer.android.com/reference/androidx/core/app/NotificationManagerCompat#IMPORTANCE_NONE()) | A notification with no importance: shows nowhere, is blocked. |\n| [IMPORTANCE_MIN](https://developer.android.com/reference/androidx/core/app/NotificationManagerCompat#IMPORTANCE_MIN()) | Min notification importance: only shows in the shade, below the fold. |\n| [IMPORTANCE_LOW](https://developer.android.com/reference/androidx/core/app/NotificationManagerCompat#IMPORTANCE_LOW()) | Low notification importance: shows everywhere, but is not intrusive. |\n| [IMPORTANCE_DEFAULT](https://developer.android.com/reference/androidx/core/app/NotificationManagerCompat#IMPORTANCE_DEFAULT()) | Default notification importance: shows everywhere, allowed to makes noise, but does not visually intrude. |\n| [IMPORTANCE_HIGH](https://developer.android.com/reference/androidx/core/app/NotificationManagerCompat#IMPORTANCE_HIGH()) | Higher notification importance: shows everywhere, allowed to makes noise and peek. |\n| [IMPORTANCE_MAX](https://developer.android.com/reference/androidx/core/app/NotificationManagerCompat#IMPORTANCE_MAX()) | Highest notification importance: shows everywhere, allowed to makes noise, peek, and use full screen intents. |\n\nSee the [Android documentation](https://developer.android.com/develop/ui/views/notifications#importance) about this property.\n\nSee also [NotificationChannel#NotificationChannel(java.lang.String,%20java.lang.CharSequence,%20int)](https://developer.android.com/reference/android/app/NotificationChannel#NotificationChannel(java.lang.String,%20java.lang.CharSequence,%20int))\n\n#### Property `androidChannelSoundUsage`\nDefault: `5` (=`USAGE_NOTIFICATION`)\n\nThe property can have one of the following values:\n\n| Property value | Android variable | Description |\n|:-----------------|:-----------------|:------------|\n| 0 | [USAGE_UNKNOWN](https://developer.android.com/reference/android/media/AudioAttributes#USAGE_UNKNOWN) | Usage value to use when the usage is unknown. |\n| 1 | [USAGE_MEDIA](https://developer.android.com/reference/android/media/AudioAttributes#USAGE_MEDIA) | Usage value to use when the usage is media, such as music, or movie soundtracks. |\n| 2 | [USAGE_VOICE_COMMUNICATION](https://developer.android.com/reference/android/media/AudioAttributes#USAGE_VOICE_COMMUNICATION)| Usage value to use when the usage is voice communications, such as telephony or VoIP. ","readmeFilename":"README.md"}