[Fix]Ensure Call.state.startedAt is non-nil when session is valid #493
Conversation
This file contains 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
martinmitrevski
approved these changes
Aug 22, 2024
SDK Size
|
Generated by 🚫 Danger |
|
ipavlidakis
deleted the
fix/call-state-startedAt-is-not-nil-when-session-is-valid
branch
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.
📝 Summary
This revision aims to resolve an issue where callDuration may not be populated from the SFU.
🧪 Manual Testing Notes
Join and leave multiple calls. The call duration on top of the call should always be visible after joining a call.
☑️ Contributor Checklist