What is the reading status of TIC 1:57 in iOS11 / Xcode 9?

Question

After upgrading to Xcode 9, using Swift 3 and the iPhone X simulator, my console is full:

TIC Read Status [11:0x0]: 1:57

What is it and how to fix it? Help is much appreciated.

PS: I prefer to not just "shut up" it with the help of Environment Variable in the assembly scheme.

Answer 1

Apple employees answered as follows:

TIC expands to "TCP I / O connection", which is a subsystem in CFNetwork that starts a TCP connection.

1 and 57 are the domain and code of CFStreamError, respectively; domain 1 is kCFStreamErrorDomainPOSIX, and within this domain 57 is ENOTCONN

In short, reading TCP failed using ENOTCONN.

Since the TCP I / O connection subsystem does not have an open API, you should definitely use it through some high-level shell (for example, NSURLSession).

source: https://forums.developer.apple.com/thread/66058

EDIT / UPDATE:

Since we still have these nasty magazines, I asked the same Apple specialist from the link above for our situation , which is now specific to Xcode 9 and Swift 4. Here it is:

Many people complain about these logs that I have in all my applications since I upgraded to Xcode 9 / iOS 11.

 2017-10-24 15:26:49.120556-0300 MyApp[1092:314222] TIC Read Status [55:0x0]: 1:57 2017-10-24 15:26:49.120668-0300 MyApp[1092:314222] TIC Read Status [55:0x0]: 1:57 2017-10-24 15:26:49.626199-0300 MyApp[1092:314617] TIC Read Status [56:0x0]: 1:57 

His answer:

It is important to understand that this ENOTCONN does not necessarily mean that something has gone wrong. Closed TCP connections are expected in all versions of HTTP. So, unless you have another symptom associated with this error, my recommendation is that you ignore it.

source: https://forums.developer.apple.com/message/272678#272678

SOLUTION: Wait for new versions / updates of Xcode 9.

Answer 2

This is how the TIC Read Status [11:0x0]: 1:57 breaks:

TIC expands to "TCP I / O connection", which is a subsystem on the CFNetwork that starts a TCP connection

11 - connection identifier in TIC

0x0 is a pointer to the TIC object itself

1 and 57 are the domain and code of CFStreamError, respectively; domain 1 is kCFStreamErrorDomainPOSIX, and within this domain 57 is ENOTCONN

Source: https://forums.developer.apple.com/thread/66058

Answer 3

Note. Like what @David mentions in a comment, this is not a good option. You can disable it because the console does not provide useful information when debugging crashes such as libc++abi.dylib: terminating with uncaught exception of type NSException .

However, for people who are wondering how to silence a warning, and until a better fix is ​​found, you can keep the variable handy and switch as needed.

Use the OS_ACTIVITY_MODE = disable environment variable in the "Arguments" section of the product schemas to avoid console leakage with such warnings.

Note B: Turn it on to see the effect.

Source: https://medium.com/@adinugroho/disable-os-logging-in-xcode-8-ec6d38502532