Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WEBRTC-690][ENGDESK-11170] Push Notification investigation enhancements + IceCandidate Bug Fix #58

Merged
merged 4 commits into from
Sep 16, 2021

Conversation

Oliver-Zimmerman
Copy link
Collaborator

WebRTC-690 - Push Notification investigation.

This PR fixes the autologin mechanism by storing the environment used after a successful login.

There is also another socket listener method that is used to set our sessionID earlier, this makes it possible to build a call before the login is successful which is useful for the upcoming Push Notification release

We no longer send video media constraints on the WebRTC SDK

We now wait 300 ms before sending our invite, this means that we have time to gather more (most often all), ice candidates, before sending our invitation. This hopefully fixes a customer issue where IPv6 was the only candidate available, which is not supported

👴 👶 Behaviors

Before changes

Environment not remembered for autologin
Session ID being set on successful login
Sending video media constraints with the invitation and answer SDPs
Sending invite as soon as first ice candidate obtained

After changes

Environment remembered via shared preferences
The session ID is now set as soon as a login is attempted, rather than after it was successful
No video media constraints in SDPs
We now leave 300 ms to collect ice candidates before sending the invite

Copy link

@guillermobattistel guillermobattistel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Oliver-Zimmerman Oliver-Zimmerman merged commit 94720d6 into main Sep 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants