Odd network error/warning in latest iOS 13 Beta 4

This issue doesn't happen in iOS 11 or iOS 12. I don't believe it happened in earlier iOS 13 betas. Although it looks like a crash, the app keeps working and getting data. However every time it gets data from the backend the error occurs. Any ideas?



019-07-18 15:45:43.161236-0400 MYAPP[56691:8522761] [] __nwlog_err_simulate_crash simulate crash already simulated "nw_endpoint_get_type called with null endpoint"

2019-07-18 15:45:43.164858-0400 MYAPP[56691:8522761] [] nw_endpoint_get_type called with null endpoint, dumping backtrace:

[x86_64] libnetcore-1872

0 libnetwork.dylib 0x00000001126be068 __nw_create_backtrace_string + 120

1 libnetwork.dylib 0x000000011262049f nw_endpoint_get_type + 175

2 libboringssl.dylib 0x0000000140ac4a6a nw_protocol_boringssl_get_subject_name + 178

3 libboringssl.dylib 0x0000000140ac7911 nw_protocol_boringssl_connected + 916

4 libnetwork.dylib 0x00000001124d655f nw_socket_connect + 239

5 libboringssl.dylib 0x0000000140ac74ee nw_protocol_boringssl_connect + 357

6 CFNetwork 0x0000000112a7e11a _CFURLStorageSessionCopyCache + 22727

7 libnetwork.dylib 0x00000001123954f8 nw_endpoint_flow_connect + 184

8 libnetwork.dylib 0x00000001123a23b9 nw_endpoint_handler_append_and_start_application_protocol + 3417

9 libnetwork.dylib 0x00000001125bc576 __nw_connection_append_and_start_application_protocol_block_invoke + 70

10 libnetwork.dylib 0x00000001126b942a nw_queue_context_async_if_needed + 74

11 libnetwork.dylib 0x00000001125bc240 nw_connection_append_and_start_application_protocol + 160

12 CFNetwork 0x000000011291e957 CFURLDownloadCancel + 113751

13 CFNetwork 0x000000011291e700 CFURLDownloadCancel + 113152

14 CFNetwork 0x000000011298083c _CFStreamErrorFromCFError + 279310

15 CFNetwork 0x00000001128a97b9 _CFHTTPMessageSetResponseProxyURL + 55146

16 CFNetwork 0x00000001128a946f _CFHTTPMessageSetResponseProxyURL + 54304

17 CFNetwork 0x00000001128a932e _CFHTTPMessageSetResponseProxyURL + 53983

18 CFNetwork 0x00000001128aa864 _CFHTTPMessageSetResponseProxyURL + 59413

19 CFNetwork 0x0000000112a6c370 __CFNetworkAgentMessageProcessorMain + 115008

20 CFNetwork 0x0000000112a6d1af __CFNetworkAgentMessageProcessorMain + 118655

21 CFNetwork 0x0000000112a6cd26 __CFNetworkAgentMessageProcessorMain + 117494

22 CFNetwork 0x0000000112a6c95e __CFNetworkAgentMessageProcessorMain + 116526

23 CFNetwork 0x0000000112a6c409 __CFNetworkAgentMessageProcessorMain + 115161

24 CFNetwork 0x0000000112a69fb5 __CFNetworkAgentMessageProcessorMain + 105861

25 CFNetwork 0x0000000112a69774 __CFNetworkAgentMessageProcessorMain + 103748

26 CFNetwork 0x0000000112a1c865 _CFNetworkHTTPConnectionCacheSetLimit + 183261

27 libdispatch.dylib 0x0000000112f21de4 _dispatch_call_block_and_release + 12

28 libdispatch.dylib 0x0000000112f22d58 _dispatch_client_callout + 8

29 libdispatch.dylib 0x0000000112f295ff _dispatch_lane_serial_drain + 788

30 libdispatch.dylib 0x0000000112f2a1c5 _dispatch_lane_invoke + 476

31 libdispatch.dylib 0x0000000112f2b815 _dispatch_workloop_invoke + 2631

32 libdispatch.dylib 0x0000000112f35a4d _dispatch_workloop_worker_thread + 722

33 libsystem_pthread.dylib 0x0000000113396611 _pthread_wqthread + 421

34 libsystem_pthread.dylib 0x00000001133963fd start_wqthread + 13

I have the same issue on a real device.


Also I didn't use any network at all. What I used was only RealmSwift framework.

I also initially observed it on a physical device. I used the simulators to confirm that it happened only in iOS 13 beta 4, and not on iOS 12 and iOS 11. For me it appears to happen as soon as the app connects to our server.


Hopefully this is just diagnostics and not an indication of a real issue.

I have the same issue:

dumping backtrace:

[x86_64] libnetcore-1872

0 libnetwork.dylib 0x00007fff500df068 __nw_create_backtrace_string + 120

1 libnetwork.dylib 0x00007fff5004149f nw_endpoint_get_type + 175

