Improve the behaviour when rejecting a call while already in an active call - #1482
Merged
aleksandar-apostolov merged 30 commits intoAug 1, 2025
Merged
Conversation
Contributor
SDK Size Comparison 📏
|
…eject-on-new-intent' into feature/rahullohra/handle-call-reject-on-new-intent
|
aleksandar-apostolov
approved these changes
Aug 1, 2025
aleksandar-apostolov
deleted the
feature/rahullohra/handle-call-reject-on-new-intent
branch
August 1, 2025 17:07
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
Improve call rejection from Notification Button
🛠 Implementation details
"The UI observes
Call.state.rejectedBy. If the value indicates the current user, the code will attempt to close the activity, provided there is no active call."We are updating
rejectedByfrom theRejectCallBroadcastReceiver