fix: call preference initialization during ringing#921
Merged
Conversation
renefloor
approved these changes
Apr 1, 2025
Contributor
renefloor
left a comment
renefloor
left a comment
There was a problem hiding this comment.
This is a breaking change, but we are already making breaking changes in the next release.
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
2 participants
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.
Fixes FLU-47
This pull request addresses the management of call preferences, particularly during the ringing flow. Previously, call preferences set while creating a ringing call could be overlooked if
StreamVideo.incomingCallwas set beforehand when handling the ringing event. Additionally, default call properties have been added to the StreamVideo options for improved functionality.