You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While handling RTCPeerconnection offer connectionstatechange event hangs in connecting state and produce "W/chromium( 7051): [WARNING:socket_tcp.cc(134)] Error from connecting socket, result=-102" error. but it works while creating offer with no problem.
Expected Behavior
I m expecting I can handle peerconnection offer with no error.
I tried both 6.1.5 and 6.2.0 beta 2 versions but same problem
flutter doctor results
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.27.1, on macOS 15.1.1 24B91 darwin-arm64, locale tr-TR)
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 16.2)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2024.2)
[✓] VS Code (version 1.96.4)
[✓] Connected device (7 available)
[✓] Network resources
Self grab
I'm ready to work on this issue!
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Current Behavior
While handling RTCPeerconnection offer connectionstatechange event hangs in connecting state and produce "W/chromium( 7051): [WARNING:socket_tcp.cc(134)] Error from connecting socket, result=-102" error. but it works while creating offer with no problem.
Expected Behavior
I m expecting I can handle peerconnection offer with no error.
Steps with code example to reproduce
run local server on main dart
render InappWebview in my widget
send ws url to inappwebview
my local javascripy codes
Stacktrace/Logs
Stacktrace/Logs
Flutter version
3.27.1
Operating System, Device-specific and/or Tool
Android default flutter sdk version
Plugin version
6.1.5 , 6.2.0 beta 2
Additional information
I tried both 6.1.5 and 6.2.0 beta 2 versions but same problem
flutter doctor results
Self grab
The text was updated successfully, but these errors were encountered: