- DailyNotificationPlugin: strip SQLite init and writes; retain SharedPreferences path; Room storage remains authoritative
- DailyNotificationTTLEnforcer: remove SQLite reads/writes and DB constants; use SharedPreferences-only
- DailyNotificationMigration: make migration a no-op (legacy SQLite removed)
- DailyNotificationFetcher/Worker: write/read via Room; keep legacy SharedPreferences as fallback; guard removed API (type/vibration/storeLong) via reflection
- Room DAOs: add column aliases to match DTO fields
- Entities: add @Ignore to non-default constructors to silence Room warnings
Build fixes: resolve missing symbols and cursor mismatches after SQLite removal; align to current NotificationContent API.
Co-authored-by: Matthew Raymer
- DailyNotificationPlugin: inject Room storage into fetcher
- DailyNotificationFetcher: persist to Room first, mirror to legacy
- DailyNotificationWorker: read from Room, fallback to legacy; write next schedule to Room
Legacy SharedPreferences path deprecated; retained for transitional compatibility.
Co-authored-by: Matthew Raymer
Complete migration from SharedPreferences to Room database architecture:
**New Components:**
- NotificationContentEntity: Core notification data with encryption support
- NotificationDeliveryEntity: Delivery tracking and analytics
- NotificationConfigEntity: Configuration and user preferences
- NotificationContentDao: Comprehensive CRUD operations with optimized queries
- NotificationDeliveryDao: Delivery analytics and performance tracking
- NotificationConfigDao: Configuration management with type safety
- DailyNotificationDatabase: Room database with migration support
- DailyNotificationStorageRoom: High-level storage service with async operations
**Key Features:**
- Enterprise-grade data persistence with proper indexing
- Encryption support for sensitive notification content
- Automatic retention policy enforcement
- Comprehensive analytics and reporting capabilities
- Background thread execution for all database operations
- Migration support from SharedPreferences-based storage
- Plugin-specific database isolation and lifecycle management
**Architecture Documentation:**
- Complete ARCHITECTURE.md with comprehensive system design
- Database schema design with relationships and indexing strategy
- Security architecture with encryption and key management
- Performance architecture with optimization strategies
- Testing architecture with unit and integration test patterns
- Migration strategy from legacy storage systems
**Technical Improvements:**
- Plugin-specific database with proper entity relationships
- Optimized queries with performance-focused indexing
- Async operations using CompletableFuture for non-blocking UI
- Comprehensive error handling and logging
- Data validation and integrity enforcement
- Cleanup operations with configurable retention policies
This completes the high-priority storage hardening improvement, providing
enterprise-grade data management capabilities for the DailyNotification plugin.
Co-authored-by: Matthew Raymer
Critical Priority Improvements (Completed):
- Enhanced exact-time reliability for Doze & Android 12+ with setExactAndAllowWhileIdle
- Implemented DST-safe time calculation using Java 8 Time API to prevent notification drift
- Added comprehensive schema validation with Zod for all notification inputs
- Created Android 13+ permission UX with graceful fallbacks and education dialogs
High Priority Improvements (Completed):
- Implemented work deduplication and idempotence in DailyNotificationWorker
- Added atomic locks and completion tracking to prevent race conditions
- Enhanced error handling and logging throughout the notification pipeline
New Services Added:
- NotificationValidationService: Runtime schema validation with detailed error messages
- NotificationPermissionManager: Comprehensive permission handling with user education
Documentation Added:
- NOTIFICATION_STACK_IMPROVEMENT_PLAN.md: Complete implementation roadmap with checkboxes
- VUE3_NOTIFICATION_IMPLEMENTATION_GUIDE.md: Vue3 integration guide with code examples
This implementation addresses the most critical reliability and user experience issues
identified in the notification stack analysis, providing a solid foundation for
production-ready notification delivery.
- Make all notifications clickable to open the app
- Use PackageManager.getLaunchIntentForPackage() for reliable app launch
- Add 'View Details' action button when URL is available
- Maintain existing 'Dismiss' action button for all notifications
- Enhanced logging for click intent and action button configuration
- Proper Intent flags for NEW_TASK and CLEAR_TOP behavior
Features:
- Tap notification body: Opens app (with URL data if available)
- Tap 'View Details': Opens URL in browser (if URL provided)
- Tap 'Dismiss': Dismisses notification and cancels future scheduling
Improves user experience with intuitive notification interactions.
- Add deduplication system to prevent double-firing of notifications
* Check existing notifications within 1-minute tolerance before scheduling
* Prevents duplicate notifications from receiver double-firing on some OEMs
* Structured logging: DN|RESCHEDULE_DUPLICATE, DN|SCHEDULE_DUPLICATE
- Implement WorkManager doze fallback system for deep doze scenarios
* DozeFallbackWorker runs 30 minutes before notification time
* Re-arms exact alarms if they get pruned during deep doze mode
* Battery-friendly constraints with no network requirement
* Structured logging: DN|DOZE_FALLBACK_SCHEDULED, DN|DOZE_FALLBACK_REARM_OK
- Add JIT soft re-fetch for borderline age content
* SoftRefetchWorker prefetches fresh content when content is 80% of TTL
* Runs 2 hours before tomorrow's notification for proactive freshness
* Asynchronous background processing with network constraints
* Structured logging: DN|JIT_BORDERLINE, DN|SOFT_REFETCH_SCHEDULED
- Enhance DailyNotificationWorker with comprehensive resilience features
* Ultra-lightweight receiver with WorkManager handoff
* DST-safe scheduling with ZonedDateTime calculations
* Storage capping and retention policy (100 entries, 14-day retention)
* Performance monitoring with StrictMode and Trace markers
- Add comprehensive status checking API
* NotificationStatusChecker provides unified permission/channel status
* Channel management with deep links to settings
* Exact alarm permission validation and guidance
All P1 features tested and working under system stress conditions.
Notification system now production-ready with full resilience suite.
- Add null checks and lazy initialization for scheduler in all plugin methods
- Prevents NullPointerException when methods called before load() completes
- Ensures scheduler is available for scheduleDailyNotification, scheduleDailyReminder, cancelDailyReminder, and updateDailyReminder
- Adds structured logging for scheduler initialization events
- Resolves critical runtime error under system stress conditions
Fixes: NullPointerException in DailyNotificationScheduler.scheduleNotification()
Tested: Notification system working correctly under stress with 45+ notifications
- Add PendingIntentManager class for proper PendingIntent handling
- Implement correct FLAG_UPDATE_CURRENT | FLAG_IMMUTABLE flags for Android 12+
- Add comprehensive exact alarm permission checking and handling
- Add fallback to windowed alarms when exact alarm permission denied
- Update DailyNotificationScheduler to use PendingIntentManager
- Add detailed alarm status reporting with Android version info
- Improve error handling for SecurityException on exact alarm scheduling
- Add comprehensive alarm status to checkStatus() method
P0 Priority Implementation:
- Fixes PendingIntent flags for modern Android compatibility
- Ensures exact alarm permissions are properly checked before scheduling
- Provides actionable error messages when exact alarm permission denied
- Adds fallback to windowed alarms for better reliability
- Improves alarm scheduling status reporting and debugging
This addresses the critical P0 issues with PendingIntent flags and
exact alarm permission handling for production reliability.
- Add ChannelManager class for notification channel management
- Implement channel existence checking and creation
- Add channel importance validation (guards against IMPORTANCE_NONE)
- Add deep link to channel settings when notifications are blocked
- Integrate channel manager into plugin load() method
- Add new plugin methods: isChannelEnabled(), openChannelSettings(), checkStatus()
- Add comprehensive status checking including permissions and channel state
- Add test app UI for channel management testing
P0 Priority Implementation:
- Guards against channel = NONE (blocked notifications)
- Provides actionable error messages with deep links to settings
- Ensures notifications can actually be delivered
- Comprehensive status checking for all notification requirements
This addresses the critical issue where notifications are scheduled
but silently dropped due to blocked notification channels.
- Remove echo() method from DailyNotificationPlugin.java
- Update Android test app to show 'Plugin is loaded and ready!' instead of echo test
- Update web test app to remove echo method call
- Update iOS test app to remove echo method call
- Update documentation to remove echo test references
- Replace echo test with simple plugin availability check
The echo test was only used for initial plugin verification and is no longer
needed since the plugin now has comprehensive notification functionality.
This simplifies the codebase and removes unnecessary test code.
- Remove setFetchTime() call as fetchedAt is now set in constructor
- Align with new immutable timestamp model
- Ensure consistent timestamp handling across all components
This completes the migration to the new timestamp model where
fetchedAt is immutable and set at object creation time.
- Remove setFetchTime() calls from DailyNotificationFetchWorker
- Remove setFetchTime() calls from DailyNotificationFetcher
- Update DailyNotificationMaintenanceWorker to use getFetchedAt()
- Update DailyNotificationMigration to use getFetchedAt()
- Align all classes with immutable fetchedAt timestamp approach
- Ensure consistent timestamp handling across the codebase
These changes support the new timestamp model where fetchedAt
is immutable and set at object creation time.
- Separate fetchedAt (immutable) and scheduledAt (mutable) timestamps
- Add custom JsonDeserializer to ensure fetchedAt is set by constructor
- Add transient fetchTime field for Gson compatibility
- Update TTL enforcer to use fetchedAt for freshness checks
- Increase DEFAULT_TTL_SECONDS to 25 hours for daily notifications
- Update storage to use custom Gson deserializer
- Add debug logging for timestamp validation
- Fix timestamp initialization in NotificationContent constructor
This resolves the TTL_VIOLATION error that was preventing
notifications from being scheduled due to stale timestamp data.
- Add ensureStorageInitialized() helper method for null safety
- Add storage initialization checks to all plugin methods
- Fix null pointer exception in scheduleDailyNotification()
- Add storage initialization to getLastNotification()
- Add storage initialization to cancelAllNotifications()
- Add storage initialization to updateSettings()
- Add storage initialization to setAdaptiveScheduling()
- Add storage initialization to checkAndPerformRecovery()
- Improve exact alarm permission handling with proper Settings intent
- Add comprehensive error handling for storage operations
This resolves the 'Attempt to invoke virtual method on null object'
error that was occurring when plugin methods were called before
storage initialization completed.
- Add android:exported="true" for API 31+ compatibility
- Add android:directBootAware="true" for Direct Boot handling
- Add LOCKED_BOOT_COMPLETED action for early boot recovery
- Remove PACKAGE_REPLACED action (not needed for our use case)
- Implement handleLockedBootCompleted() for Direct Boot safety
- Use device protected storage context for Direct Boot operations
- Add comprehensive logging for boot receiver events
This fixes Android 10+ boot receiver restrictions and ensures
notifications are restored after device reboots and app updates.
- Add full DailyNotificationPlugin with @CapacitorPlugin annotation
- Implement echo method for testing plugin connectivity
- Add comprehensive notification functionality with offline-first approach
- Include performance optimization and error handling classes
- Add WorkManager integration for background content fetching
- Plugin now ready for testing with Capacitor 6 registration
- Add capacitor.plugins.json with correct DailyNotification plugin entry
- Use 'classpath' field instead of 'classname' for Capacitor 6 compatibility
- Add annotation processor dependency to plugin build.gradle
- Plugin now successfully registers with Capacitor bridge
Fixes: PluginLoadException and plugin availability issues
Resolves: DailyNotification plugin not loading despite manual registration
- Create fix-capacitor-build.sh script to restore fixes after Capacitor operations
- Update build-native.sh to automatically apply fix when needed
- Add warnings to BUILDING.md about auto-generated file risks
- Document which Capacitor commands will overwrite manual fixes
This protects against losing the capacitor.build.gradle fix when running
npx cap sync, npx cap update, or other Capacitor CLI commands.
- Fix capacitor.build.gradle to comment out missing Capacitor integration file
- Create separate plugin module with proper build.gradle configuration
- Copy plugin source code to android/plugin/src/main/java/
- Update settings.gradle to include plugin module
- Fix plugin build.gradle to remove Kotlin plugin dependency
- Successfully build plugin AAR: android/plugin/build/outputs/aar/plugin-release.aar
- Update BUILDING.md with correct build commands and troubleshooting
This resolves the Android Studio build issues by creating a proper
plugin library module separate from the test app.
Matthew Raymer