forked from trent_larson/crowd-funder-for-time-pwa
docs: mark daily-notification Android receiver issue as resolved
Plugin fix is in @timesafari/daily-notification-plugin (explicit PendingIntent component + id in Intent). Document resolution date, summary of the fix, and follow-up steps (npm install, cap sync, restore-local-plugins, test on device).
This commit is contained in:
@@ -1,13 +1,30 @@
|
||||
# Daily Notification Plugin - Android Receiver Not Triggered by AlarmManager
|
||||
|
||||
**Date**: 2026-02-02
|
||||
**Status**: 🔴 Critical Bug - Alarms Fire But Receiver Not Triggered
|
||||
**Status**: ✅ Resolved (2026-02-06)
|
||||
**Plugin**: @timesafari/daily-notification-plugin
|
||||
**Platform**: Android
|
||||
**Issue**: AlarmManager fires alarms but DailyNotificationReceiver is not receiving broadcasts
|
||||
|
||||
---
|
||||
|
||||
## Resolution (2026-02-06)
|
||||
|
||||
The bug was fixed in the plugin repository. The plugin now:
|
||||
|
||||
- Creates the PendingIntent with the receiver component explicitly set (`setComponent(ComponentName(context, DailyNotificationReceiver::class.java))`), so AlarmManager delivers the broadcast to the receiver.
|
||||
- Adds the schedule ID to the Intent extras (`intent.putExtra("id", scheduleId)`), resolving the `missing_id` error.
|
||||
|
||||
**In this app after pulling the fix:**
|
||||
|
||||
1. Run `npm install` to get the latest plugin from `#master`.
|
||||
2. Run `npx cap sync` so the Android (and iOS) native projects get the updated plugin code.
|
||||
3. Run `node scripts/restore-local-plugins.js` if you use local plugins (e.g. SafeArea, SharedImage).
|
||||
4. Rebuild and run on Android, then verify using the [Testing Steps for Plugin Fix](#testing-steps-for-plugin-fix) below.
|
||||
</think>
|
||||
|
||||
---
|
||||
|
||||
## Problem Summary
|
||||
|
||||
Alarms are being scheduled successfully and fire at the correct time, but the `DailyNotificationReceiver` is not being triggered when AlarmManager delivers the broadcast. Manual broadcasts to the receiver work correctly, indicating the receiver itself is functional.
|
||||
|
||||
Reference in New Issue
Block a user