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
Runnig on Android 11 (same error) Real Device
Runnig on Android 9 (Android Emulator) MeMu Play
Runnig on Android 9 (Android Emulator) BlueStacks 5
The origin of error is internal and unknow
It's definitely a DOTNET issue on android. Netly uses System.Net.Sockets as the basis for socket creation. This library is having internal errors in the Android device.
My suspicions:
Android Manifest needs some kind of permissions.
The compilation of System.Net.Sockets internally is not working due to some internal type of conversion (C# to C++/Java or object).
Doubts:
The problem is with the TCP server or TcpClient. What about the server that is not working (listening directly?) or the TcpClient that cannot connect to the socket? (Needs to be tested)
In case the problem is the TcpServer that cannot listen to the localhost on Android or the TcpClient that cannot connect to the localhost. How should you solve it if the problem is internal? (Do nothing?)
How to move forward? Continue writing socket using System.Net.*? or start the base in C++ and the interface in C#?
The cause of this error is because ``TCP Backlog`` by default was using ``0`` and searching ``TcpListener`` api it was using ``2147483647``. To fix it needed update default value to ``2147483647`` or diferent by zero or negative value.
After many test i find it.
It's definitely a DOTNET issue on android. Netly uses
System.Net.Sockets
as the basis for socket creation. This library is having internal errors in the Android device.My suspicions:
System.Net.Sockets
internally is not working due to some internal type of conversion (C# to C++/Java or object).Doubts:
The problem is with the TCP server or TcpClient. What about the server that is not working (listening directly?) or the TcpClient that cannot connect to the socket? (Needs to be tested)
In case the problem is the TcpServer that cannot listen to the localhost on Android or the TcpClient that cannot connect to the localhost. How should you solve it if the problem is internal? (Do nothing?)
How to move forward? Continue writing socket using
System.Net.*
? or start the base in C++ and the interface in C#?Originally posted by @alec1o in #33 (comment)
The text was updated successfully, but these errors were encountered: