Skip to content

Conversation

@ovitrif
Copy link
Collaborator

@ovitrif ovitrif commented Jan 9, 2026

Description

The notification service extension now follows a lightweight approach that avoids iOS memory (~24MB) and time (~30s) constraints by not starting ldk-node in the extension.

Changes:

  • NotificationService now only decrypts payload and displays time-sensitive notifications with urgency messaging
  • Added IncomingPaymentInfo model to persist payment data between extension and main app via App Group UserDefaults
  • Main app now processes incoming payments when it becomes active, with priority handling for node startup and LSP peer connection
  • Notifications are auto-removed after payment expiry window (2 minutes)
  • AppViewModel clears pending payments when payment is received

Linked Issues/Tasks

n/a

Screenshot / Video

n/a

The notification service extension now follows a lightweight approach that
avoids iOS memory (~24MB) and time (~30s) constraints by not starting the
LDK node in the extension.

Changes:
- NotificationService now only decrypts payload and displays time-sensitive
  notifications with urgency messaging
- Added IncomingPaymentInfo model to persist payment data between extension
  and main app via App Group UserDefaults
- Main app now processes incoming payments when it becomes active, with
  priority handling for node startup and LSP peer connection
- Notifications are auto-removed after payment expiry window (2 minutes)
- AppViewModel clears pending payments when payment is received
@ovitrif ovitrif force-pushed the feat/push-notif-wo-delivery branch from 4991f92 to 15f1a14 Compare January 9, 2026 16:57
@ovitrif ovitrif changed the title refactor(notifications): Replace node background processing with UI notifications wording refactor(notifications): simplify extension to avoid LDK node startup Jan 9, 2026
@ovitrif ovitrif changed the title refactor(notifications): simplify extension to avoid LDK node startup refactor: simplify extension to avoid LDK node startup Jan 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants