Azure-iot-sdk-c: IOS 12.2 SSLHandShake failed (-9807)

Created on 15 Apr 2019  路  6Comments  路  Source: Azure/azure-iot-sdk-c

I have had an application running since January on IOS sending telemetry data from IOS devices to IOT Hub. Recently, first noticed with the March 25th release of the IOS update the connection from IOS to the Azure IOT Hub is showing an error on connection and is waiting for the ssl certificate. I have test all Microsoft IOS examples and all seem to exhibit the same behavior.

Reproducible with IOS example found in the following repos:

https://github.com/Azure/azure-iot-sdk-c/tree/master/iothub_client/samples/ios

https://github.com/Azure-Samples/azure-iot-samples-ios.git

MacOS:
10.14.4

Xcode:
10.2

IOS:
12.2

Output Logs:

Creating IoTHub Device handle

Sending message 1 to IoTHub

Sending message 2 to IoTHub

Sending message 3 to IoTHub

Sending message 4 to IoTHub

Sending message 5 to IoTHub

2019-04-14 23:12:10.015786-0400 AzureIoTSample[547:35602] CFNetwork SSLHandshake failed (-9807)
2019-04-14 23:12:10.015877-0400 AzureIoTSample[547:35602] TCP Conn 0x283c052c0 SSLHandshake failed (-9807)
The device client has been disconnected

2019-04-14 23:12:10.143412-0400 AzureIoTSample[547:35602] CFNetwork SSLHandshake failed (-9807)
2019-04-14 23:12:10.143482-0400 AzureIoTSample[547:35602] TCP Conn 0x283c052c0 SSLHandshake failed (-9807)
The device client has been disconnected

2019-04-14 23:12:12.124070-0400 AzureIoTSample[547:35602] CFNetwork SSLHandshake failed (-9807)
2019-04-14 23:12:12.124145-0400 AzureIoTSample[547:35602] TCP Conn 0x283c04900 SSLHandshake failed (-9807)
The device client has been disconnected

2019-04-14 23:12:16.121599-0400 AzureIoTSample[547:35602] CFNetwork SSLHandshake failed (-9807)
2019-04-14 23:12:16.121696-0400 AzureIoTSample[547:35602] TCP Conn 0x283c02640 SSLHandshake failed (-9807)

area-service bug

Most helpful comment

@duvitech thanks for bringing this to our attention. We'll work on a repro and investigate a fix.

All 6 comments

@duvitech thanks for bringing this to our attention. We'll work on a repro and investigate a fix.

look like it is possibly the ssl certificate being flagged as invalid and the usual tricks of setting TLS security in the Plist entry does not seem to work.

Look like a bug similar to what @massand is investigating so reassigning to him.

@duvitech - thank you for reporting the issue! All Hubs had a recent certificate refresh to resolve iOS 12.2 and Mojave 10.14 TLS establishment issues. Please retry your connections now.

@YoDaMa, @duvitech, @massand, thank you for your contribution to our open-sourced project! Please help us improve by filling out this 2-minute customer satisfaction survey

Works as designed now thank you for the quick responses and investigation into this.

Was this page helpful?
0 / 5 - 0 ratings