Hello,
The problem described occurs on windows mobile platforms. Tested on equipment: CN50, CN51, MC65, MC67.
How to produce the error:
- Install an app on one of the devices described above.
- Restart the machine
- I make connection tests for the app, via Wireless and GPRS (Creating a socket and exchanging data with it)
- I leave the device for an idle time (about 1h)
- Click the button to take the test again. The socket error 10050 starts to appear.
This error also occurs when you change the connection type. Ex: The equipment is connected via cable to the computer and pulls the cable causing the equipment to use the wirless connections (wifi or GPRS)
Procedures to try to solve:
- I left the app and turned off the wireless interface and tried GPRS only (did not work)
- Exit the app and disconnected the gprs interface and tried only wireless (did not work)
- I left the app, reconnected the wireless interface and gprs, opened internet explorer, entered a web address, then opened the app and tested the connection (worked).
APP:
The application basically creates a socket with a server, I do not perform any connection request operation type ConnectionManager.open () before creating the socket, since I saw that it is deprecated.
Is it necessary to use the ConnectionManager for devices with windows mobile?