Skip to content

fix: make notification initialization idempotent#554

Merged
jjoonleo merged 1 commit into
mainfrom
feature/issue-532-notification-init-idempotent
Jun 28, 2026
Merged

fix: make notification initialization idempotent#554
jjoonleo merged 1 commit into
mainfrom
feature/issue-532-notification-init-idempotent

Conversation

@jjoonleo

Copy link
Copy Markdown
Contributor

Summary

  • Make NotificationService.initialize() idempotent across sequential and concurrent calls.
  • Store FCM foreground/opened-app and token-refresh subscriptions so repeated setup does not duplicate notification handling or token refresh registration.
  • Document the service-level initialization and listener guarantees in Notification-Behavior.

Tests

  • flutter test test/core/services/notification_service_test.dart
  • flutter analyze

Closes #532

@jjoonleo jjoonleo merged commit f3550ce into main Jun 28, 2026
1 of 4 checks passed
@jjoonleo jjoonleo deleted the feature/issue-532-notification-init-idempotent branch June 28, 2026 12:12
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.

Make NotificationService initialization idempotent

1 participant