NSURLConnection finished with error - code -1001

2,118 views
Skip to first unread message

Richard Fan

unread,
Jul 11, 2018, 3:01:33 AM7/11/18
to Google Mobile Ads SDK Developers
in these days, I found admob can't show ads in some devices (iOS 11.4).
I have debugged this issue, and found the below logs.
----

2018-07-11 00:56:40.242790+0800 GoodReader[2852:986647] [] tcp_timers tcp[4] retransmit SYN 3

2018-07-11 00:56:40.292947+0800 GoodReader[2852:986647] [] tcp_timers tcp[5] retransmit SYN 3

2018-07-11 00:56:41.248268+0800 GoodReader[2852:986647] [] tcp_timers tcp[4] retransmit SYN 4

2018-07-11 00:56:41.299647+0800 GoodReader[2852:986647] [] tcp_timers tcp[5] retransmit SYN 4

2018-07-11 00:56:42.252846+0800 GoodReader[2852:986647] [] tcp_timers tcp[4] retransmit SYN 5

2018-07-11 00:56:42.302811+0800 GoodReader[2852:986647] [] tcp_timers tcp[5] retransmit SYN 5

2018-07-11 00:56:44.254738+0800 GoodReader[2852:986647] [] tcp_timers tcp[4] retransmit SYN 6

2018-07-11 00:56:44.309143+0800 GoodReader[2852:986647] [] tcp_timers tcp[5] retransmit SYN 6

2018-07-11 00:56:48.256414+0800 GoodReader[2852:986643] [] tcp_timers tcp[4] retransmit SYN 7

2018-07-11 00:56:48.315795+0800 GoodReader[2852:986643] [] tcp_timers tcp[5] retransmit SYN 7

2018-07-11 00:56:56.262118+0800 GoodReader[2852:986647] [] tcp_timers tcp[4] retransmit SYN 8

2018-07-11 00:56:56.325257+0800 GoodReader[2852:986647] [] tcp_timers tcp[5] retransmit SYN 8

2018-07-11 00:57:00.019216+0800 GoodReader[2852:986428] Status bar could not find cached time string image. Rendering in-process.

2018-07-11 00:57:12.268898+0800 GoodReader[2852:986647] [] tcp_timers tcp[4] retransmit SYN 9

2018-07-11 00:57:12.336495+0800 GoodReader[2852:986647] [] tcp_timers tcp[5] retransmit SYN 9

2018-07-11 00:57:44.270810+0800 GoodReader[2852:986643] [] tcp_timers tcp[4] retransmit SYN 10

2018-07-11 00:57:44.337423+0800 GoodReader[2852:986643] [] tcp_timers tcp[5] retransmit SYN 10

2018-07-11 00:57:52.259319+0800 GoodReader[2852:987026] TIC TCP Conn Failed [4:0x1d0176680]: 1:60 Err(60)

2018-07-11 00:57:52.259903+0800 GoodReader[2852:987026] Task <6EBC2D34-C17F-4491-896B-B58A7FE6E4F4>.<0> HTTP load failed (error code: -1001 [1:60])

2018-07-11 00:57:52.260347+0800 GoodReader[2852:986647] NSURLConnection finished with error - code -1001

2018-07-11 00:57:52.305842+0800 GoodReader[2852:987026] TIC TCP Conn Failed [5:0x1d0177580]: 1:60 Err(60)

2018-07-11 00:57:52.306038+0800 GoodReader[2852:987026] Task <45183138-6353-42AC-A4EF-744079E69806>.<0> HTTP load failed (error code: -1001 [1:60])

2018-07-11 00:57:52.306470+0800 GoodReader[2852:987081] NSURLConnection finished with error - code -1001

2018-07-11 00:57:55.405253+0800 GoodReader[2852:987026] [] tcp_timers tcp[6] retransmit SYN 3

2018-07-11 00:57:56.408789+0800 GoodReader[2852:987080] [] tcp_timers tcp[6] retransmit SYN 4

2018-07-11 00:57:57.414426+0800 GoodReader[2852:987080] [] tcp_timers tcp[6] retransmit SYN 5

2018-07-11 00:57:59.418637+0800 GoodReader[2852:987080] [] tcp_timers tcp[6] retransmit SYN 6

2018-07-11 00:58:00.007749+0800 GoodReader[2852:986428] Status bar could not find cached time string image. Rendering in-process.

