this._socket is undefined about peerjs HOT 7 CLOSED

turns out Peer.prototype._init is never called.

from peerjs.

so I traced this call to disconnect before init back to

Peer.prototype._cleanup = function() {
var self = this;
if (!!this.managers) {
var peers = Object.keys(this.managers);
for (var i = 0, ii = peers.length; i < ii; i++) {
this.managers[peers[i]].close();
}
}
util.setZeroTimeout(function(){
self.disconnect();
});
this.emit('close');
}; 

Tests are working, thats only happens in project. I'm using angular js

from peerjs.

ok, so that happens on unsupported browser. it called from 👍

/** Destroys the Peer and emits an error message. */
Peer.prototype._abort = function(type, message) {
util.log('Aborting. Error:', message);
var err = new Error(message);
err.type = type;
this.destroy();
this.emit('error', err);
}; 

it tries to destroy non intialized peer before it emts error.

from peerjs.

Having problems with this issue as well, thanks for posting it!
seems to happen even when I only use latest Chrome 27.0.1453.94 .
So I don't think it's related to unsupported browsers... maybe an issue with the browser.
I can't figure out why it happens, one out of 10 connections fail because of this issue.

do you see it as a browser issue?

from peerjs.

Got it, disconnect defaults to undefined, should default to true. Fixing now..

from peerjs.

Just decided to check if socket exists before closing, peer.disconnected does not correlate with whether socket connection has been made, but rather whether this peer is 'dead' so using that to check wouldn't have made sense.

Anyways, @roeeyud and @darvin, this should be fixed here: a4a3f2d Let me know / reopen issue if you still have problems

from peerjs.

Thanks for that quick response!
No problems with it so far

from peerjs.