Post

Replies

Boosts

Views

Activity

Receiving "The request timed out." when using NSURLSession
Hi all, I'm facing a very strange problem in my application. In particular, using the application when a request receives a timeout message, all the following ones receive a timeout too (see screenshot). Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo={NSUnderlyingError=0x28113a550 {Error Domain=kCFErrorDomainCFNetwork Code=-1001 "(null)" UserInfo={_kCFStreamErrorCodeKey=-2102, _kCFStreamErrorDomainKey=4}}, NSErrorFailingURLStringKey=https://MY_SERVER_URL, NSErrorFailingURLKey=https://MY_SERVER_URL, _kCFStreamErrorDomainKey=4, _kCFStreamErrorCodeKey=-2102, NSLocalizedDescription=The request timed out.} I'm not sure if this happens when the application enters the foreground after a background state since it's quite difficult to replicate. Based on what exposed, do you any clue why this can happen? additionally, is there a way to replicate a similar behavior in a consistent way? Waiting for a reply I thank you for your attention. Thanks, Lorenzo
5
0
6.9k
Dec ’21
Meaning of "No Connection" in Network Instruments
Hi all, I'm facing a strange timeout problem in my application. I've opened another thread for that [Receiving "The request timed out." when using NSURLSession].(https://developer.apple.com/forums/thread/696762) Based on Xcode 13 Network Instruments, when a network request receives a timeout, all the subsequent ones receive the timeout too. Those requests are hitting the same host / domain that works with HTTP/1 (head of line blocking?). Instead, other request that do not involve this domain are working correctly. I've collected a trace but I cannot understand the meaning of "No Connection" and the red color of the box under inspection. Are you able to clarify their meaning and when this scenario could happen? Thanks, Lorenzo
1
0
805
Dec ’21
Understanding how Xcode Organizer Crashes Report works
Hi, I'm writing here in order to make sense of how Xcode Organizer Crashes Report works. In particular, I'm experiencing strange behaviors when I switch among filters (date, version, builds, etc.): if I select, for example, "Last Two Weeks" filter, the latest version of the app, "All Builds" and "App Store", I see additional crashes (new crash entries) compared to using a specific build (we just have one single build for that version that is published in the App Store). I'm noticing the same behavior when, for example, I select "App Store or Test Flight" filter without selecting the specific build ("All Builds" is set). furthermore, I would like to know if a crash that is reported in a previous version will be available in the latest one if not fixed or not experienced anymore by users. Waiting for a reply I thank you for your feedback. All the best, Lorenzo
0
1
530
Aug ’23