react-native-notify-kit 9.1.19 → 9.1.20

package/README.md

@@ -251,7 +251,7 @@ This fork is a complete migration to React Native's **New Architecture**:
 - **Minimum React Native 0.73**, development target **0.84**
 - **Toolchain**: Yarn 4, Node 22+, Java 17, compileSdk/targetSdk 35
 - **Core notification logic (NotifeeCore) is unchanged** — the public API is fully compatible with the original Notifee
-- **14 upstream bugs fixed** — see [Bugs Fixed from Upstream Notifee](#bugs-fixed-from-upstream-notifee) below
+- **17 upstream bugs fixed** — see [Bugs Fixed from Upstream Notifee](#bugs-fixed-from-upstream-notifee) below
 - **Reliable trigger notifications** — AlarmManager is the default backend instead of WorkManager, with automatic fallback when exact alarm permission is not granted
 - **New API: `setNotificationConfig()`** — opt-out flag to prevent Notifee from intercepting iOS remote notification handlers (see [New APIs](#new-apis) below)
 
@@ -265,6 +265,8 @@ This fork fixes the following bugs that were never resolved in the original Noti
 | `completionHandler` not called on notification dismiss | iOS | Pre-existing | 9.1.12 |
 | `completionHandler` not called in `willPresentNotification` fallback | iOS | Pre-existing | 9.1.12 |
 | `getInitialNotification()` returns `null` on cold start (deprecated `UIApplicationLaunchOptionsLocalNotificationKey` check) | iOS | [#1128](https://github.com/invertase/notifee/issues/1128) | 9.1.12 |
+| `willPresentNotification:` fallback silently drops foreground notifications when no original delegate is captured (returns `None` instead of platform defaults) | iOS | Pre-existing (introduced by partial fix in v9.1.12) | 9.1.20 |
+| All delivered notifications dismissed from Notification Center when the app is opened | iOS | [#828](https://github.com/invertase/notifee/issues/828) | 9.1.20 |
 | `getInitialNotification()` returns `null` without `pressAction` configured | Android | [#1128](https://github.com/invertase/notifee/issues/1128) | 9.1.12 |
 | Foreground press events silently dropped when React instance not ready | Android | [#1279](https://github.com/invertase/notifee/issues/1279) | 9.1.12 |
 | Trigger notifications not firing on Android 14-15 when app is killed (missing `goAsync()` in `BroadcastReceiver`) | Android | [#1100](https://github.com/invertase/notifee/issues/1100) | 9.1.12 |
@@ -275,6 +277,8 @@ This fork fixes the following bugs that were never resolved in the original Noti
 | Manifest merger failure when overriding `foregroundServiceType` on `ForegroundService` | Android | [#1108](https://github.com/invertase/notifee/issues/1108) | 9.1.13 |
 | Foreground service notifications dismissible on Android 13+ even with `ongoing: true` (library doesn't auto-set `ongoing` for foreground services) | Android | [#1248](https://github.com/invertase/notifee/issues/1248) | 9.1.14 |
 | DST (daylight saving time) shifts repeating scheduled notifications by ±1 hour | Android | [#875](https://github.com/invertase/notifee/issues/875) | 9.1.14 |
+| `!=` reference equality on String comparison in `NotificationPendingIntent` (latent — would activate when `getLaunchActivity()` returns a non-null value for `id=default`) | Android | Pre-existing (latent) | 9.1.19 |
+| `pressAction.launchActivity` not defaulted at native layer when `pressAction.id === 'default'` | Android | N/A (defense-in-depth) | 9.1.19 |
 
 > **Note for apps requiring guaranteed exact alarms (alarm clocks, timers, calendars):**
 > Add `<uses-permission android:name="android.permission.USE_EXACT_ALARM" />` to your app's
@@ -285,6 +289,24 @@ This fork fixes the following bugs that were never resolved in the original Noti
 
 As bugs are fixed, this table is updated. See [CHANGELOG.md](CHANGELOG.md) for full details.
 
+## Behavior changes from upstream
+
+In addition to bug fixes, the fork makes a few opinionated default changes vs `@notifee/react-native` to improve reliability and reduce footguns. These are intentional behavioral differences that you should be aware of when migrating:
+
+- **Trigger notifications use AlarmManager by default** instead of WorkManager (since 9.1.12). WorkManager is battery-friendly but unreliable for time-sensitive notifications — Android may defer or drop WorkManager tasks based on Doze mode and OEM power management. Opt out per-trigger with `alarmManager: false` in the trigger config if you need battery-friendly scheduling where exact timing is not critical.
+
+- **`AlarmType` defaults to `SET_EXACT_AND_ALLOW_WHILE_IDLE`** (since 9.1.12) instead of upstream's `SET_EXACT`, for better Doze mode compatibility.
+
+- **`ongoing` defaults to `true` when `asForegroundService: true`** (since 9.1.14), preventing foreground service notifications from being dismissed by the user on Android 13+. This matches pre-Android 13 platform behavior. Override by setting `ongoing: false` explicitly.
+
+- **Foreground service notifications dismissed on Android 14+ are auto re-posted** (since 9.1.14) while the service is still running. Android 14 ignores `FLAG_ONGOING_EVENT` for most foreground service types (except `mediaPlayback`, `phoneCall`, and enterprise DPC); the library detects the dismissal and immediately re-displays the notification.
+
+- **`pressAction.launchActivity` defaults to `'default'` at the native layer when `pressAction.id === 'default'`** (since 9.1.19). The TypeScript validator already applied this default since upstream PR #141 (Sept 2020), but native code paths bypassing the validator (e.g., trigger notifications restored from the Room database after reboot, headless tasks) could miss it. The fork closes the gap at the native layer as defense-in-depth — eliminates an entire class of "tap doesn't open app" bugs in Android task management edge cases.
+
+- **Library no longer hardcodes `foregroundServiceType` in its manifest** (since 9.1.13 — **BREAKING vs upstream**). Apps using `asForegroundService: true` on Android 14+ must declare their own `foregroundServiceType` on `app.notifee.core.ForegroundService` in their app manifest. See [Foreground Service Setup](#foreground-service-setup-android-14) below for migration instructions. Upstream hardcoded `shortService`, which caused a manifest merger failure ([#1108](https://github.com/invertase/notifee/issues/1108)) and a 3-minute timeout ANR crash ([#703](https://github.com/invertase/notifee/issues/703)).
+
+These changes are documented in the [CHANGELOG](CHANGELOG.md) under the release that introduced them. If you rely on any of the upstream defaults, you can either pin to the specific behavior via the opt-out flags listed above, or open an issue to discuss.
+
 ## Foreground Service Setup (Android 14+)
 
 Android 14 (API 34) requires all foreground services to declare an explicit `foregroundServiceType`. If you use `asForegroundService: true` in your notifications, add the following to your app's `AndroidManifest.xml`:

package/android/libs/app/notifee/core/maven-metadata.xml

@@ -8,6 +8,6 @@
     <versions>
       <version>202108261754</version>
     </versions>
-    <lastUpdated>20260407095025</lastUpdated>
+    <lastUpdated>20260407153620</lastUpdated>
   </versioning>
 </metadata>

package/android/libs/app/notifee/core/maven-metadata.xml.md5

@@ -1 +1 @@
-4cd00d35eb2c52b5da70bd750ca2f278
+e81dd495216cd8b79614ae21d2c49dab

package/android/libs/app/notifee/core/maven-metadata.xml.sha1

@@ -1 +1 @@
-b2423a4923cfd7d1606dd2b1261c1c469852c77a
+648add9af365c35bc323edb8ae6dbd26d2c7d04f

package/android/libs/app/notifee/core/maven-metadata.xml.sha256

@@ -1 +1 @@
-f7d8da04a8e3efd70f19ddeacdc092398c3b3af14737fd90e1f6e0fd76e6974c
+c8268693b54af384d9490ceecabfb9588c41842f43074d2eeb1d6e6008445a5f

package/android/libs/app/notifee/core/maven-metadata.xml.sha512

@@ -1 +1 @@
-7eca8612035b483c4dede070ada94ff63f5d04714c37597ddcba8e11afa8ad47e4107f6f1908503682c990b01954bede58b413f04f19e6c9896e6939703c6878
+ff39f1f751413787f873ac76677c4506acadfce7f712a8048b02f6fd99a195a83d4a7a202975ebc9b898ae116be7b72f50ce166ccfa5b86df9d945adf3f3daf3

package/dist/version.d.ts

@@ -1 +1 @@
-export declare const version = "9.1.19";
+export declare const version = "9.1.20";

package/dist/version.js

@@ -1,3 +1,3 @@
 // Generated by genversion.
-export const version = '9.1.19';
+export const version = '9.1.20';
 //# sourceMappingURL=version.js.map

package/ios/NotifeeCore/NotifeeCore+UNUserNotificationCenter.m

@@ -166,7 +166,24 @@ struct {
                       willPresentNotification:notification
                         withCompletionHandler:completionHandler];
   } else {
-    completionHandler(UNNotificationPresentationOptionNone);
+    // No original delegate captured and the notification is not Notifee-owned.
+    // Returning UNNotificationPresentationOptionNone would silently drop the
+    // notification (no banner, no sound, no badge, no Notification Center entry),
+    // making remote pushes invisible to users in apps that don't install a
+    // competing UNUserNotificationCenterDelegate (e.g. apps without
+    // @react-native-firebase/messaging). Fall back to the platform default
+    // presentation options instead so the system shows the notification as it
+    // would if Notifee had not installed a delegate at all.
+    if (@available(iOS 14.0, *)) {
+      completionHandler(UNNotificationPresentationOptionBanner |
+                        UNNotificationPresentationOptionSound |
+                        UNNotificationPresentationOptionList |
+                        UNNotificationPresentationOptionBadge);
+    } else {
+      completionHandler(UNNotificationPresentationOptionAlert |
+                        UNNotificationPresentationOptionSound |
+                        UNNotificationPresentationOptionBadge);
+    }
   }
 }
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "react-native-notify-kit",
-  "version": "9.1.19",
+  "version": "9.1.20",
   "author": "Marco Crupi",
   "description": "Maintained Notifee-compatible fork for React Native — advanced local notifications for Android & iOS.",
   "main": "dist/index.js",

package/src/version.ts

@@ -1,2 +1,2 @@
 // Generated by genversion.
-export const version = '9.1.19';
+export const version = '9.1.20';