I tested nw 0.9.1 linux. It's working with Chrome 32.

The demo I'm using is https://bitbucket.org/webrtc/codelab/overview step7 folder

with this patch to use SCTP:

diff --git a/complete/step7/js/main.js b/complete/step7/js/main.js
index 7daf56c..0dc7f4c 100644
--- a/complete/step7/js/main.js
+++ b/complete/step7/js/main.js
@@ -161,7 +161,7 @@ function createPeerConnection() {
     try {
       // Reliable Data Channels not yet supported in Chrome
       sendChannel = pc.createDataChannel("sendDataChannel",
-        {reliable: false});
+        {reliable: true});
       sendChannel.onmessage = handleMessage;
       trace('Created send data channel');
     } catch (e) {

Ok - thanks for providing the link. I will check what might be the difference with my code and maybe i find the reason or can provide an example which does not work.

Hi! I'm trying to get work following code with peerjs.
Here is index.html, which works in webkit:

<script src="http://cdn.peerjs.com/0.3/peer.js"></script>
<script>
  var peer = new Peer('someid1', {host: 'localhost', port: 9000});
  // ADDED THIS:
  peer.on('open', function(id) {
    console.log('My Peer is is: ' + id)
    var conn = peer.connect('someid2', {reliable:true});
    console.log(conn.label)
    console.log("REMOTE connecting to LOCAL", conn)

    conn.on('error', function(err) {
        console.log('error')
        console.log(err)
    });

    conn.on('data', function(data) {
        console.log('on data')
        console.log('Received', data);
    });


    conn.on('open', function(){  
      console.log("connect to REMOTE opened", conn);
      console.log('before sending hi')
      conn.send('hi!');
    });
  }); 

  peer.on('close', function() { 
    console.log('peer destroyed')
  });

  peer.on('error', function(err) {
      console.log('error peer')
      console.log(err)
    });
</script>

Here is remote peer code which accepts connections and data peer2.html:

<script src="http://cdn.peerjs.com/0.3/peer.js"></script>
<script>
  var peer = new Peer('someid1', {host: 'localhost', port: 9000});
  // ADDED THIS:
  peer.on('open', function(id) {
    console.log('My Peer is is: ' + id)
    var conn = peer.connect('someid2', {reliable:true});
    console.log(conn.label)
    console.log("REMOTE connecting to LOCAL", conn)

    conn.on('error', function(err) {
        console.log('error')
        console.log(err)
    });

    conn.on('data', function(data) {
        console.log('on data')
        console.log('Received', data);
    });


    conn.on('open', function(){  
      console.log("connect to REMOTE opened", conn);
      console.log('before sending hi')
      conn.send('hi!');
    });
  }); 

  peer.on('close', function() { 
    console.log('peer destroyed')
  });

  peer.on('error', function(err) {
      console.log('error peer')
      console.log(err)
    });
</script>

If I run these code in different window chrome browsers then I get such output:
index.html >>>>>
My Peer is is: someid1
dc_9t5698cttbuik9
REMOTE connecting to LOCAL
DataConnection {_events: Object, options: Object, open: false, type: "data", peer: "someid2"…}
connect to REMOTE opened
DataConnection {_events: Object, options: Object, open: true, type: "data", peer: "someid2"…}
before sending hi
on data
Received Hello!

peer2.html >>>>
My Peer is is: someid2
LOCAL connection open
DataConnection {_events: Object, options: Object, open: true, type: "data", peer: "someid1"…}
before data
LOCAL got message hi!

But when I launch index.html in node-webkit then following output I get:
index.html>>>>
My Peer is is: someid1
dc_4ydx86ya8nbnvcxr
REMOTE connecting to LOCAL
DataConnection {_events: Object, options: Object, open: false, type: "data", peer: "someid2"…}
connect to REMOTE opened
DataConnection {_events: Object, options: Object, open: true, type: "data", peer: "someid2"…}
before sending hi

peer2.html>>>>>
My Peer is is: someid2 peer2.html:7
LOCAL connection open
DataConnection {_events: Object, options: Object, open: true, type: "data", peer: "someid1"…}
peer2.html:25
before data

So, connection is established but no data is transmitted or no 'data' event emitted.

Chrome browser version Version 33.0.1750.117 And all above code works there

Node-webkit chromium version Version 32.0.1700.107 (1700.107)

Any ideas? Maybe trouble in Chromium version? Is there any instructions how to build node-webkit with fresh chromium?

All right - i am not able to reproduce this with node-webkit 0.9.2. SCTP Data channels work fine with 0.9.2 so i am closing this.

@rogerwang: node-webkit can communicate fine with Chrome 32 but not with Chrome 33 or later. This seems to be a Chrome 32 issue. The same issue can be found in Chromium 32.0.1700.77. This is the same version as the Chromium Version in node-webkit 0.9.2 and these too talk fine to each other. But both cannot speak to Chromium 33+. I think that you guys cannot do much about it other than upgrading to Chromium 33 - feel free to keep it open or close it. I was not able to find a workaound to make Chromium 32.0.1700.77 talk to anyone other that itself.

@longsleep nw 0.9.2 is updated to Chromium 32.0.1700.107. Does that version have the bug as well?

@rogerwang: sorry i meant 32.0.1700.107. The same Version is in Ubuntu too - and it has the same Problem. It is exactly varuzhnikov described above with node-webkit. To test one can install Spreed Speak Freely https://github.com/strukturag/spreed-speakfreely
When installed, join twice and call the other user. Then try to chat when in a call.

Are there any updates for this issue?

As previously said, it's currently impossible to send data using DataChannels to Chromium v33+. Is node-webkit going to be updated soon to a newer Chromium release?

👍 got bit by this just today, after spending a few hours trying to figure out why my client refuses to work in node-webkit.

This is bug in the Chromium version included with node-webkit 0.9. Try with 0.10.0-rc1 when it is available.

Thanks for the update, will do. I'm afraid to embark on the compilation journey myself, so I guess I'll wait :)

Since a couple of hours there are automatic builds - check your code with the latest build and report back.

Builds: http://dl.node-webkit.org/live-build/

@rogerwang: Live builds are great. http://dl.node-webkit.org/live-build/06-21-2014/linux64_master-build-55-633e3d5-b0d0757-cf7702c-8fb09a0-d54520d-86728d1/ fixes the problem for me. So i am tempted to close this.

@jure: Please let us know if it works for you too.

Closing as it works in nw 0.10.

Yes, very sorry for the delay, I also confirm that DataChannels now work as expected. P.S.: Live builds are fantastic!