react-native-notify-kit 9.5.0 → 9.7.0

package/android/src/test/java/app/notifee/core/ForegroundServiceTest.java

@@ -1,11 +1,26 @@
 package app.notifee.core;
 
 import static org.junit.Assert.assertEquals;
+import static org.junit.Assert.assertNotNull;
+import static org.junit.Assert.assertNull;
 import static org.junit.Assert.assertTrue;
 import static org.junit.Assert.fail;
 
+import android.app.Notification;
+import android.app.NotificationChannel;
+import android.app.NotificationManager;
 import android.app.Service;
+import android.content.Context;
 import android.content.Intent;
+import android.content.pm.ServiceInfo;
+import android.os.Bundle;
+import androidx.core.app.NotificationCompat;
+import app.notifee.core.event.NotificationEvent;
+import java.lang.reflect.Field;
+import java.util.ArrayList;
+import java.util.List;
+import org.greenrobot.eventbus.Subscribe;
+import org.greenrobot.eventbus.ThreadMode;
 import org.junit.After;
 import org.junit.Before;
 import org.junit.Test;
@@ -26,12 +41,15 @@ public class ForegroundServiceTest {
   }
 
   @After
-  public void tearDown() {
-    // Reset all accessible static fields to prevent cross-test pollution.
-    // mCurrentNotificationBundle, mCurrentNotification, mCurrentHashCode are private static
-    // and can only be reset via onStartCommand (the STOP path clears them).
+  public void tearDown() throws Exception {
+    // Reset public and private static fields to prevent cross-test pollution. The three private
+    // statics are cleared via reflection here so that tests which seed them directly (to exercise
+    // onTimeout without running the full START path) cannot leak state into neighbouring tests.
     ForegroundService.mCurrentNotificationId = null;
     ForegroundService.mCurrentForegroundServiceType = -1;
+    setPrivateStatic("mCurrentNotificationBundle", null);
+    setPrivateStatic("mCurrentNotification", null);
+    setPrivateStatic("mCurrentHashCode", 0);
   }
 
   /**
@@ -179,4 +197,233 @@ public class ForegroundServiceTest {
     int result = service.onStartCommand(stopIntent, 0, 2);
     assertEquals(Service.START_STICKY_COMPATIBILITY, result);
   }
+
+  // ──────────────────────────────────────────────────────────────────────────
+  // START path and onTimeout event emission (regression guards for 9.1.13)
+  // ──────────────────────────────────────────────────────────────────────────
+
+  private static final String TEST_CHANNEL_ID = "fgs-test-channel";
+
+  /**
+   * START happy path: a valid intent with a notification payload must drive the service through
+   * {@code startForeground()} and leave {@code mCurrentNotificationId} populated so a subsequent
+   * STOP/onTimeout can reference it. Runs on SDK 33 to avoid the API 34+ manifest-type check, which
+   * would require a test-specific {@code foregroundServiceType} declaration.
+   */
+  @Test
+  @Config(sdk = 33)
+  public void onStartCommand_startIntent_setsCurrentNotificationIdAndCallsStartForeground()
+      throws Exception {
+    createChannel();
+    ServiceController<ForegroundService> controller =
+        Robolectric.buildService(ForegroundService.class);
+    ForegroundService service = controller.create().get();
+
+    String id = "fgs-start-happy";
+    int result =
+        service.onStartCommand(
+            buildStartIntent(id, id.hashCode()), /* flags= */ 0, /* startId= */ 1);
+
+    assertEquals(Service.START_NOT_STICKY, result);
+    assertEquals(id, ForegroundService.mCurrentNotificationId);
+    // Robolectric's ShadowService records the most recent Notification passed to
+    // startForeground(); a non-null result proves the 3-arg startForeground() overload on the
+    // API 33 branch of onStartCommand was exercised and Android's contract was satisfied.
+    Notification posted = org.robolectric.Shadows.shadowOf(service).getLastForegroundNotification();
+    assertNotNull("startForeground() must have been called during the START path", posted);
+    // The private static mCurrentHashCode tracks the caller-supplied hash; verifying it via
+    // reflection proves the START branch fully ran (not just the early-return path).
+    Field hashField = ForegroundService.class.getDeclaredField("mCurrentHashCode");
+    hashField.setAccessible(true);
+    assertEquals(id.hashCode(), hashField.getInt(null));
+  }
+
+  /**
+   * Regression guard for the 9.1.13 {@code onTimeout(int)} fix (upstream invertase/notifee#703). On
+   * API 34, Android's single-argument {@code onTimeout} fires when a {@code shortService} FGS
+   * exceeds its 3-minute budget. The handler must:
+   *
+   * <ol>
+   *   <li>emit a {@link NotificationEvent} with type {@link NotificationEvent#TYPE_FG_TIMEOUT},
+   *   <li>carry the originating notification model so JS can correlate the event,
+   *   <li>populate {@code startId} and {@code fgsType} extras (the latter is {@code -1} as a
+   *       sentinel on the single-argument variant), and
+   *   <li>reset the service's static tracking state.
+   * </ol>
+   */
+  @Test
+  @Config(sdk = 34)
+  public void onTimeout_api34_emitsFgTimeoutEventWithStartIdAndSentinelFgsType() throws Exception {
+    ServiceController<ForegroundService> controller =
+        Robolectric.buildService(ForegroundService.class);
+    ForegroundService service = controller.create().get();
+
+    String id = "fgs-timeout-api34";
+    seedActiveForegroundServiceState(id);
+
+    FgsEventCapture capture = new FgsEventCapture();
+    EventBus.register(capture);
+    try {
+      int startId = 42;
+      service.onTimeout(startId);
+
+      assertEquals(
+          "exactly one NotificationEvent should be emitted on timeout", 1, capture.events.size());
+      NotificationEvent event = capture.events.get(0);
+      assertEquals(NotificationEvent.TYPE_FG_TIMEOUT, event.getType());
+      assertNotNull(
+          "timeout event must carry the originating notification", event.getNotification());
+      assertEquals(id, event.getNotification().getId());
+      assertNotNull("timeout event must carry startId/fgsType extras", event.getExtras());
+      assertEquals(startId, event.getExtras().getInt("startId"));
+      // handleTimeout is called with -1 as the fgsType sentinel from the single-argument overload.
+      assertEquals(-1, event.getExtras().getInt("fgsType"));
+    } finally {
+      EventBus.unregister(capture);
+    }
+
+    assertNull(
+        "mCurrentNotificationId must be cleared after onTimeout",
+        ForegroundService.mCurrentNotificationId);
+    assertEquals(-1, ForegroundService.mCurrentForegroundServiceType);
+  }
+
+  /**
+   * Regression guard for the API 35+ {@code onTimeout(int, int)} overload, which supersedes the
+   * single-argument variant and surfaces the type-specific timeout cause (e.g. {@code
+   * FOREGROUND_SERVICE_TYPE_DATA_SYNC}'s new Android 15 cumulative cap). The emitted event must
+   * carry the explicit {@code fgsType} value, not the sentinel.
+   */
+  @Test
+  @Config(sdk = 35)
+  public void onTimeout_api35_emitsFgTimeoutEventWithExplicitFgsType() throws Exception {
+    ServiceController<ForegroundService> controller =
+        Robolectric.buildService(ForegroundService.class);
+    ForegroundService service = controller.create().get();
+
+    String id = "fgs-timeout-api35";
+    seedActiveForegroundServiceState(id);
+
+    FgsEventCapture capture = new FgsEventCapture();
+    EventBus.register(capture);
+    try {
+      int startId = 7;
+      int fgsType = ServiceInfo.FOREGROUND_SERVICE_TYPE_DATA_SYNC;
+      service.onTimeout(startId, fgsType);
+
+      assertEquals(1, capture.events.size());
+      NotificationEvent event = capture.events.get(0);
+      assertEquals(NotificationEvent.TYPE_FG_TIMEOUT, event.getType());
+      assertEquals(id, event.getNotification().getId());
+      assertNotNull(event.getExtras());
+      assertEquals(startId, event.getExtras().getInt("startId"));
+      assertEquals(fgsType, event.getExtras().getInt("fgsType"));
+    } finally {
+      EventBus.unregister(capture);
+    }
+
+    assertNull(ForegroundService.mCurrentNotificationId);
+    assertEquals(-1, ForegroundService.mCurrentForegroundServiceType);
+  }
+
+  /**
+   * Defensive behaviour: if onTimeout fires on a service instance whose static state has already
+   * been cleared (a race between STOP and the Android system delivering a delayed timeout), the
+   * handler must not crash and must not post a stray event.
+   */
+  @Test
+  @Config(sdk = 34)
+  public void onTimeout_withNoActiveState_doesNotCrashOrEmitEvent() {
+    ServiceController<ForegroundService> controller =
+        Robolectric.buildService(ForegroundService.class);
+    ForegroundService service = controller.create().get();
+
+    FgsEventCapture capture = new FgsEventCapture();
+    EventBus.register(capture);
+    try {
+      service.onTimeout(/* startId= */ 99);
+      assertEquals(0, capture.events.size());
+    } finally {
+      EventBus.unregister(capture);
+    }
+  }
+
+  // ──────────────────────────────────────────────────────────────────────────
+  // Helpers
+  // ──────────────────────────────────────────────────────────────────────────
+
+  private static void createChannel() {
+    Context context = RuntimeEnvironment.getApplication();
+    NotificationManager nm =
+        (NotificationManager) context.getSystemService(Context.NOTIFICATION_SERVICE);
+    if (nm != null && nm.getNotificationChannel(TEST_CHANNEL_ID) == null) {
+      NotificationChannel channel =
+          new NotificationChannel(
+              TEST_CHANNEL_ID, "FGS test channel", NotificationManager.IMPORTANCE_LOW);
+      nm.createNotificationChannel(channel);
+    }
+  }
+
+  private static Bundle buildNotificationBundle(String id) {
+    Bundle bundle = new Bundle();
+    bundle.putString("id", id);
+    bundle.putString("title", "FGS test " + id);
+    Bundle androidBundle = new Bundle();
+    androidBundle.putString("channelId", TEST_CHANNEL_ID);
+    bundle.putBundle("android", androidBundle);
+    return bundle;
+  }
+
+  private static Notification buildNotification() {
+    Context context = RuntimeEnvironment.getApplication();
+    return new NotificationCompat.Builder(context, TEST_CHANNEL_ID)
+        .setSmallIcon(android.R.drawable.ic_dialog_info)
+        .setContentTitle("FGS test")
+        .build();
+  }
+
+  private static Intent buildStartIntent(String id, int hashCode) {
+    Intent intent = new Intent();
+    intent.setAction(ForegroundService.START_FOREGROUND_SERVICE_ACTION);
+    intent.putExtra("hashCode", hashCode);
+    intent.putExtra("notification", buildNotification());
+    intent.putExtra("notificationBundle", buildNotificationBundle(id));
+    return intent;
+  }
+
+  /**
+   * Populates the service's private static tracking fields directly, simulating the post-START
+   * state that onTimeout expects to observe. Using reflection here (rather than running a full
+   * START first) keeps the onTimeout tests SDK-independent — the START path would trip the API 34+
+   * manifest-type check, but onTimeout itself is sdk-agnostic because its body only uses pre-API-34
+   * primitives.
+   */
+  private static void seedActiveForegroundServiceState(String id) throws Exception {
+    ForegroundService.mCurrentNotificationId = id;
+    ForegroundService.mCurrentForegroundServiceType = 1;
+    setPrivateStatic("mCurrentNotificationBundle", buildNotificationBundle(id));
+    setPrivateStatic("mCurrentNotification", buildNotification());
+    setPrivateStatic("mCurrentHashCode", id.hashCode());
+  }
+
+  private static void setPrivateStatic(String name, Object value) throws Exception {
+    Field field = ForegroundService.class.getDeclaredField(name);
+    field.setAccessible(true);
+    field.set(null, value);
+  }
+
+  /**
+   * greenrobot EventBus subscriber that records every {@link NotificationEvent} posted during a
+   * test. {@link ThreadMode#POSTING} fires the subscriber synchronously on the caller thread, so
+   * the test can inspect {@code events} immediately after {@code post()} returns without any looper
+   * advancement.
+   */
+  public static class FgsEventCapture {
+    final List<NotificationEvent> events = new ArrayList<>();
+
+    @Subscribe(threadMode = ThreadMode.POSTING)
+    public void onNotificationEvent(NotificationEvent event) {
+      events.add(event);
+    }
+  }
 }

