Open Gaubee opened 10 months ago
@Gaubee sorry, I'm not able to look deeper your demo right now. However, there PR #98 has been merged recently. It is not published yet. So it might be a cause if you were using 0.114.4.
@shepeliev I have review this commit. This commit is just a question of the js platform, but in my example, I wrote the js-code myself. The problem I found was on IOS, not JS.
I did this test because I was trying to set up faster communication between WKWebView and native instead of WKScriptMessageHandler based communication. I have tested that WebSocket's speed does not meet the demand, and it has a large speed gap between up and down, which seems to be a hard-coded limitation. That's why I'm trying to give WebRTC point-to-point connectivity.
Maybe I should be suspicious of the WKWebView problem?
Having the same issue with iOS data channel, most of the time the data channel is closed with no events or feedback
iOS data channel (From onDataChannel
callback) stops receiving messages in a short time after the connection was established. While debugging, I found out that didReceiveMessageWithBuffer
which is inside DataChannel
, stops getting called. No signs of any crash or error.
Maybe this is related https://groups.google.com/g/discuss-webrtc/c/9NObqxnItCg
Hello @shepeliev! Can we please have a patch release with this fix https://github.com/shepeliev/webrtc-kmp/pull/123? I'm confident it will fix @Gaubee's problem as well
@tamimattafi, I've just published it. @Gaubee, could you check if it solves the issue, please?
@tamimattafi, I've just published it. @Gaubee, could you check if it solves the issue, please?
Thank you! @shepeliev
webrtc-sdk/Specs/114.5735.08 my demo is simple, open RTCDataChannel by webrtc-kmp and safari. then 10MB of data is sent, 64kb at one time. In theory, 157 times need to be sent to complete the transmission, but on the native side, often only 42 to 44 times can be received.
The same DEMO is correct on Android. I've read the source code for webrtc-kmp and I don't find it problematic. So one can only suspect that something is wrong here.
js code:
I don't think there's anything wrong with this code, and on Android, it works correctly, so I'm just Posting it here for reference.
Can you give me some inspiration?