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

No error when client tries to connect with a non-existing ID #467

Open
1 task done
chris0203 opened this issue Dec 10, 2024 · 0 comments
Open
1 task done

No error when client tries to connect with a non-existing ID #467

chris0203 opened this issue Dec 10, 2024 · 0 comments

Comments

@chris0203
Copy link

Please, check for existing issues to avoid duplicates.

  • No similar issues found.

What happened?

When trying to connect a non-existing ID, on error has no fired.

The Peer A

this._peer = new Peer('test', {
    host: 'localhost',
    port: 9000,
    path: '/signaling',
});

The Peer B

this._peer = new Peer({
    host: 'localhost',
    port: 9000,
    path: '/signaling',
});
this.peerConnection = this._peer.connect('abc');
this.peerConnection.on('error', () => {
      console.log('ERROR');
  });

The Signal server return {"type":"EXPIRE","src":"abc","dst":"7ac5c04a-d47a-44f1-95e4-7800b1a72900"}
The on error in Peer B should catch the error, but here is nothing catch.

The similar error #127 , but not the same

peerjs version: 1.5.4
peer signal server version: 1.0.2

How can we reproduce the issue?

No response

What do you expected to happen?

The on error in Peer B should catch the error

Environment setup

  • OS: Windows 10
  • Platform: Electron 30.0.1

Is this a regression?

No response

Anything else?

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant