This repository was archived by the owner on Apr 7, 2026. It is now read-only.
Description Bug report
Hello everyone and thanks to the authors for maintaining this lib.
[x] I've created a simple example to reproduce the issue.
Description
This bug occurs in versions 9.0.0 and 9.0.2, but is not present in version 7.8.2. The issue happens when a progress notification is triggered; 3 minutes after the notification is sent, the app crashes.
Steps to Reproduce
Clone the repository:
Install dependencies:
Run the project on an Android simulator:
Trigger the progress notification:
Wait for 3 minutes:
Expected Result: The app should continue to run normally.Actual Result: The app crashes automatically after 3 minutes.
Versions
Notifee : "^9.0.2"React Native : "0.72.10"Expo : "49.0.0"Node.js : "18.14.0"Android : "Android 14 - API 34"
Logs (adb)
09-26 07:53:33.982 210 210 I tombstoned: received crash request for pid 1346
09-26 07:53:33.982 210 210 I tombstoned: found intercept fd 512 for pid 1346 and type kDebuggerdJavaBacktrace
09-26 07:53:33.982 1346 1357 I ndroid.systemui: Wrote stack traces to tombstoned
09-26 07:53:33.982 210 210 W tombstoned: skipping tombstone file creation due to intercept
09-26 07:53:33.983 629 4750 I system_server: libdebuggerd_client: done dumping process 1346
09-26 07:53:33.984 629 4750 I ActivityManager: dumpStackTraces nativepids=null
09-26 07:53:33.984 629 4750 I ActivityManager: dumpStackTraces extraPids=[]
09-26 07:53:33.984 629 4750 I ActivityManager: Done dumping
09-26 07:53:33.984 629 4750 E ActivityManager: ANR in com.testnotifee.app
09-26 07:53:33.984 629 4750 E ActivityManager: PID: 4656
09-26 07:53:33.984 629 4750 E ActivityManager: Reason: A foreground service of FOREGROUND_SERVICE_TYPE_SHORT_SERVICE did not stop within a timeout: ComponentInfo{com.testnotifee.app/app.notifee.core.ForegroundService}
09-26 07:53:33.984 629 4750 E ActivityManager: ErrorId: 06ba5e89-7aa9-4c3c-b2d2-cd5a221ab3c9
09-26 07:53:33.984 629 4750 E ActivityManager: Frozen: false
09-26 07:53:33.984 629 4750 E ActivityManager: Load: 0.08 / 0.12 / 0.15
09-26 07:53:33.984 629 4750 E ActivityManager: ----- Output from /proc/pressure/memory -----
09-26 07:53:33.984 629 4750 E ActivityManager: some avg10=0.00 avg60=0.00 avg300=0.00 total=92019425
09-26 07:53:33.984 629 4750 E ActivityManager: full avg10=0.00 avg60=0.00 avg300=0.00 total=49140800
09-26 07:53:33.984 629 4750 E ActivityManager: ----- End output from /proc/pressure/memory -----
09-26 07:53:33.984 629 4750 E ActivityManager: ----- Output from /proc/pressure/cpu -----
09-26 07:53:33.984 629 4750 E ActivityManager: some avg10=0.22 avg60=0.22 avg300=0.29 total=1712746463
09-26 07:53:33.984 629 4750 E ActivityManager: full avg10=0.00 avg60=0.00 avg300=0.00 total=0
09-26 07:53:33.984 629 4750 E ActivityManager: ----- End output from /proc/pressure/cpu -----
09-26 07:53:33.984 629 4750 E ActivityManager: ----- Output from /proc/pressure/io -----
09-26 07:53:33.984 629 4750 E ActivityManager: some avg10=0.00 avg60=0.00 avg300=0.00 total=232649866
09-26 07:53:33.984 629 4750 E ActivityManager: full avg10=0.00 avg60=0.00 avg300=0.00 total=90749479
09-26 07:53:33.984 629 4750 E ActivityManager: ----- End output from /proc/pressure/io -----
09-26 07:53:33.984 629 4750 E ActivityManager:
09-26 07:53:33.984 629 4750 E ActivityManager: CPU usage from 176687ms to 0ms ago (2024-09-26 07:50:36.762 to 2024-09-26 07:53:33.449):
09-26 07:53:33.984 629 4750 E ActivityManager: 2.3% 4656/com.testnotifee.app: 1.8% user + 0.5% kernel / faults: 1787 minor 1 major
09-26 07:53:33.984 629 4750 E ActivityManager: 0.6% 393/surfaceflinger: 0.1% user + 0.4% kernel / faults: 53 minor 5 major
09-26 07:53:33.984 629 4750 E ActivityManager: 0.4% 629/system_server: 0.1% user + 0.3% kernel / faults: 1076 minor 33 major
09-26 07:53:33.984 629 4750 E ActivityManager: 0.4% 1346/com.android.systemui: 0.2% user + 0.2% kernel / faults: 2287 minor 50 major
09-26 07:53:33.984 629 4750 E ActivityManager: 0.2% 4729/kworker/0:1-virtio_vsock: 0% user + 0.2% kernel
09-26 07:53:33.984 629 4750 E ActivityManager: 0.1% 368/android.hardware.sensors-service.multihal: 0% user + 0.1% kernel
09-26 07:53:33.984 629 4750 E ActivityManager: 0% 376/android.hardware.graphics.composer3-service.ranchu: 0% user + 0% kernel / faults: 5 minor
09-26 07:53:33.984 629 4750 E ActivityManager: 0% 13/ksoftirqd/0: 0% user + 0% kernel
09-26 07:53:33.984 629 4750 E ActivityManager: 0% 1533/com.android.networkstack.process: 0% user + 0% kernel / faults: 356 minor
09-26 07:53:33.984 629 4750 E ActivityManager: 0% 1608/com.android.phone: 0% user + 0% kernel / faults: 173 minor
09-26 07:53:33.984 629 4750 E ActivityManager: 2.5% TOTAL: 0.7% user + 0.6% kernel + 0% iowait + 1.1% irq + 0% softirq
09-26 07:53:33.984 629 4750 E ActivityManager: CPU usage from 4ms to 270ms later (2024-09-26 07:53:33.453 to 2024-09-26 07:53:33.718):
09-26 07:53:33.984 629 4750 E ActivityManager: 52% 4656/com.testnotifee.app: 20% user + 32% kernel / faults: 41512 minor 190 major
09-26 07:53:33.984 629 4750 E ActivityManager: 56% 4662/Signal Catcher: 24% user + 32% kernel
09-26 07:53:33.984 629 4750 E ActivityManager: 19% 629/system_server: 7.8% user + 11% kernel / faults: 2816 minor 75 major
09-26 07:53:33.984 629 4750 E ActivityManager: 11% 653/Signal Catcher: 11% user + 0% kernel
09-26 07:53:33.984 629 4750 E ActivityManager: 3.9% 4751/AnrAuxiliaryTas: 0% user + 3.9% kernel
09-26 07:53:33.984 629 4750 E ActivityManager: 3.7% 13/ksoftirqd/0: 0% user + 3.7% kernel
09-26 07:53:33.984 629 4750 E ActivityManager: 30% TOTAL: 8.4% user + 12% kernel + 6.6% iowait + 2.8% irq
09-26 07:53:33.985 629 4750 D ActivityManager: Completed ANR of com.testnotifee.app in 536ms, latency 1ms
Reactions are currently unavailable
Bug report
Hello everyone and thanks to the authors for maintaining this lib.
[x] I've created a simple example to reproduce the issue.
Reproduced on:
Description
This bug occurs in versions 9.0.0 and 9.0.2, but is not present in version 7.8.2. The issue happens when a progress notification is triggered; 3 minutes after the notification is sent, the app crashes.
Steps to Reproduce
Ensure you have the latest version of the code by cloning the repository to your local machine.
Navigate to the project directory and install all necessary packages by running the appropriate package manager command (e.g., npm install or yarn install).
Use an Android emulator or a physical device to run the project by executing npm run android or yarn android or the equivalent command in your setup.
Within the app, locate and click the blue button to trigger the progress notification.
After triggering the notification, wait for approximately 3 minutes to observe the app's behavior.s.
Expected Result: The app should continue to run normally.
Actual Result: The app crashes automatically after 3 minutes.
Versions
Notifee: "^9.0.2"
React Native: "0.72.10"
Expo: "49.0.0"
Node.js: "18.14.0"
Android: "Android 14 - API 34"
Logs (adb)