package/android/src/test/java/app/notifee/core/GetDisplayedNotificationsDataTest.java

@@ -0,0 +1,242 @@
+package app.notifee.core;
+
+/*
+ * Copyright (c) 2016-present Invertase Limited & Contributors
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this library except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ *   http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+import static org.junit.Assert.assertEquals;
+import static org.junit.Assert.assertFalse;
+import static org.junit.Assert.assertNotNull;
+import static org.junit.Assert.assertTrue;
+
+import android.os.Bundle;
+import java.util.Arrays;
+import java.util.HashSet;
+import java.util.Set;
+import org.junit.Test;
+import org.junit.runner.RunWith;
+import org.robolectric.RobolectricTestRunner;
+
+/**
+ * Unit tests for {@link NotificationManager#shouldIncludeInData(String)} and {@link
+ * NotificationManager#extractDataFromExtras(android.os.Bundle)} — the denylist filter and
+ * bundle-to-bundle helper added for upstream invertase/notifee#393.
+ *
+ * <p>The end-to-end {@code getDisplayedNotifications()} path is intentionally not exercised here
+ * because it depends on {@code android.app.NotificationManager.getActiveNotifications()}, which
+ * would require a system service mock. Extracting the pure predicate and the extras iteration into
+ * helper methods lets these tests run under Robolectric with a real {@link Bundle} implementation
+ * and no system service at all.
+ */
+@RunWith(RobolectricTestRunner.class)
+public class GetDisplayedNotificationsDataTest {
+
+  // -------- shouldIncludeInData (pure predicate) --------
+
+  @Test
+  public void shouldIncludeInData_plainKey_returnsTrue() {
+    assertTrue(NotificationManager.shouldIncludeInData("event"));
+    assertTrue(NotificationManager.shouldIncludeInData("userId"));
+    assertTrue(NotificationManager.shouldIncludeInData("conversation_id"));
+  }
+
+  @Test
+  public void shouldIncludeInData_androidPrefix_returnsFalse() {
+    assertFalse(NotificationManager.shouldIncludeInData("android.title"));
+    assertFalse(NotificationManager.shouldIncludeInData("android.text"));
+  }
+
+  @Test
+  public void shouldIncludeInData_androidLookalike_returnsTrue() {
+    // The `android.` prefix intentionally includes the dot, so custom keys that
+    // merely begin with the substring `android` are not accidentally filtered.
+    assertTrue(NotificationManager.shouldIncludeInData("androidify"));
+    assertTrue(NotificationManager.shouldIncludeInData("androidish"));
+  }
+
+  @Test
+  public void shouldIncludeInData_googlePrefix_returnsFalse() {
+    assertFalse(NotificationManager.shouldIncludeInData("google.sent_time"));
+    assertFalse(NotificationManager.shouldIncludeInData("google.delivered_priority"));
+  }
+
+  @Test
+  public void shouldIncludeInData_googleLookalike_returnsTrue() {
+    // Same reasoning as androidLookalike — `google.` with dot keeps the filter precise.
+    assertTrue(NotificationManager.shouldIncludeInData("googleish"));
+    assertTrue(NotificationManager.shouldIncludeInData("googlebot"));
+  }
+
+  @Test
+  public void shouldIncludeInData_gcmPrefix_returnsFalse() {
+    assertFalse(NotificationManager.shouldIncludeInData("gcm.notification.foo"));
+    assertFalse(NotificationManager.shouldIncludeInData("gcm.n.e"));
+  }
+
+  @Test
+  public void shouldIncludeInData_notifeePrefix_returnsFalse() {
+    // "notifee.notification" and "notifee.trigger" are the current internal
+    // constants (EXTRA_NOTIFEE_NOTIFICATION / EXTRA_NOTIFEE_TRIGGER). They
+    // are caught by the no-dot `notifee` prefix.
+    assertFalse(NotificationManager.shouldIncludeInData("notifee.notification"));
+    assertFalse(NotificationManager.shouldIncludeInData("notifee.trigger"));
+
+    // `notifee` is INTENTIONALLY kept without the dot: the library reserves
+    // its own namespace entirely, so `notifeeFoo` is also filtered. This
+    // differs from `fcm.` (with dot, see below): for `notifee` the whole
+    // prefix is library-owned and can collide with future internal constants,
+    // whereas `fcm` is a third-party namespace where we prefer to let
+    // realistic user keys like `fcmRegion` or `fcmToken` survive.
+    assertFalse(NotificationManager.shouldIncludeInData("notifeeFoo"));
+  }
+
+  @Test
+  public void shouldIncludeInData_fcmDottedPrefix_returnsFalse() {
+    // `fcm.` uses the trailing dot so realistic user custom keys (fcmRegion,
+    // fcmToken, fcmlike) can round-trip through `data`. This diverges from
+    // iOS parseDataFromUserInfo:, which uses bare `[key hasPrefix:@"fcm"]`
+    // specifically to catch `fcm_options` (see the `// fcm_options` marker
+    // at NotifeeCoreUtil.m:627-628 and the dedicated
+    // shouldIncludeInData_fcmOptionsExactKey_returnsFalse test above). Both
+    // platforms drop `fcm_options`; Android additionally preserves bare-fcm
+    // user keys (fcmRegion, fcmToken, …) that iOS drops as collateral.
+    assertFalse(NotificationManager.shouldIncludeInData("fcm.notification"));
+    assertFalse(NotificationManager.shouldIncludeInData("fcm.foo"));
+  }
+
+  @Test
+  public void shouldIncludeInData_fcmLookalike_returnsTrue() {
+    // These survive the Android filter. They would NOT survive the iOS
+    // filter, which is an accepted cross-platform divergence in favor of
+    // preserving realistic user data on Android. Note: `fcm_options` is a
+    // deliberate EXCEPTION to this rule — see the dedicated test
+    // shouldIncludeInData_fcmOptionsExactKey_returnsFalse below.
+    assertTrue(NotificationManager.shouldIncludeInData("fcm"));
+    assertTrue(NotificationManager.shouldIncludeInData("fcmlike"));
+    assertTrue(NotificationManager.shouldIncludeInData("fcmRegion"));
+    assertTrue(NotificationManager.shouldIncludeInData("fcmToken"));
+  }
+
+  @Test
+  public void shouldIncludeInData_fcmOptionsExactKey_returnsFalse() {
+    // `fcm_options` is the Firebase HTTP v1 Message.fcm_options analytics
+    // label. On iOS it is caught by the bare `[key hasPrefix:@"fcm"]` filter
+    // in NotifeeCoreUtil.m:627-628, which has an inline `// fcm_options`
+    // comment documenting that the whole reason the iOS prefix is bare (not
+    // dotted) is specifically to drop this key. On Android we switched the
+    // prefix to `fcm.` (with dot) so realistic user keys like `fcmRegion`
+    // can survive — but that alone would leak `fcm_options`. This test
+    // guards the exact-match entry in EXCLUDED_DATA_KEYS that restores
+    // parity with iOS for the one Firebase-reserved bare-`fcm` key.
+    assertFalse(NotificationManager.shouldIncludeInData("fcm_options"));
+  }
+
+  @Test
+  public void shouldIncludeInData_exactKeyBlocklist_returnsFalse() {
+    assertFalse(NotificationManager.shouldIncludeInData("from"));
+    assertFalse(NotificationManager.shouldIncludeInData("collapse_key"));
+    assertFalse(NotificationManager.shouldIncludeInData("message_type"));
+    assertFalse(NotificationManager.shouldIncludeInData("message_id"));
+    assertFalse(NotificationManager.shouldIncludeInData("aps"));
+  }
+
+  @Test
+  public void shouldIncludeInData_nullKey_returnsFalse() {
+    assertFalse(NotificationManager.shouldIncludeInData(null));
+  }
+
+  // -------- extractDataFromExtras (bundle → bundle) --------
+
+  @Test
+  public void extractDataFromExtras_nullExtras_returnsEmptyBundle() {
+    Bundle result = NotificationManager.extractDataFromExtras(null);
+    assertNotNull(result);
+    assertEquals(0, result.size());
+  }
+
+  @Test
+  public void extractDataFromExtras_emptyExtras_returnsEmptyBundle() {
+    Bundle result = NotificationManager.extractDataFromExtras(new Bundle());
+    assertNotNull(result);
+    assertEquals(0, result.size());
+  }
+
+  @Test
+  public void extractDataFromExtras_mixedKeys_returnsOnlyCustomKeys() {
+    Bundle extras = new Bundle();
+
+    // Custom keys that should survive the filter.
+    extras.putString("event", "chat_msg");
+    extras.putString("userId", "42");
+
+    // System keys that must be dropped.
+    extras.putString("android.title", "Hello");
+    extras.putString("android.text", "Body");
+    extras.putString("google.sent_time", "123456");
+    extras.putString("gcm.notification.e", "1");
+    extras.putString("from", "12345");
+    extras.putString("collapse_key", "do_not_collapse");
+    extras.putString("message_id", "msg-abc");
+    extras.putString("notifee.notification", "internal");
+    extras.putString("fcm.foo", "reserved-dotted");
+
+    // Custom key matching the iOS-divergent survivor pattern: `fcmRegion`
+    // must appear in the result on Android, even though iOS would drop it.
+    extras.putString("fcmRegion", "eu-west-1");
+
+    // Non-String value to verify toString() coercion for the rare survivor.
+    extras.putInt("count", 5);
+
+    Bundle result = NotificationManager.extractDataFromExtras(extras);
+    assertNotNull(result);
+
+    Set<String> expected = new HashSet<>(Arrays.asList("event", "userId", "fcmRegion", "count"));
+    assertEquals(expected, result.keySet());
+    assertEquals("chat_msg", result.getString("event"));
+    assertEquals("42", result.getString("userId"));
+    assertEquals("eu-west-1", result.getString("fcmRegion"));
+    assertEquals("5", result.getString("count"));
+  }
+
+  @Test
+  public void extractDataFromExtras_onlySystemKeys_returnsEmptyBundle() {
+    Bundle extras = new Bundle();
+    extras.putString("android.title", "Hello");
+    extras.putString("google.sent_time", "123");
+    extras.putString("gcm.notification.foo", "bar");
+    extras.putString("notifee.trigger", "internal");
+    extras.putString("from", "12345");
+    extras.putString("fcm.options", "reserved-dotted");
+    // Firebase analytics label — exact-match filtered for iOS parity,
+    // see shouldIncludeInData_fcmOptionsExactKey_returnsFalse.
+    extras.putString("fcm_options", "{\"analytics_label\":\"foo\"}");
+
+    Bundle result = NotificationManager.extractDataFromExtras(extras);
+    assertNotNull(result);
+    assertEquals(0, result.size());
+  }
+
+  @Test
+  public void extractDataFromExtras_nullValueForCustomKey_isSkipped() {
+    Bundle extras = new Bundle();
+    extras.putString("event", "chat_msg");
+    extras.putString("nullable", null);
+
+    Bundle result = NotificationManager.extractDataFromExtras(extras);
+    assertNotNull(result);
+    assertEquals(1, result.size());
+    assertEquals("chat_msg", result.getString("event"));
+  }
+}

