react-native-notify-kit 9.1.12 → 9.1.13

package/README.md

@@ -206,14 +206,127 @@ transformIgnorePatterns: [
 
 ## What's Different from Notifee
 
-This fork fixes 9 upstream bugs and adds several improvements:
+This fork is a complete migration to React Native's **New Architecture**:
+
+- **TurboModules only** — no legacy Bridge support
+- **Android bridge rewritten in Kotlin** (original was Java)
+- **11 upstream bugs fixed** — see table below
+- **Reliable trigger notifications** — AlarmManager is the default backend instead of WorkManager
+- **New API: `setNotificationConfig()`** — opt-out flag for iOS remote notification handling
+
+## Bugs Fixed from Upstream Notifee
+
+| Bug | Platform | Upstream Issue | Fixed in |
+| --- | -------- | -------------- | -------- |
+| Notifee intercepts iOS remote notification tap handlers, breaking RNFB `onNotificationOpenedApp` / `getInitialNotification` | iOS | [#912](https://github.com/invertase/notifee/issues/912) | 9.1.12 |
+| `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 |
+| `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 |
+| `SCHEDULE_EXACT_ALARM` denial silently drops scheduled alarms (no fallback) | Android | [#1100](https://github.com/invertase/notifee/issues/1100) | 9.1.12 |
+| `getNotificationSettings()` returns `DENIED` instead of `NOT_DETERMINED` on Android 13+ before permission requested | Android | [#1237](https://github.com/invertase/notifee/issues/1237) | 9.1.12 |
+| Default `AlarmType.SET_EXACT` doesn't work in Doze mode; `AlarmType.SET` uses `RTC` instead of `RTC_WAKEUP` | Android | [#961](https://github.com/invertase/notifee/issues/961) | 9.1.12 |
+| Foreground service crashes with ANR after ~3 min on Android 14+ (`shortService` timeout, missing `onTimeout()`) | Android | [#703](https://github.com/invertase/notifee/issues/703) | 9.1.13 |
+| Manifest merger failure when overriding `foregroundServiceType` on `ForegroundService` | Android | [#1108](https://github.com/invertase/notifee/issues/1108) | 9.1.13 |
+
+> **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
+> `AndroidManifest.xml`. This permission is auto-granted and not revocable, but Google Play
+> restricts its use to apps whose core function requires exact timing.
+> For all other apps, the library uses `SCHEDULE_EXACT_ALARM` with automatic fallback
+> to inexact alarms when the permission is not granted.
+
+See [CHANGELOG](https://github.com/marcocrupi/notifee/blob/main/CHANGELOG.md) for full details.
+
+## 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`:
+
+1. **Add the required permissions:**
 
-- **Reliable trigger notifications** — AlarmManager is the default backend instead of WorkManager, ensuring delivery even when the app is killed
-- **iOS remote notification fix** — new `setNotificationConfig()` API to prevent Notifee from intercepting Firebase Messaging tap handlers ([#912](https://github.com/invertase/notifee/issues/912))
-- **Android alarm fixes** — `goAsync()` in BroadcastReceivers, exact alarm fallback, Doze mode compatibility ([#1100](https://github.com/invertase/notifee/issues/1100), [#961](https://github.com/invertase/notifee/issues/961))
-- **Cold start fixes** — `getInitialNotification()` works correctly on both platforms ([#1128](https://github.com/invertase/notifee/issues/1128))
+   ```xml
+   <uses-permission android:name="android.permission.FOREGROUND_SERVICE" />
+   <!-- Replace SHORT_SERVICE with the type matching your use case -->
+   <uses-permission android:name="android.permission.FOREGROUND_SERVICE_SHORT_SERVICE" />
+   ```
+
+2. **Declare the service type on Notifee's ForegroundService:**
+
+   ```xml
+   <application ...>
+     <service
+       android:name="app.notifee.core.ForegroundService"
+       android:exported="false"
+       android:foregroundServiceType="shortService" />
+   </application>
+   ```
+
+Available types: `camera`, `connectedDevice`, `dataSync`, `health`, `location`, `mediaPlayback`, `mediaProjection`, `microphone`, `phoneCall`, `remoteMessaging`, `shortService`, `specialUse`, `systemExempted`. Choose the type that matches your use case — using the wrong type may cause Google Play policy violations.
+
+> **Note:** `shortService` has a 3-minute timeout on Android 14+. If your foreground service needs to run longer, use a different type. The library's `onTimeout()` handler will gracefully stop the service if the timeout fires.
+
+## Trigger Notification Reliability
+
+This fork defaults to AlarmManager for trigger notifications on Android, instead of WorkManager.
+This ensures scheduled notifications are delivered reliably even when the app is killed.
+
+The original Notifee used WorkManager by default, which is battery-friendly but unreliable
+for time-sensitive notifications — Android may defer or drop WorkManager tasks based on
+battery optimization, Doze mode, and OEM power management.
+
+If you need battery-friendly scheduling where exact timing is not critical (e.g., daily digest
+notifications), you can opt out:
+
+```typescript
+await notifee.createTriggerNotification(notification, {
+  type: TriggerType.TIMESTAMP,
+  timestamp: Date.now() + 60000,
+  alarmManager: false, // Uses WorkManager instead
+});
+```
+
+## New APIs
+
+### `setNotificationConfig` (iOS)
+
+Controls whether Notifee intercepts remote (push) notification tap events on iOS.
+When using React Native Firebase Messaging alongside Notifee, call this at app startup
+to let Firebase handle remote notification taps:
+
+```typescript
+import notifee from 'react-native-notify-kit';
+
+await notifee.setNotificationConfig({
+  ios: { handleRemoteNotifications: false },
+});
+```
+
+With `handleRemoteNotifications: false`:
+
+- Remote notifications (FCM) → handled by Firebase Messaging (`onNotificationOpenedApp`, `getInitialNotification`)
+- Local Notifee notifications → still handled by Notifee (unchanged)
+
+Default is `true` (backward compatible — Notifee handles everything, same as original Notifee behavior).
+
+### Android: `pressAction` required for tap handling
+
+On Android, notifications require a `pressAction` to open the app when tapped:
+
+```typescript
+await notifee.displayNotification({
+  title: 'Hello',
+  body: 'Tap to open',
+  android: {
+    channelId: 'default',
+    pressAction: { id: 'default', launchActivity: 'default' },
+  },
+});
+```
 
-See the full [CHANGELOG](https://github.com/marcocrupi/notifee/blob/main/CHANGELOG.md) and [README](https://github.com/marcocrupi/notifee#bugs-fixed-from-upstream-notifee) for details.
+Without `pressAction`, the notification will display but tapping it will do nothing.
+This is Android platform behavior, not a bug. iOS opens the app by default on tap.
 
 ## Documentation
 

package/android/libs/app/notifee/core/202108261754/core-202108261754.aar.md5

@@ -1 +1 @@
-92a6444c2c6acb894f8114d257d642c2
+03be2bd9ea6f1abab7409b008a68b22f

package/android/libs/app/notifee/core/202108261754/core-202108261754.aar.sha1

@@ -1 +1 @@
-bcaf285f6e2974c8d8e7005bb6aae61e9da6e8b7
+3c5d3fba5a39e0379492ccebf595780f1ca4b2bb

package/android/libs/app/notifee/core/202108261754/core-202108261754.aar.sha256

@@ -1 +1 @@
-abdf2235b5decafa866c977614e1a684cd0184e3cc08af31f406e20ee44e4923
+0adbd7ca46edd01d54d884368b4009a6725d71d84cb1cc390d0d69824cf4f4d8

package/android/libs/app/notifee/core/202108261754/core-202108261754.aar.sha512

@@ -1 +1 @@
-2c07293600a245e9f1366620f2745e6fda40e4bb77bec1fd262b0aa74fc7deecf1c6aa0ae7b56b1ca2a85e0bf1a46690be1619d4ed1d9bbaf59cd84c40413099
+47b1f9afbe975069248b988c23d5e693c7aed936016041e259c53180d29f37b8366d68c854f268bfc1b091e0bda4f47931d7814f092c0a9a37b76896e7017d3e

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

@@ -8,6 +8,6 @@
     <versions>
       <version>202108261754</version>
     </versions>
-    <lastUpdated>20260405104736</lastUpdated>
+    <lastUpdated>20260405202849</lastUpdated>
   </versioning>
 </metadata>

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

@@ -1 +1 @@
-c313005fb95a7f74adb2ab4a7d965a84
+642689e0ae7e377ba7c0b81eea65b251

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

@@ -1 +1 @@
-0d0abfdcd79dd71d19a57ef2e11a6a9f15c5bfdf
+5cca9a43a4a3ec1ef1fea9eb4f7f539845698d6c

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

@@ -1 +1 @@
-bf0ca1fdb6cf65587d3a9c53b1bfdec388dfa3f54c13e5f10bd51d65aca40dad
+23cbe0485817c9c413e87c45aec0a27a770fd63942baca688b482f819bc97fb6

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

@@ -1 +1 @@
-ba064764bf62e099f544cdee6c6c0fe600b47c77284d82f3dbf14f2a9c87bfc9aed016d0cb05be1efc872bdaa8999fa3372710eb31bd4325e0ec0fffee5fb3be
+5794011b4c59116e983c15137b9a08db00585e3a0771d55af89e5abcca04a76770f83cc73fe30a3ca25bf4e23d8ea9e7834e86516b632c68994979c893b99062

package/android/src/main/kotlin/io/invertase/notifee/NotifeeEventSubscriber.kt

@@ -45,6 +45,12 @@ class NotifeeEventSubscriber : EventListener {
             extras.getString(KEY_DETAIL_INPUT)?.let { input ->
                 eventDetailMap.putString(KEY_DETAIL_INPUT, input)
             }
+            if (extras.containsKey("startId")) {
+                eventDetailMap.putInt("startId", extras.getInt("startId"))
+            }
+            if (extras.containsKey("fgsType")) {
+                eventDetailMap.putInt("fgsType", extras.getInt("fgsType"))
+            }
         }
 
         eventMap.putMap(KEY_DETAIL, eventDetailMap)

package/dist/version.d.ts

@@ -1 +1 @@
-export declare const version = "9.1.12";
+export declare const version = "9.1.13";

package/dist/version.js

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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "react-native-notify-kit",
-  "version": "9.1.12",
+  "version": "9.1.13",
   "author": "Marco Crupi",
   "description": "React Native Notify Kit - a feature rich notifications library for React Native.",
   "main": "dist/index.js",

package/src/version.ts

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