Skip to content

fix: Correct FCM wire-format field names for AndroidNotification#118

Merged
akalex merged 1 commit intomasterfrom
bugfix/Correct-FCM-wire-format-field-names-for-AndroidNotification
Mar 30, 2026
Merged

fix: Correct FCM wire-format field names for AndroidNotification#118
akalex merged 1 commit intomasterfrom
bugfix/Correct-FCM-wire-format-field-names-for-AndroidNotification

Conversation

@akalex
Copy link
Copy Markdown
Member

@akalex akalex commented Mar 30, 2026

  • visibility: remove incorrect "VISIBILITY_" prefix ("PRIVATE" not "VISIBILITY_PRIVATE")
  • priority: use wire-format key "notification_priority" instead of "priority"
  • event_timestamp: use wire-format key "event_time" instead of "event_timestamp"
  • Remove stale dataclass field names from serialized payload that differ from FCM API keys (priority, event_timestamp, vibrate_timings_millis)

Aligned with the official firebase-admin-python SDK serialization.

- visibility: remove incorrect "VISIBILITY_" prefix ("PRIVATE" not "VISIBILITY_PRIVATE")
- priority: use wire-format key "notification_priority" instead of "priority"
- event_timestamp: use wire-format key "event_time" instead of "event_timestamp"
- Remove stale dataclass field names from serialized payload that differ
  from FCM API keys (priority, event_timestamp, vibrate_timings_millis)

Aligned with the official firebase-admin-python SDK serialization.
@akalex akalex self-assigned this Mar 30, 2026
@akalex akalex merged commit d449ff3 into master Mar 30, 2026
16 checks passed
@akalex akalex deleted the bugfix/Correct-FCM-wire-format-field-names-for-AndroidNotification branch March 30, 2026 14:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant