Forward the original push payload into the notification handler - #1481
Merged
aleksandar-apostolov merged 12 commits intoAug 1, 2025
Conversation
Contributor
SDK Size Comparison 📏
|
rahul-lohra
marked this pull request as draft
July 28, 2025 13:20
rahul-lohra
marked this pull request as ready for review
July 28, 2025 13:46
|
aleksandar-apostolov
approved these changes
Aug 1, 2025
aleksandar-apostolov
deleted the
feature/rahullohra/push-payload-downstream
branch
August 1, 2025 08:17
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.


🎯 Goal
Propagate push payload from FCM down to our Notification APIs
Enhance the notification handling flow by forwarding the full push notification payload (key-value pairs) to the
StreamNotificationHandlerinterface.This allows client applications to access the original push payload and consume custom fields (e.g., dynamic titles, metadata) directly, which was not possible before.
🛠 Implementation details
Existing API will new extend new interface which has
payload:Map<String, Any?>Customizing PendingIntent Bundles
We’ve introduced new APIs that allow client applications to customize the Bundle attached to
PendingIntents.This enables you to:
StreamCallActivity.Implementation Details
Added two new interfaces:
StreamIntentResolverWithPayloadNotificationIntentBundleResolverThese are used internally by the Notification Handler.
Provided a
DefaultNotificationIntentBundleResolver, which can be supplied during SDK initialization.Client Usage
Here is an example on how you can customise the bundle for accect and reject bundle on the incoming call
We will extend
DefaultNotificationIntentBundleResolverand overridegetAcceptCallBundleandgetRejectCallBundleTo simplify creating a base bundle for StreamCallActivity, you can use the helper method: