Fix documentation to address Xcode behavior where 'Simulate Background
Fetch' menu item only appears when app is NOT running.
Changes:
- Add explicit note about Xcode menu item availability
- Prioritize LLDB command method when app is running (recommended)
- Document three methods: LLDB command, Xcode menu, and UI button
- Add troubleshooting section for common issues
- Update quick start section to reference LLDB method
- Explicitly reference test-apps/ios-test-app path for clarity
This resolves confusion when 'Simulate Background Fetch' disappears
from Debug menu while app is running. LLDB command method works reliably
in all scenarios.
Add iOS prefetch testing guide with detailed procedures, log checklists,
and behavior classification. Enhance iOS test app requirements with
security constraints, sign-off checklists, and changelog structure.
Update main directive with testing strategy and method behavior mapping.
Changes:
- Add IOS_PREFETCH_TESTING.md with simulator/device test plans, log
diagnostics, telemetry expectations, and test run templates
- Add DailyNotificationBackgroundTaskTestHarness.swift as reference
implementation for BGTaskScheduler testing
- Enhance IOS_TEST_APP_REQUIREMENTS.md with security/privacy constraints,
review checklists, CI hints, and glossary cross-links
- Update 0003-iOS-Android-Parity-Directive.md with testing strategy
section, method behavior classification, and validation matrix updates
All documents now include changelog stubs, cross-references, and
completion criteria for Phase 1 implementation and testing.
Fixed scheduleDailyNotification to read parameters directly from CAPPluginCall
(matching Android pattern) instead of looking for wrapped "options" object.
Improved BGTaskScheduler error handling to clearly indicate simulator limitations.
Changes:
- Read parameters directly from call (call.getString("time"), etc.) instead of
call.getObject("options") - Capacitor passes options object directly as call data
- Improved BGTaskScheduler error handling with clear simulator limitation message
- Added priority parameter extraction (was missing)
- Error handling doesn't fail notification scheduling if background fetch fails
BGTaskScheduler Simulator Limitation:
- BGTaskSchedulerErrorDomain Code=1 (notPermitted) is expected on simulator
- Background fetch scheduling fails on simulator but works on real devices
- Notification scheduling still works correctly; prefetch won't run on simulator
- Error messages now clearly indicate this is expected behavior
Result: scheduleDailyNotification now works correctly. Notification scheduling
verified working on simulator. Background fetch error is expected and documented.
Files modified:
- ios/Plugin/DailyNotificationPlugin.swift: Parameter reading fix, error handling
- doc/directives/0003-iOS-Android-Parity-Directive.md: Implementation details documented
Capacitor iOS was not discovering DailyNotificationPlugin because it did not
conform to the CAPBridgedPlugin protocol required for runtime discovery.
Changes:
- Add @objc extension to DailyNotificationPlugin implementing CAPBridgedPlugin
with identifier, jsName, and pluginMethods properties
- Force-load plugin framework in AppDelegate before Capacitor initializes
- Remove duplicate BGTaskScheduler registration from AppDelegate (plugin handles it)
- Update podspec to use dynamic framework (static_framework = false)
- Add diagnostic logging to verify plugin discovery
Result: Plugin is now discovered by Capacitor and all methods are accessible
from JavaScript. Verified working with checkPermissionStatus() method.
Files modified:
- ios/Plugin/DailyNotificationPlugin.swift: Added CAPBridgedPlugin extension
- test-apps/ios-test-app/ios/App/App/AppDelegate.swift: Force-load + diagnostics
- ios/DailyNotificationPlugin.podspec: Dynamic framework setting
- doc/directives/0003-iOS-Android-Parity-Directive.md: Documented solution
- Update integration checklist with Phase 8 and Phase 9 completion
- Mark audit status as PASSED with comprehensive implementation
- Update all phase completion statuses
- Add native-first architecture documentation
- Update platform support to reflect current implementation
- Add comprehensive observability and compliance documentation
- Mark all integration phases as complete
Audit Status: ✅ PASSED - 2025-10-08 06:08:15 UTC
All phases complete: Package prep, dependencies, architecture, build system,
platform config, service integration, testing, documentation, observability
- Update STARRED_PROJECTS_POLLING_IMPLEMENTATION.md to version 2.0.0
- Introduce structured request/response polling system architecture
- Add GenericPollingRequest interface for host app-defined schemas
- Implement PollingScheduleConfig with cron-based scheduling
- Add comprehensive idempotency enforcement with X-Idempotency-Key
- Include unified backoff policy with Retry-After + jittered exponential caps
- Document watermark CAS (Compare-and-Swap) for race condition prevention
- Add outbox pressure controls with back-pressure and eviction strategies
- Include telemetry budgets with low-cardinality metrics and PII redaction
- Document clock synchronization with skew tolerance and JWT validation
- Add platform-specific implementations (Android WorkManager, iOS BGTaskScheduler, Web Service Workers)
- Include host app usage examples and integration patterns
- Add ready-to-merge checklist and acceptance criteria for MVP
This redesign provides maximum flexibility while maintaining cross-platform consistency.
- Added explicit coverage for activeDid-aware retry policy enhancements
- Specified Android DailyNotificationFetchWorker.java modifications for activeDid change detection
- Specified web callback-registry.ts enhancements for authentication refresh
- Added platform policy unification (android 1min→1hour vs web 1sec→1min standardization)
- Added integration with existing circuit breaker and error handling systems
This addresses the gap where scheduled event retry enhancements were only
mentioned at high level but lacked specific implementation steps.
- Added Current Implementation Baseline section documenting existing functionality
- Updated authentication examples to enhance existing DailyNotificationETagManager.java
- Modified HTTP request implementation to extend existing DailyNotificationFetcher.java
- Updated plugin interface to extend current DailyNotificationPlugin rather than replace
- Corrected implementation phases to build upon existing infrastructure:
* Phase 1: Extend core infrastructure (not rebuild)
* Phase 2: Add activeDid integration to existing methods
* Phase 3: Enhance existing background integration
* Phase 4: Add TimeSafari-specific features
- Updated Android examples to show enhancement of existing SQLite + SharedPreferences
- Updated Web examples to enhance existing IndexedDB (no host delegation initially)
- Changed status from 'implementation plan' to 'enhancement plan for existing implementation'
- Aligned dependencies with existing plugin infrastructure rather than new requirements
The plan now accurately reflects building upon our working plugin instead of
rebuilding from scratch, providing a realistic enhancement roadmap.
- Consolidated DATABASE_ACCESS_CLARIFICATION.md content into main plan
- Consolidated ACTIVE_DID_CHANGE_REQUIREMENTS.md content into main plan
- Consolidated TIMESAFARI_INTEGRATION_ANALYSIS.md content into main plan
- Enhanced main document with Option A architecture overview
- Added comprehensive TimeSafari integration patterns section
- Added critical requirement section for activeDid change detection
- Added event-based solution implementation details
- Updated README.md to reference single consolidated document
- Eliminated unnecessary document proliferation as requested
The BACKGROUND_DATA_FETCHING_PLAN.md now serves as the single source of truth
for all implementation guidance, containing Option A architecture, TimeSafari
integration patterns, activeDid change management, and platform-specific details.
- Added critical requirement that plugin MUST be notified of activeDid changes
- Enhanced plugin interface with onActiveDidChange() callback method
- Added clearCacheForNewIdentity() and refreshAuthenticationForNewIdentity() methods
- Updated integration examples to include activeDid change listeners
- Created comprehensive ActiveDid change requirements document covering:
* Security implications of not detecting changes
* Event-based notification pattern implementation
* Cache clearing and authentication refresh requirements
* Testing scenarios for identity switching
* Platform-specific considerations and edge cases
* Performance optimization for rapid identity changes
This addresses the critical data integrity and security requirement that the plugin
must know when TimeSafari users switch identities to prevent data leakage.
- Simplified authentication to use single activeDid instead of complex user management
- Updated plugin interface to require only setActiveDid() method
- Modified API requests to use activeDid as both issuer and recipient
- Streamlined configuration to activeDid: string instead of complex credential object
- Aligned JWT generation with simple DID-based authentication pattern
- Reduced complexity while maintaining security through DID signing
This assumption significantly simplifies the host application integration.
- Document native HTTP client implementation for Android/iOS
- Include JWT authentication strategies (Basic DID + Advanced Passkey)
- Detail API endpoint integration with TimeSafari/Endorser.ch patterns
- Cover error handling, caching, and performance optimization
- Provide migration phases and testing strategies
- Include platform-specific considerations and success criteria
This plan replaces web push implementations with native solutions
for reliable background data fetching across all target platforms.
- Add UI_REQUIREMENTS.md with detailed UI component specifications
- Add ui-integration-examples.ts with ready-to-use UI components
- Document all required UI elements for plugin integration
- Include platform-specific UI components (Android/iOS/Web)
- Provide complete implementation examples with TypeScript
- Add responsive design guidelines and accessibility requirements
- Include error handling and status monitoring UI components
- Update README.md to reference new UI documentation
UI Components Covered:
✅ Permission management dialogs and status displays
✅ Configuration panels for settings and preferences
✅ Status dashboards with real-time monitoring
✅ Platform-specific components (battery optimization, background refresh)
✅ Error handling and recovery UI
✅ Testing and debug components
✅ Complete integration examples with event handling
- Add VERIFICATION_REPORT.md with detailed analysis of closed-app requirements
- Add VERIFICATION_CHECKLIST.md for regular verification process
- Update README.md to reference verification documentation
- Document all test scenarios and platform-specific implementations
- Include performance metrics and security considerations
- Define quarterly verification schedule and success criteria
The verification report confirms the plugin meets all requirements:
✅ Local notifications from device database
✅ Data populated by scheduled network fetches
✅ Works when app is closed
✅ TTL enforcement and error handling
✅ Cross-platform support with platform optimizations
- Add complete SQLite schema with Room database (content_cache, schedules, callbacks, history)
- Implement WorkManager FetchWorker with exponential backoff and network constraints
- Add AlarmManager NotifyReceiver with TTL-at-fire logic and notification delivery
- Create BootReceiver for automatic rescheduling after device reboot
- Update AndroidManifest.xml with necessary permissions and receivers
- Add Room, WorkManager, and Kotlin coroutines dependencies to build.gradle
feat(callback-registry)!: implement callback registry with circuit breaker
- Add CallbackRegistryImpl with HTTP, local, and queue callback support
- Implement circuit breaker pattern with exponential backoff retry logic
- Add CallbackEvent interface with structured event types
- Support for exactly-once delivery semantics with retry queue
- Include callback status monitoring and health checks
feat(observability)!: add comprehensive observability and health monitoring
- Implement ObservabilityManager with structured logging and event codes
- Add performance metrics tracking (fetch, notify, callback times)
- Create health status API with circuit breaker monitoring
- Include log compaction and metrics reset functionality
- Support for DNP-* event codes throughout the system
feat(web)!: enhance web implementation with new functionality
- Integrate callback registry and observability into web platform
- Add mock implementations for dual scheduling methods
- Implement performance tracking and structured logging
- Support for local callback registration and management
- Enhanced error handling and event logging
BREAKING CHANGE: New Android dependencies require Room, WorkManager, and Kotlin coroutines
- Updated directive to accurately reflect Phase 1 completion
- Added status indicators (✅ COMPLETE, 🔄 NEXT PHASE, ❌ NOT IMPLEMENTED)
- Documented current implementation vs pending requirements
- Added summary section for model comparison
- Clarified 85% consistency with perfect API alignment
- Identified next phase: platform-specific implementation
BREAKING CHANGE: Directive now reflects actual codebase state
rather than aspirational requirements
- Reduced from 688 lines to 157 lines (77% reduction)
- Maintained all essential information and architecture
- Applied @markdown_core.mdc formatting standards
- Removed redundant content and verbose explanations
- Focused on actionable next steps and clear requirements
- Single source of truth for research findings
BREAKING CHANGE: Consolidated 5 separate research documents
into single RESEARCH_COMPLETE.md file
- Add GLOSSARY.md with core terminology and cross-references
- Add implementation-roadmap.md with 3-phase development plan
- Add notification-system.md with Native-First architecture spec
- Update ios/Plugin/README.md to reflect actual vs planned implementation status
This establishes the foundation for implementing shared SQLite storage,
TTL-at-fire enforcement, rolling window safety, and platform completion
as outlined in the phased roadmap.
Files: 4 changed, 807 insertions(+), 13 deletions(-)
- Remove UI framework considerations (Tailwind, etc.) as irrelevant for Capacitor plugins
- Focus on plugin API design, data models, and platform integration
- Update implementation phases to reflect actual plugin development needs
- Correct conclusion to emphasize plugin architecture over UI components
- Clarify that plugins provide backend functionality, not visual presentation
Resolves: Misunderstanding of Capacitor plugin architecture and UI responsibilities
- Focus plan on implementation phases and priorities
- Update package-lock.json with markdownlint-cli2 dependency
Resolves: Streamline feature planning to focus on implementation approach
- Remove 'Next 1-2 days' from Immediate Actions
- Remove 'Next 1 week' from Short-Term Actions
- Remove 'Next 2-4 weeks' from Medium-Term Actions
- Remove 'timeline' references from action items
- Clean up all time-based language while maintaining structure
- Document now focuses on phases and priorities without misleading estimates
Resolves: Complete removal of unrealistic time estimates
- Fix line length to never exceed 80 characters
- Remove trailing spaces from wrapped lines
- Ensure consistent spacing around all structural elements
- Pass markdownlint validation (0 errors)
- Maintain proper markdown structure and readability
Resolves: Markdown formatting compliance and readability
- Replace 5 separate research documents with single consolidated file
- Eliminate document duplication and overlapping information
- Move documentation from 'docs/' to 'doc/' folder
- Maintain all essential research findings and implementation details
- Improve maintainability with single source of truth
- Follow responsible documentation principles
Resolves: Document multiplication and organization issues
