Skip to content

feat: Support data-only FCM messages#121

Merged
akalex merged 1 commit intomasterfrom
feature/ISSUE-120-Support-data-only-FCM-messages
Apr 7, 2026
Merged

feat: Support data-only FCM messages#121
akalex merged 1 commit intomasterfrom
feature/ISSUE-120-Support-data-only-FCM-messages

Conversation

@akalex
Copy link
Copy Markdown
Member

@akalex akalex commented Apr 7, 2026

The builder methods unconditionally created notification/alert objects, making it impossible to produce data-only FCM messages. Now, when no notification-related fields are provided, the builders omit the notification (Android) or alert (APNS) from the payload.

Also changes AndroidConfig.build() visibility default from Visibility.PRIVATE to None — FCM applies PRIVATE server-side when omitted, so wire behavior is unchanged.

…SConfig.build() (#120)

The builder methods unconditionally created notification/alert objects,
making it impossible to produce data-only FCM messages. Now, when no
notification-related fields are provided, the builders omit the
notification (Android) or alert (APNS) from the payload.

Also changes `AndroidConfig.build()` visibility default from
`Visibility.PRIVATE` to None — FCM applies PRIVATE server-side when
omitted, so wire behavior is unchanged.
@akalex akalex self-assigned this Apr 7, 2026
@akalex akalex merged commit e11a4df into master Apr 7, 2026
17 checks passed
@akalex akalex deleted the feature/ISSUE-120-Support-data-only-FCM-messages branch April 7, 2026 17:46
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.

Support data-only FCM messages in AndroidConfig.build() and APNSConfig.build()

2 participants