2 libboringssl.dylib 0x00007fff4ef09a6a nw_protocol_boringssl_get_subject_name + 178

3 libboringssl.dylib 0x00007fff4ef0c911 nw_protocol_boringssl_connected + 916

4 libnetwork.dylib 0x00007fff4fefcfdf nw_socket_handle_socket_event + 1711

5 libdispatch.dylib 0x000000010b62ed58 _dispatch_client_callout + 8

6 libdispatch.dylib 0x000000010b6316ca _dispatch_continuation_pop + 552

7 libdispatch.dylib 0x000000010b644a83 _dispatch_source_invoke + 2205

8 libdispatch.dylib 0x000000010b637815 _dispatch_workloop_invoke + 2631

9 libdispatch.dylib 0x000000010b641a4d _dispatch_workloop_worker_thread + 722

10 libsystem_pthread.dylib 0x00007fff511fd6d3 _pthread_wqthread.cold.1 + 125

11 libsystem_pthread.dylib 0x00007fff511f7856 _pthread_wqthread + 203

12 libsystem_pthread.dylib 0x00007fff511f7717 start_wqthread + 15

I have the same issue in the SwiftUI (debug) Peview and a iPhone Xr-simulator too.

I'm working on a little project that started showing this error after I started using Realm. It was fine before that.
(Using Xcode Beta 4 and SwiftUI)

I have the same issue in our project, I am sure our app is okay in Xcode11 beta3 and before, but the new issue in beta4 seriouly block our test in Xcode11 compatible, i have to roll back to beta3 now, please help to fix the issue.


nw_endpoint_get_type called with null endpoint, dumping backtrace:

[x86_64] libnetcore-1872

0 libnetwork.dylib 0x00007fff500df068 __nw_create_backtrace_string + 120

1 libnetwork.dylib 0x00007fff5004149f nw_endpoint_get_type + 175

2 libboringssl.dylib 0x00007fff4ef09a6a nw_protocol_boringssl_get_subject_name + 178

3 libboringssl.dylib 0x00007fff4ef0c911 nw_protocol_boringssl_connected + 916

4 libnetwork.dylib 0x00007fff4fef755f nw_socket_connect + 239

5 libboringssl.dylib 0x00007fff4ef0c4ee nw_protocol_boringssl_connect + 357

6 CFNetwork 0x00007fff22ea311a _CFURLStorageSessionCopyCache + 22727

7 libnetwork.dylib 0x00007fff4fdb64f8 nw_endpoint_flow_connect + 184

8 libnetwork.dylib 0x00007fff4fdc33b9 nw_endpoint_handler_append_and_start_application_protocol + 3417

9 libnetwork.dylib 0x00007fff4ffdd576 __nw_connection_append_and_start_application_protocol_block_invoke + 70

10 libnetwork.dylib 0x00007fff500da42a nw_queue_context_async_if_needed + 74

11 libnetwork.dylib 0x00007fff4ffdd240 nw_connection_append_and_start_application_protocol + 160

12 CFNetwork 0x00007fff22d43957 CFURLDownloadCancel + 113751

13 CFNetwork 0x00007fff22d43700 CFURLDownloadCancel + 113152

14 CFNetwork 0x00007fff22da583c _CFStreamErrorFromCFError + 279310

15 CFNetwork 0x00007fff22cce7b9 _CFHTTPMessageSetResponseProxyURL + 55146

16 CFNetwork 0x00007fff22cce46f _CFHTTPMessageSetResponseProxyURL + 54304

17 CFNetwork 0x00007fff22cce32e _CFHTTPMessageSetResponseProxyURL + 53983

18 CFNetwork 0x00007fff22ccf864 _CFHTTPMessageSetResponseProxyURL + 59413

19 CFNetwork 0x00007fff22e91370 __CFNetworkAgentMessageProcessorMain + 115008

20 CFNetwork 0x00007fff22e921af __CFNetworkAgentMessageProcessorMain + 118655

21 CFNetwork 0x00007fff22e91d26 __CFNetworkAgentMessageProcessorMain + 117494

22 CFNetwork 0x00007fff22e9195e __CFNetworkAgentMessageProcessorMain + 116526

23 CFNetwork 0x00007fff22e91409 __CFNetworkAgentMessageProcessorMain + 115161

24 CFNetwork 0x00007fff22e8efb5 __CFNetworkAgentMessageProcessorMain + 105861

25 CFNetwork 0x00007fff22e8e774 __CFNetworkAgentMessageProcessorMain + 103748

26 CFNetwork 0x00007fff22e41865 _CFNetworkHTTPConnectionCacheSetLimit + 183261

27 libdispatch.dylib 0x0000000115442de4 _dispatch_call_block_and_release + 12

28 libdispatch.dylib 0x0000000115443d58 _dispatch_client_callout + 8

29 libdispatch.dylib 0x000000011544a5ff _dispatch_lane_serial_drain + 788

