Closed
Bug 1280392
Opened 9 years ago
Closed 9 years ago
Error restarting WebRTC: "Unknown Error while getting user media"
Categories
(Hello (Loop) :: Client, defect)
Hello (Loop)
Client
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: ianbicking, Unassigned)
Details
(Whiteboard: [akita])
When I try to reconnect A/V in Akita I get an error (and it fails to reconnect). If I close the room and re-open the room, I am able to connect A/V again. Error:
OT.Publisher.onStreamAvailableError SourceUnavailableError: Unknown Error while getting user media sdk.js:31997:5
[197]</</Publisher/onStreamAvailableError() sdk.js:31997
[122]</</module.exports/onError() sdk.js:21451
tryCatcher() sdk.js:11177
[70]</</</<[23]</module.exports/Promise.prototype._settlePromiseFromHandler() sdk.js:9283
[70]</</</<[23]</module.exports/Promise.prototype._settlePromiseAt() sdk.js:9357
[70]</</</<[23]</module.exports/Promise.prototype._settlePromises() sdk.js:9473
[70]</</</<[2]</Async.prototype._drainQueue() sdk.js:6763
[70]</</</<[2]</Async.prototype._drainQueues() sdk.js:6773
Async/this.drainQueues() sdk.js:6655
(Async: MutationCallback) [70]</</</<[31]</schedule() sdk.js:10501
Async() sdk.js:6658
[70]</</</<[2]<() sdk.js:6789
s() sdk.js:6617
s/<() sdk.js:6617
[70]</</</<[23]</module.exports() sdk.js:8806
[70]</</</<[4]<() sdk.js:6875
s() sdk.js:6617
e() sdk.js:6617
[70]</</<() sdk.js:6617
[70]</</<() sdk.js:6617
[70]</<() sdk.js:6617
[70]<() sdk.js:6588
s() sdk.js:11
s/<() sdk.js:11
[34]</<() sdk.js:3813
[34]<() sdk.js:3810
s() sdk.js:11
s/<() sdk.js:11
[19]<() sdk.js:1944
s() sdk.js:11
s/<() sdk.js:11
[23]</<() sdk.js:2712
[23]<() sdk.js:2708
s() sdk.js:11
s/<() sdk.js:11
[24]<() sdk.js:3067
s() sdk.js:11
s/<() sdk.js:11
[4]</<() sdk.js:55
[4]<() sdk.js:19
s() sdk.js:11
s/<() sdk.js:11
[138]</<() sdk.js:23036
[138]<() sdk.js:23027
s() sdk.js:11
e() sdk.js:11
<anonymous> sdk.js:11
10:43:18.097 sending analytics: Object { clientVersion: "js-2.7.5", guid: "e169995e-65f1-4cfa-8360-83dcbb9e32a0", partnerId: "44669102", source: "about:loopconversation#-6u6zsMeK2o", logVersion: "1", clientSystemTime: 1466070198097, action: "Publish", variation: "Failure", payload: Object, sessionId: null, 2 more… }(unknown)
10:43:18.108 OT.exception :: title: Unable to Publish (1500) msg: GetUserMedia sdk.js:29026:3
_exceptionHandler() sdk.js:29026
[181]</OTError.handleJsException() sdk.js:29095
[197]</</Publisher/onStreamAvailableError() sdk.js:32012
[122]</</module.exports/onError() sdk.js:21451
tryCatcher() sdk.js:11177
[70]</</</<[23]</module.exports/Promise.prototype._settlePromiseFromHandler() sdk.js:9283
[70]</</</<[23]</module.exports/Promise.prototype._settlePromiseAt() sdk.js:9357
[70]</</</<[23]</module.exports/Promise.prototype._settlePromises() sdk.js:9473
[70]</</</<[2]</Async.prototype._drainQueue() sdk.js:6763
[70]</</</<[2]</Async.prototype._drainQueues() sdk.js:6773
Async/this.drainQueues() sdk.js:6655
(Async: MutationCallback) [70]</</</<[31]</schedule() sdk.js:10501
Async() sdk.js:6658
[70]</</</<[2]<() sdk.js:6789
s() sdk.js:6617
s/<() sdk.js:6617
[70]</</</<[23]</module.exports() sdk.js:8806
[70]</</</<[4]<() sdk.js:6875
s() sdk.js:6617
e() sdk.js:6617
[70]</</<() sdk.js:6617
[70]</</<() sdk.js:6617
[70]</<() sdk.js:6617
[70]<() sdk.js:6588
s() sdk.js:11
s/<() sdk.js:11
[34]</<() sdk.js:3813
[34]<() sdk.js:3810
s() sdk.js:11
s/<() sdk.js:11
[19]<() sdk.js:1944
s() sdk.js:11
s/<() sdk.js:11
[23]</<()sdk.js:2712
[23]<()sdk.js:2708
s()sdk.js:11
s/<()sdk.js:11
[24]<()sdk.js:3067
s()sdk.js:11
s/<()sdk.js:11
[4]</<()sdk.js:55
[4]<()sdk.js:19
s()sdk.js:11
s/<()sdk.js:11
[138]</<()sdk.js:23036
[138]<()sdk.js:23027
s()sdk.js:11
e()sdk.js:11
<anonymous>sdk.js:11
10:43:18.126 No string found for key: unmute_local_screen_button_title
Reporter | ||
Updated•9 years ago
|
Whiteboard: [akita]
Comment 1•9 years ago
|
||
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
Closed: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•