We're having issues with network calls on iOS with URLSessionDataTask waiting after~325 calls and all future calls timing out at 60s. We have cloudflare on our backend, are there any known issues with QUIC/HTTP/3 implementation on iOS with cloudflare?

We met many crashes like below on iOS 15, it seems multi-thread issue EXC_BAD_ACCESS. We get the dataServiceIdentifier on different threads. Does CTTelephonyNetworkInfo not thread-safe anymore from iOS 15? 0 libobjc.A.dylib _objc_retain 1 CoreTelephony -[CoreTelephonyClientMux cachedValueForSelector:] 2 CoreTelephony -[CoreTelephonyClient(Data) getCurrentDataServiceDescriptorSync:] 3 CoreTelephony -[CTTelephonyNetworkInfo dataServiceIdentifier]

QUIC support in Network framework in iOS 15 and macOS 12 seems to be aware of the datagram draft, but there doesn’t seem to be any way to configure NWProtocolQUIC.Options to set the datagram transport parameter (0x20). If I configure the server to send a datagram to a Swift client, it closes the connection with a PROTOCOL_VIOLATION frame with the error message "DATAGRAM frame size too big". Given that Eric Kinnear at Apple is an author of the datagram draft, is support for this intentionally missing? https://www.ietf.org/archive/id/draft-ietf-quic-datagram-03.html You can see a minimal example here: https://github.com/alta/swift-quic-datagram-example Thanks!

Tags

Hi, I am learning SwiftUI(typing level: awful), and trying to perform access to internet sites from within the application. However, i cannot figure out how to make it work. I have followed several different class examples, but none work in downloading a file. I am able to access the internet from within Safari on the simulator. Is there some setting, possibly within Xcode, that I need to set? What sort of debugging tools are available to try to debug the issue. Many Thanks, Rob