Excessive Console logs

ios

#1

I’ve recently updated my {N} version to 4.0.1 and now I’m seeing a lot of extra really annoying http-related console logs in my iOS terminal. I didn’t used to have them and now they’re clogging up my terminal and making debugging more difficult. Here’s what I mean:

TIC TCP Conn Cancel [1:0x10d343730]
[1 stream, pid: 1482, url: {{url}}, tls] cancelled
[1.1 5F5002E2-DD06-45EC-8DEA-A047C7011A31 .53690<->]
Connected Path: satisfied (Path is satisfied), interface: en0, ipv4, dns
Duration: 120.386s, DNS @0.004s took 0.071s, TCP @0.086s took 0.010s, TLS took 0.078s
bytes in/out: 4386/923, packets in/out: 9/9, rtt: 0.011s, retransmitted packets: 0, out-of-order packets: 0
TIC TCP Conn Destroyed [1:0x10d343730]
TIC Read Status [1:0x0]: 1:57
TIC Read Status [1:0x0]: 1:57
Task <7130F128-5A53-4ED2-BF45-67FC1EE0CE96>.<96> now using Connection 2
Task <646B0B4D-ED89-49B9-8AB8-BDE46CF5FFCF>.<98> now using Connection 3
Task <646B0B4D-ED89-49B9-8AB8-BDE46CF5FFCF>.<98> sent request, body N
Task <1BF0BAE9-D532-44CF-BCAC-433CC4A0CEF2>.<97> now using Connection 4
Task <7130F128-5A53-4ED2-BF45-67FC1EE0CE96>.<96> sent request, body N
Task <1BF0BAE9-D532-44CF-BCAC-433CC4A0CEF2>.<97> sent request, body N
Task <646B0B4D-ED89-49B9-8AB8-BDE46CF5FFCF>.<98> received response, status 200 content K
Task <646B0B4D-ED89-49B9-8AB8-BDE46CF5FFCF>.<98> response ended
Task <7130F128-5A53-4ED2-BF45-67FC1EE0CE96>.<96> received response, status 200 content K
Task <7130F128-5A53-4ED2-BF45-67FC1EE0CE96>.<96> response ended
Task <1BF0BAE9-D532-44CF-BCAC-433CC4A0CEF2>.<97> received response, status 200 content K
Task <1BF0BAE9-D532-44CF-BCAC-433CC4A0CEF2>.<97> response ended

And it just continuously prints that so I have to go searching for my actual logs. Googling this didn’t seem to come up with anything.

Any way to get rid of this?


#2

This is a bit of an old question, but for reference for future internet searchers, there is more discussion around this issue on Github:

It seems this problem might(?) be related to use of the {N} Firebase plug-in. Hopefully a good permanent fix to filter these extra messages in the console will be available soon.