Hi
Getting a crash mainly on iOS 15 with the Apple network thread. From our logs seems like in many locations in the app. Anyone any advice on how to debug it.
Apple crash log below:
iOS 15.2b2 (19C5036e) … does not have the fix for this bug (r. 84641488).
Yesterday we started seeding iOS 15.2b3 (19C5044b). My understanding is that this includes the fix for this bug (yay!). Please let us know if you see any evidence to the contrary.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
Hi eskimo! Our users using iOS 15.2 are still experiencing this crash, by far the most important crash we have in the application :/
Is it possible to disable HTTP/3 in the client side for a specific server side host?
shuaichaolian wrote:
Is there any way to bypass this problem?
Not on the client side.
xinlinp wrote:
if it is public?
It is not.
iOS 13.2 was just released and I recommend that you encourage your users to upgrade.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
Seemingly out of no where I have just started to see this crash pop up as our #1 crash in app. It is a repetitive crash for most users that see it.
Same here
Same here. I started to see this crash on Jan 12th (around 9 PM GMT) out of nowhere. It's our #1 crash at the moment.
It seems that the issue is still around or a new one creeped in? I can see a number of crashes in Crashlytics on iOS 15.5.0.
Crashed: com.apple.network.connections
0 libquic.dylib 0x6b06c qlog_abort_internal + 276
1 libquic.dylib 0x6b058 qlog_abort_internal + 256
2 libquic.dylib 0x239e4 quic_send_frames_for_key_state + 3928
3 libquic.dylib 0x301e0 quic_migration_probe_path + 1532
4 libquic.dylib 0x33010 quic_migration_new_cid + 156
5 libquic.dylib 0x110e0 quic_frame_process_NEW_CONNECTION_ID + 4080
6 libquic.dylib 0x647cc quic_frame_process + 140
7 libquic.dylib 0x169c4 quic_process_inbound + 1376
8 libnetwork.dylib 0x5dd5f0 nw_protocol_data_access_buffer + 1064
9 libquic.dylib 0x157cc __quic_handle_inbound_block_invoke + 152
10 libquic.dylib 0x10bc quic_handle_inbound + 124
11 libnetwork.dylib 0x5c048c __nw_protocol_implementation_get_input_internal_block_invoke + 136
12 libnetwork.dylib 0x5bf60c nw_protocol_implementation_get_input_internal + 252
13 libnetwork.dylib 0x5be7f8 nw_protocol_implementation_read + 436
14 libnetwork.dylib 0x5bdf08 nw_protocol_implementation_input_available + 96
15 libnetwork.dylib 0x514698 nw_channel_add_input_frames + 9236
16 libnetwork.dylib 0x512198 nw_channel_update_input_source + 328
17 libnetwork.dylib 0x5113a4 __nw_channel_create_block_invoke.29 + 72
18 libdispatch.dylib 0x3a30 _dispatch_client_callout + 20
19 libdispatch.dylib 0x6eec _dispatch_continuation_pop + 500
20 libdispatch.dylib 0x1a13c _dispatch_source_invoke + 1596
21 libdispatch.dylib 0xcf80 _dispatch_workloop_invoke + 1784
22 libdispatch.dylib 0x16500 _dispatch_workloop_worker_thread + 648
23 libsystem_pthread.dylib 0x10bc _pthread_wqthread + 288
24 libsystem_pthread.dylib 0xe5c start_wqthread + 8
If you're seeing this issue again after it was previously fixed them please open a bug report with a sysdiagnose.