2018-07-11 00:58:03.421764+0800 GoodReader[2852:987080] [] tcp_timers tcp[6] retransmit SYN 7

2018-07-11 00:58:11.424115+0800 GoodReader[2852:986647] [] tcp_timers tcp[6] retransmit SYN 8

2018-07-11 00:58:27.428362+0800 GoodReader[2852:987201] [] tcp_timers tcp[6] retransmit SYN 9

2018-07-11 00:58:59.431595+0800 GoodReader[2852:987201] [] tcp_timers tcp[6] retransmit SYN 10

2018-07-11 00:59:00.007297+0800 GoodReader[2852:986428] Status bar could not find cached time string image. Rendering in-process.

2018-07-11 00:59:07.404630+0800 GoodReader[2852:987201] TIC TCP Conn Failed [6:0x1c8170bc0]: 1:60 Err(60)

2018-07-11 00:59:07.405005+0800 GoodReader[2852:987201] Task <4817A7C7-7E17-4AA3-AEC2-8728A41FBC77>.<0> HTTP load failed (error code: -1001 [1:60])

2018-07-11 00:59:07.405491+0800 GoodReader[2852:987358] NSURLConnection finished with error - code -1001

2018-07-11 00:59:10.426533+0800 GoodReader[2852:987359] [] tcp_timers tcp[7] retransmit SYN 3

----

I used xcode 9.4.1 and admob sdk 7.31.0, I debug it in simulator, the ads works well, when I debug it in real device, it can't show admob ads (interstitial and banner ads), in the real device, I can run third-party apps which can show google ads.

It's very strange to me, can you give me help?


Richard Fan

mobileadssdk-a...@google.com

unread,
Jul 11, 2018, 5:01:30 AM7/11/18
to Richard Fan, Google Mobile Ads SDK Developers
Hi Richard,

Thank you for reaching out to us.

Since you are able to display ads on an iOS simulator, then it's enough confirmation that your code implementation of the Mobile Ads SDK is working correctly.

On the other hand, the logs doesn't seem to suggest anything that could have prevented the ads from loading, however, to help us pinpoint the root cause of the issue, could you capture the error code returned (via Ad events) when ads failed to load on your end?

For us to test on our end, could you provide to us the Ad Unit Ids in question privately using Reply privately to author option?

Regards,
Ivan Bautista
Mobile Ads SDK Team

mobileadssdk-a...@google.com

unread,
Jul 12, 2018, 3:49:23 AM7/12/18
to Richard Fan, Google Mobile Ads SDK Developers
Hi Richard,

Thank you for providing the Ad Unit Ids privately and other helpful details.

I tested them with our sample apps and I kept on getting No fill error on an actual device. However, when I set my device as an enabled test device, I was able to load ads on my end. Thus, it's possible that there are just no available ads at the moment for your Ad Unit Ids.

On the other hand, it's odd that the didFailToReceiveAdWithError is not being invoked on your end when ads failed to load. Could you test with these modified sample apps (with Ad events implemented) and see if the didFailToReceiveAdWithError doesn't invoke when ads failed to load?

mobileadssdk-a...@google.com

unread,
Jul 12, 2018, 6:09:57 AM7/12/18
to Richard Fan, Google Mobile Ads SDK Developers
Hi Richard,

Below are my responses to your concerns raised privately.

thank you for your response, how to deal with No fill error on an actual device, it should be a normal action, should I took action for it?
The No fill error suggests that there are no available ads for your Ad Request at the moment but this doesn't mean that there's something wrong with your code implementation or with the Mobile Ads SDK. On the other hand, one way to possibly increase your Ad Inventory is to mediate to supported 3rd party Ad Networks.

for didFailToReceiveAdWithError invoke issue, in my device, the tcp will request again and again, till it request successfully, but it spend much time on it.
Do you mean to say that the didFailToReceiveAdWithError didn't invoke when ads failed to load even when using these modified sample apps? Maybe the callback was not triggered because the Ad Request are now returning ads successfully on your end as you've said and based from your recent device logs.

As for the "tcp_timers tcp[49] retransmit SYN 7" logs, I suggest that you raise this to the experts over at StackOverflow or Apple Developer forums as they can give you better insights on this.
Reply all
Reply to author
Forward
0 new messages