[AND-241] Fixed an issue where the notification for a ringing call was not being removed after the call was declined #1280
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
The PR #1263 introduced an issue where the notification for a ringing call was not being removed after the call was declined.
🛠 Implementation details
In the current fix, we stop the foreground service when a ringing call is declined. Previously, we stopped any service within the
removeActiveCall(call)method, which functioned correctly, likely because only one service was running. Now, to stop a service, we identify the specific call associated with the service to be terminated.Here is the previous version of removeActiveCall
Here is current version
🎨 UI Changes
Add relevant screenshots
Add relevant videos
🧪 Testing
Explain how this change can be tested (or why it can't be tested)
Provide a patch below if it is necessary for testing
Provide the patch summary here
☑️Contributor Checklist
General
developbranchCode & documentation
stream-video-examples)☑️Reviewer Checklist
🎉 GIF
Please provide a suitable gif that describes your work on this pull request