30 libdispatch.dylib 0x000000011544b1c5 _dispatch_lane_invoke + 476

31 libdispatch.dylib 0x000000011544c815 _dispatch_workloop_invoke + 2631

32 libdispatch.dylib 0x0000000115456a4d _dispatch_workloop_worker_thread + 722

33 libsystem_pthread.dylib 0x00007fff511f3611 _pthread_wqthread + 421

34 libsystem_pthread.dylib 0x00007fff511f33fd start_wqthread + 13



(Using Xcode Beta 4)

I just installed the Xcode 11.0 beta 4 (11M374r) and attempted to run in the simulator. I'm seeing this after launch:


2019-07-24 14:24:17.041578-0600 App[12150:11838368] [] __nwlog_err_simulate_crash simulate crash already simulated "nw_endpoint_get_type called with null endpoint"
2019-07-24 14:24:17.041828-0600 App[12150:11838368] [] nw_endpoint_get_type called with null endpoint, dumping backtrace:
        [x86_64] libnetcore-1872
    0   libnetwork.dylib                    0x00007fff500df068 __nw_create_backtrace_string + 120
    1   libnetwork.dylib                    0x00007fff5004149f nw_endpoint_get_type + 175
    2   libboringssl.dylib                  0x00007fff4ef09a6a nw_protocol_boringssl_get_subject_name + 178
    3   libboringssl.dylib                  0x00007fff4ef0c911 nw_protocol_boringssl_connected + 916
    4   libnetwork.dylib                    0x00007fff4fefcfdf nw_socket_handle_socket_event + 1711
    5   libdispatch.dylib                   0x000000010b873d58 _dispatch_client_callout + 8
    6   libdispatch.dylib                   0x000000010b8766ca _dispatch_continuation_pop + 552
    7   libdispatch.dylib                   0x000000010b889a83 _dispatch_source_invoke + 2205
    8   libdispatch.dylib                   0x000000010b87c815 _dispatch_workloop_invoke + 2631
    9   libdispatch.dylib                   0x000000010b886a4d _dispatch_workloop_worker_thread + 722
    10  libsystem_pthread.dylib             0x00007fff511f3611 _pthread_wqthread + 421
    11  libsystem_pthread.dylib             0x00007fff511f33fd start_wqthread + 13

and as I navigate around our application.

If you go to the Breakpoints menu in the left pane, add a Runtime Issue Breakpoint for System Frameworks and you'll stop when the actual error is happening (and be able to identify the problem library). Am seeing the same issue in my case from FirebaseInstanceID in


- (void)checkinWithExistingCheckin:(FIRInstanceIDCheckinPreferences *)existingCheckin

completion:(FIRInstanceIDDeviceCheckinCompletion)completion


and specifically with NSURLSessionDataTask



NSURLSessionDataTask *task = [self.session dataTaskWithRequest:request completionHandler:handler];



I suspect this is an Apple beta bug so going to report to them but will check out the Firebase side of things too. Hope that helps.

UPDATE: Removing Firebase/Performance from the solution fixed the issue. Still no idea if it's Firebase or Apple that caused the issue but it's definitely some combo of the two. I've run into a couple issues now with Firebase Performance installed alongside Firebase Analytics/Remote Config so am not that surprised.

I have the same issue:


2019-08-02 17:01:26.763235+0800 App[14522:138289] []nw_endpoint_get_type called with null endpoint

2019-08-02 17:01:26.763235+0800 App[14522:138289] [] nw_endpoint_get_type called with null endpoint, dumping backtrace:

[x86_64] libnetcore-1872

0 libnetwork.dylib 0x00007fff500df068 __nw_create_backtrace_string + 120

1 libnetwork.dylib 0x00007fff5004149f nw_endpoint_get_type + 175

2 libboringssl.dylib 0x00007fff4ef09a6a nw_protocol_boringssl_get_subject_name + 178

3 libboringssl.dylib 0x00007fff4ef0c911 nw_protocol_boringssl_connected + 916

4 libnetwork.dylib 0x00007fff4fefcfdf nw_socket_handle_socket_event + 1711

5 libdispatch.dylib 0x000000010db10d58 _dispatch_client_callout + 8

6 libdispatch.dylib 0x000000010db136ca _dispatch_continuation_pop + 552

7 libdispatch.dylib 0x000000010db26a83 _dispatch_source_invoke + 2205

8 libdispatch.dylib 0x000000010db19815 _dispatch_workloop_invoke + 2631

9 libdispatch.dylib 0x000000010db23a4d _dispatch_workloop_worker_thread + 722

10 libsystem_pthread.dylib 0x00007fff511f3611 _pthread_wqthread + 421

11 libsystem_pthread.dylib 0x00007fff511f33fd start_wqthread + 13

I have the same question on xcode 11 beta4 iPhone 8 Simulator iOS 13 beta.

Odd network error/warning in latest iOS 13 Beta 4
 
 
Q