package/android/src/test/java/app/notifee/core/InitProviderBootCheckTest.java

@@ -0,0 +1,81 @@
+package app.notifee.core;
+
+/*
+ * Copyright (c) 2016-present Invertase Limited & Contributors
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this library except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ *   http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+import static org.junit.Assert.assertFalse;
+import static org.junit.Assert.assertTrue;
+
+import org.junit.Test;
+import org.junit.runner.RunWith;
+import org.robolectric.RobolectricTestRunner;
+
+/**
+ * Unit tests for the BOOT_COUNT-based cold-start reschedule decision logic added for upstream
+ * invertase/notifee#734. Exhaustively covers the pure decision helper {@link
+ * InitProvider#shouldRescheduleAfterBoot}.
+ *
+ * <p>The integration path {@code runBootCheck → rescheduleNotifications} is intentionally not
+ * exercised here because {@code rescheduleNotifications} touches a real Room database via {@code
+ * WorkDataRepository.getInstance}, which is not set up in this unit-test environment. That path is
+ * covered by the instrumented {@code RebootRecoveryTest} and by the manual Step 4 smoke test.
+ */
+@RunWith(RobolectricTestRunner.class)
+public class InitProviderBootCheckTest {
+
+  @Test
+  public void shouldRescheduleAfterBoot_firstRun_withValidBootCount_returnsFalse() {
+    // lastKnown == -1 means "no baseline recorded yet". We record the baseline
+    // and skip reschedule to avoid firing stale triggers on fresh installs.
+    assertFalse(InitProvider.shouldRescheduleAfterBoot(5, -1));
+  }
+
+  @Test
+  public void shouldRescheduleAfterBoot_sameBoot_returnsFalse() {
+    // Same app process, same device boot → nothing to recover.
+    assertFalse(InitProvider.shouldRescheduleAfterBoot(5, 5));
+  }
+
+  @Test
+  public void shouldRescheduleAfterBoot_newBoot_returnsTrue() {
+    // Reboot detected since last run → recover scheduled alarms.
+    assertTrue(InitProvider.shouldRescheduleAfterBoot(6, 5));
+  }
+
+  @Test
+  public void shouldRescheduleAfterBoot_bootCountDecreased_returnsTrue() {
+    // BOOT_COUNT decreasing is unexpected but possible (factory reset, counter
+    // rollover on exotic ROMs). Any change is treated as "unknown transition
+    // since last run" → conservative reschedule.
+    assertTrue(InitProvider.shouldRescheduleAfterBoot(3, 5));
+  }
+
+  @Test
+  public void shouldRescheduleAfterBoot_bootCountUnavailable_returnsTrue() {
+    // BOOT_COUNT couldn't be read → we can't tell if a reboot happened, so we
+    // reschedule conservatively. This also covers emulators and rooted ROMs
+    // where the Settings.Global row is missing or throws.
+    assertTrue(InitProvider.shouldRescheduleAfterBoot(-1, 5));
+  }
+
+  @Test
+  public void shouldRescheduleAfterBoot_bootCountUnavailable_andFirstRun_returnsTrue() {
+    // Degenerate case: first run AND BOOT_COUNT unavailable. The "unavailable"
+    // branch wins over the "first run" branch because we genuinely don't know
+    // if the device has rebooted since install.
+    assertTrue(InitProvider.shouldRescheduleAfterBoot(-1, -1));
+  }
+}