otSdkDriver.js needs an error handling approach

RESOLVED INCOMPLETE

Status

Hello (Loop)
Client
P3
normal
Rank:
32
RESOLVED INCOMPLETE
3 years ago
a year ago

People

(Reporter: dmose, Unassigned)

Tracking

unspecified
Points:
---
Bug Flags:
firefox-backlog +

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [tech-debt])

(Reporter)

Description

3 years ago
There are a bunch of action methods in otSdkDriver.js that simple log any error to the console and return.  Presumably, some (maybe all?) of them should really be provide some sort of user feedback that something went wrong, perhaps by dispatching error actions.
Flags: firefox-backlog+

Updated

3 years ago
Rank: 32
Priority: -- → P3
(Reporter)

Comment 1

3 years ago
Of particular interest here will be figuring how we want to surface errors to the user when a remote video subscribe fails (kill the call and show an error message?) and a screen share subscribe fails (show an in-call error message -- need to figure out what the common failure modes/possible remedies are here, at least).
(Reporter)

Comment 2

3 years ago
Just to help see this behavior in the wild, I asked :bwc how to force ICE to fail.  He said:

14:49:43 <bwc> dmose: From content, you can just trickle garbage.
14:50:10 <bwc> dmose: You can also fail to trickle at all, but that hits a slightly different failure path.
14:50:32 <bwc> dmose: Failing to trickle at all will cause a failure faster.
(Reporter)

Comment 3

3 years ago
Also:

<bwc> dmose: I think the ICE stack will wait 5 seconds to see trickle candidates before giving up.
Blocks: 1259762
Support for Hello/Loop has been discontinued.

https://support.mozilla.org/kb/hello-status

Hence closing the old bugs. Thank you for your support.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.