Hi,
I have an app which connects to a product by a SSL Socket and it sends ASCII messages and I get the reply etc. in my app.
On my phone (plus 1500+ other devices customers have in the field) my app works fine.
I have one customer whos phone is having an issue connecting with SSL.
I have developed a backend log in my app which I can view in a web browser to see what is happening in the background, and I find that it tries to make connection to the device using a SSL socket and then closes the socket pretty much straight away. The astream_Error sub get trigged as soon as the connection tries to make connection.
Using my Phone and connecting to the same IP/Port using a SSL Socket the connection gets made and works fine.
His phone is a Samsung (I think S5).
If I make a connection using a standard socket, (not SSL) then it connects fine and works. Only seems to be a SSL socket that is having the issue making connection.
Anyone else come across something like this or have any suggestions for me to try ?
I have an app which connects to a product by a SSL Socket and it sends ASCII messages and I get the reply etc. in my app.
On my phone (plus 1500+ other devices customers have in the field) my app works fine.
I have one customer whos phone is having an issue connecting with SSL.
I have developed a backend log in my app which I can view in a web browser to see what is happening in the background, and I find that it tries to make connection to the device using a SSL socket and then closes the socket pretty much straight away. The astream_Error sub get trigged as soon as the connection tries to make connection.
Using my Phone and connecting to the same IP/Port using a SSL Socket the connection gets made and works fine.
His phone is a Samsung (I think S5).
If I make a connection using a standard socket, (not SSL) then it connects fine and works. Only seems to be a SSL socket that is having the issue making connection.
Anyone else come across something like this or have any suggestions for me to try ?