BoringSSL Error

This pretty much means what it says. An operation on the TLS connection failed because the TLS was closed via the

close_notify

Share and Enjoy
—
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

I'm having the same problem.

Xcode 9.2 - Swift 4 - Alamofire 4.6.0 - PHP7 - AWS Beanstalk

I'm using Alamofire to get data from a php API in my xcode project.

I'm only getting part of the response back, ie 3 posts rather than 10. The response is not even sequential. For example, if I have posts 1-10, i only get 3, 7,9.

I consistently get the following error with this strange https post response.

[BoringSSL] Function boringssl_session_errorlog: line 2871 [boringssl_session_read] SSL_ERROR_ZERO_RETURN(6): operation failed because the connection was cleanly shut down with a close_notify alert

https://forums.developer.apple.com/message/289738#289738

Did anybody find a solution for this?

The response is not even sequential. For example, if I have posts 1-10, i only get 3, 7,9.

That very unlikely to be related to this BoringSSL message. This message is from the TLS layer and it’s related to how the TLS connection closes. If you’re missing content from the middle of the stream, that’s clearly not related to this message but rather is more likely to be a problem on the server.

I recommend that you use CFNetwork diagnostic logging (per QA1887) to look at the plaintext of the response you’re getting back from the server.

Share and Enjoy
—
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

well, I got the same error message. I am using Swift 4.0 and Alamofire as well. Then I found a typo in composing my request url and corrected. But still the same error message came up. Then I used CFNetwork diagnostic logging as eskimo suggested and the error message was gone. Even I removed the

CFNETWORK_DIAGNOSTICS

Maybe I can help track this down. I have a really simple test app that is using NSURLSession directly. I have two data transactions using POST, and each one generates this:

[BoringSSL] Function boringssl_session_errorlog: line 2871 [boringssl_session_read] SSL_ERROR_ZERO_RETURN(6): operation failed because the connection was cleanly shut down with a close_notify alert

My configuration is really simple:

config = URLSessionConfiguration.default
config.urlCache = nil
config.httpShouldSetCookies = false
config.httpShouldUsePipelining = true

I tried with pipelining off, no difference.

Xcode 9.2, iPad simulator.

Anything I can try?

Anything I can try?

To what end? Are you seeing any problems other than this log message?. Because the log message is not a problem in and of itself

Share and Enjoy
—
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

I didn't really read the whole thread - missed its just cosmetic. Was offering to help track it down if needed. You said not needed, that's fine.

I request a api such as https://192.168.0.1/v1/market/areas.html (192.168.0.1 mean use ip direct, just as example, and use allow Invalid Certificates option). I got the same error log, then time out, and delegate of NSURLSession not called except the error method. Here are some other information ( ✅ get right response, ✖ get error log and time out error).

Device: iPhone 7plus 11.3.1

Network: Wi-Fi Cellular×

iPhone use Wi-Fi: AFNetwork or NSURLSession:✅ safari:✅ chrome:✅

iPhone use Cellular: AFNetwork or NSURLSession:✖ safari:✖ chrome:✖

MAC (iPhone use Cellular as a hotspot to mac): chrome:✅ Insomnia:✅ firefox:✅ safari:✖

More: Insomnia is a client to test api like postman, and it use the Electron Framework developed.

I'm likewise seeing the following new messages in Swift 4.2 Xcode 10 beta 6

Are these an issue? If so, Can I filter them out?

2018-08-17 08:07:58.634513-0700 Turismo[568:89141] [BoringSSL] boringssl_session_errorlog(224) [C2.1:2][0x125dd65e0] [boringssl_session_read] SSL_ERROR_SSL(1): operation failed within the library

2018-08-17 08:07:58.636372-0700 Turismo[568:89141] [BoringSSL] boringssl_session_handshake_error_print(205) [C2.1:2][0x125dd65e0] 5028053656:error:100000d7:SSL routines:OPENSSL_internal:SSL_HANDSHAKE_FAILURE:/BuildRoot/Library/Caches/com.apple.xbs/Sources/boringssl/boringssl-109.200.32/ssl/ssl_lib.cc:1081:

2018-08-17 08:07:58.639481-0700 Turismo[568:89141] [BoringSSL] boringssl_session_errorlog(224) [C2.1:2][0x125dd65e0] [boringssl_session_read] SSL_ERROR_SSL(1): operation failed within the library

2018-08-17 08:07:58.641903-0700 Turismo[568:89141] [BoringSSL] boringssl_session_handshake_error_print(205) [C2.1:2][0x125dd65e0] 5028053656:error:100000d7:SSL routines:OPENSSL_internal:SSL_HANDSHAKE_FAILURE:/BuildRoot/Library/Caches/com.apple.xbs/Sources/boringssl/boringssl-109.200.32/ssl/ssl_lib.cc:1081:

2018-08-17 08:07:58.644097-0700 Turismo[568:89141] [BoringSSL] boringssl_session_errorlog(224) [C2.1:2][0x125dd65e0] [boringssl_session_read] SSL_ERROR_SSL(1): operation failed within the library

2018-08-17 08:07:58.644412-0700 Turismo[568:89141] [BoringSSL] boringssl_session_handshake_error_print(205) [C2.1:2][0x125dd65e0] 5028053656:error:100000d7:SSL routines:OPENSSL_internal:SSL_HANDSHAKE_FAILURE:/BuildRoot/Library/Caches/com.apple.xbs/Sources/boringssl/boringssl-109.200.32/ssl/ssl_lib.cc:1081:

2018-08-17 08:07:58.644527-0700 Turismo[568:89141] [BoringSSL] boringssl_session_errorlog(224) [C2.1:2][0x125dd65e0] [boringssl_session_read] SSL_ERROR_SSL(1): operation failed within the library

2018-08-17 08:07:58.644622-0700 Turismo[568:89141] [BoringSSL] boringssl_session_handshake_error_print(205) [C2.1:2][0x125dd65e0] 5028053656:error:100000d7:SSL routines:OPENSSL_internal:SSL_HANDSHAKE_FAILURE:/BuildRoot/Library/Caches/com.apple.xbs/Sources/boringssl/boringssl-109.200.32/ssl/ssl_lib.cc:1081:

I am seeing this problem now with macOS 10.14 beta 8 / XCode 10 beta 6.

I tried running the same app but built on macOS 10.13, XCode 9 an it works fine on 10.13 but also fails when I try running it on 10.14 beta 8.

Realm query returns no data either so somethings broken I think..

I think its something broken in the 10.14 beta because the same app compiled with XCode 10 beta 6 on macOS 10.14 beta 8 runs fine on macOS 10.13.

Strange though, Realm Studio seems to work fine

Here is an update - it seems things were working fine, it just took a little while for data to synchronise - seems it might have been quite a bit slower than it usually is.

We manage to solved this logging problem by disabling HTTP/2 on the web server, in our case we have migrated from classic ELB to application ELB that added support to HTTP/2 on AWS and we started getting "TIC Read Status [11:0x0]: 1:57" on XCode 10.1 / iOS 12 console