Hi Apple Team, I have to do some such functionality in my applications that when application is in background, I have to upload the entire gallery assets of the iphone to a server (if the user has given permission to upload). I have come to a point where my background processing is not running for more than 28-30 seconds. And my process is such that I pick up the asset one by one from the gallery and process it and put it in a single task for uploading to the background thread. All this happens in a loop and photos are uploaded one after the other untill 28-30 seconds(in background). As I have also got my app registered for background processing and also coding is running from all standard process according to apple documentation. So I have to ask you something about background processing, my questions are as follows: 1: What is the maximum duration for background processing and background uploading? What if I want to increase the duration of background processing in my app? 2: Does Apple extend the background processing time for certain category of apps, if it does, then please mention those categories(Or share some links). 3: As my application is built for a particular organization(they upload their all photos), I need maximum background upload limit, is there any way Apple provides for that? if yes, could you please share sample code base or links. 4: Some applications like Google Photos etc. upload in the background for more than 30 seconds, is there a standard procedure that I can achieve as well? 5: If there is any framework provided by Apple to do this work then please mention it. Thanks, I am waiting for your kind reply.

Hello We are developing our own iOS Network Extensions-based VPN and it has an HTTP proxy in the VPN. In addition, we also use PAC (Proxy auto-configuration) script to configure what kind of HTTP/HTTPS traffic should route to our proxy in the VPN. However, we get this kind of message "Received XPC error Connection invalid for message type 3 kCFNetworkAgentXPCMessageTypePACQuery" randomly on iOS 15.5. We have not been aware of any weird behavior of iOS based on the error message. We are afraid of this error message is caused by our VPN solution. Is there any suggestion that should consider or follow to fix this error?

finished with error [-1001] Error Domain=NSURLErrorDomain Code=-1001 “The request timed out.” UserInfo={_kCFStreamErrorCodeKey=-2102, NSUnderlyingError=0x282fbd800 {Error Domain=kCFErrorDomainCFNetwork Code=-1001 “(null)” UserInfo={_kCFStreamErrorCodeKey=-2102, _kCFStreamErrorDomainKey=4}}, _NSURLErrorFailingURLSessionTaskErrorKey=LocalDataTask <7060BA29-10BA-40C9-91AB-DCA082E5F038>.<235>, _NSURLErrorRelatedURLSessionTaskErrorKey=(  “LocalDataTask <7060BA29-10BA-40C9-91AB-DCA082E5F038>.<235>” ),NSLocalizedDescription=The request timed out., NSErrorFailingURLStringKey=<xyz.com>, NSErrorFailingURLKey=<xyz.com>, _kCFStreamErrorDomainKey=4} getting this issue in some rare scenario, unable to find solution for this? anyone can help to resolve this? because of this issue some times app stucks with loader screen and unable to work further. I just replaced our server url with <xyz.com>. I have checked with iPad 3rd generation.

I am using URLSessionConfiguration.background and uploadTask to upload a file from an iOS app. request.httpMethod = "POST" request.setValue("application/octect-stream", forHTTPHeaderField: "Content-Type") let task = uploadURLSession.uploadTask(with: request, fromFile: fileURL) I'd like to understand how to manage the error handling. How the http errors 4xx or 5xx are handled by the URLSession.uploadTask?

I want to use URLCache to make data (e.g. User, Session, Privileges objects) available when offline. I think it is better to manually saving data in file or UserDefaults because it will fit seamlessly with existing code that load stuff from URLs and without extra code. One of my concern is this. In URLCache documentation - https://developer.apple.com/documentation/foundation/urlcache, it says: Note In iOS, the on-disk cache may be purged when the system runs low on disk space, but only when your app is not running. I don't want my on-disk cache to get purged on low disk space. I browse around and see URLCache has a new initializer in iOS 13 that accepts a directory url for on-disk cache. convenience init(memoryCapacity: Int, diskCapacity: Int, directory: URL? = nil) From my understanding, Caches directory gets purged on low disk space. From File System Programming Guide - https://developer.apple.com/library/archive/documentation/FileManagement/Conceptual/FileSystemProgrammingGuide/FileSystemOverview/FileSystemOverview.html: In iOS 5.0 and later, the system may delete the Caches directory on rare occasions when the system is very low on disk space. This will never occur while an app is running. However, be aware that restoring from backup is not necessarily the only condition under which the Caches directory can be erased. So, my question is, if I pass a URL that is not a Caches directory URL. Will my on-disk cache survive the low memory purge? If not, is there any other way to achieve it?

https://developer.apple.com/documentation/foundation/urlcache has this: "Although URLCache instance methods can safely be called from multiple execution contexts at the same time, be aware that methods like  cachedResponse(for:) and storeCachedResponse(_:for:) have an unavoidable race condition when attempting to read or write responses for the same request." What does it mean "unavoidable"? If I put a lock (mutex / NSLock, or similar) in my wrappers on top of "cachedResponse" / "storeCachedResponse" would that avoid the mentioned race condition? Also, what do they mean by "the same request"? A few examples below: let url = URL(string: "https://www.apple.com")! let req1 = URLRequest(url: url) let req2 = req1 // perhaps "the same" let req3 = URLRequest(url: url) // "the same"? let req4 = URLRequest(url: req1.url!) // "the same"? let req5 = URLRequest(url: url, cachePolicy: req1.cachePolicy, timeoutInterval: req1.timeoutInterval) // "the same"? let req6 = URLRequest(url: url, cachePolicy: req1.cachePolicy, timeoutInterval: 1234) // "the same"? let req7 = URLRequest(url: url, cachePolicy: .reloadIgnoringCacheData, timeoutInterval: req1.timeoutInterval) // "the same"? assert(req1 == req2) assert(req1 == req3) assert(req1 == req4) assert(req1 == req5) assert(req1 == req6) // this is ok assert(req1 == req7) // this fails

Report I have an application that apparently crashed for one of my users. Does anyone have any idea what might have caused this crash? I tried Reproducing the bug, but I had no success. I don't even know what use case would cause such a crash Looking into some other posts with similar problems, but couldn't find anything close to this issue In the next section, I provided you with some information that might be useful. If anything else is needed, feel free to let me know. Crash details Date May 3, 2022, 6:02:02 PM Device iPhone 11 - iOS 15.4.1 Stack trace Crashed: com.apple.CFNetwork.Connection 0 libsystem_kernel.dylib 0x7b78 __pthread_kill + 8 1 libsystem_pthread.dylib 0x73bc pthread_kill + 268 2 libsystem_c.dylib 0x2051c abort + 168 3 libsystem_malloc.dylib 0x1ca04 _malloc_put + 550 4 libsystem_malloc.dylib 0x1cc9c malloc_zone_error + 100 5 libsystem_malloc.dylib 0x170dc nanov2_allocate_from_block + 568 6 libsystem_malloc.dylib 0x16164 nanov2_allocate + 128 7 libsystem_malloc.dylib 0x16080 nanov2_malloc + 64 8 libsystem_malloc.dylib 0x6020 _malloc_zone_malloc + 156 9 libsystem_blocks.dylib 0x1630 _Block_copy + 64 10 libdispatch.dylib 0x1e2c _dispatch_Block_copy + 32 11 libdispatch.dylib 0x3bf8 _dispatch_block_create + 160 12 libdispatch.dylib 0x71e4 dispatch_block_create_with_qos_class + 256 13 libnetwork.dylib 0xbdac8 nw_connection_async_on_queue + 88 14 libnetwork.dylib 0xe35c0 nw_connection_report_state_with_handler_on_nw_queue + 1136 15 libnetwork.dylib 0xe3e80 nw_connection_set_state_on_nw_queue + 304 16 libnetwork.dylib 0x8c5a4 nw_connection_endpoint_report_on_nw_queue + 21732 17 libnetwork.dylib 0xb24a4 nw_endpoint_handler_report + 304 18 libnetwork.dylib 0x11509c -[NWConcrete_nw_endpoint_resolver startWithHandler:] + 2124 19 libnetwork.dylib 0x79d18 nw_endpoint_handler_path_change + 8984 20 libnetwork.dylib 0xa5798 nw_endpoint_handler_start + 1084 21 libnetwork.dylib 0xab124 __nw_connection_start_block_invoke + 1408 22 libnetwork.dylib 0xd5384 nw_connection_start + 252 23 CFNetwork 0x1b570 CFURLRequestCopyHTTPRequestMethod + 912 24 CFNetwork 0x1c1b0 CFHTTPMessageCopyBody + 536 25 CFNetwork 0x116be0 CFURLDownloadCancel + 77848 26 CFNetwork 0x19464 CFURLRequestSetURL + 10348 27 CFNetwork 0x12100 CFURLCacheSetMemoryCapacity + 8996 28 CFNetwork 0x110b8 CFURLCacheSetMemoryCapacity + 4828 29 CFNetwork 0x184e98 _CFNetworkErrorGetLocalizedDescription + 335348 30 CFNetwork 0x185034 _CFNetworkErrorGetLocalizedDescription + 335760 31 libdispatch.dylib 0x1e68 _dispatch_call_block_and_release + 32 32 libdispatch.dylib 0x3a2c _dispatch_client_callout + 20 33 libdispatch.dylib 0xb124 _dispatch_lane_serial_drain + 668 34 libdispatch.dylib 0xbcb4 _dispatch_lane_invoke + 444 35 libdispatch.dylib 0xcf80 _dispatch_workloop_invoke + 1784 36 libdispatch.dylib 0x16500 _dispatch_workloop_worker_thread + 648 37 libsystem_pthread.dylib 0x10bc _pthread_wqthread + 288 38 libsystem_pthread.dylib 0xe5c start_wqthread + 8

We started noticing that for some users the app is crashing as soon as it opens. They cannot get past the issue unless the app is removed and re-installed. There are several similar, but related crashes that we are seeing and all pointing to CFNetwork. The main ones we are seeing are CFNetwork _CFURLStorageSessionCopyCache, CFNetwork _CFURLStorageSessionCopyIdentifier these are showing on our firebase crashlytics console.We recently updated some of the code within our app to use Async / Await and there are several API calls that are called on the app startup to get necessary data. The only test device we have with the issue has not used the app for some time before we updated and opened it. On this device, it crashes every time the app opens.On other devices, we do seem to get a crash after opening and closing the app repeatedly, which we think might be the same issue but are not 100% sure as we can't debug the issue when it occurs as it is very sporadic and never seems to occur on the simulator and only after reopening the app several times in a row.Configuration: We have seen this occur on different versions of iOS. A few examples of devices are: the iPhone 6s running iOS 14.8.1 and iPhone 12 Pro running iOS iOS 15.3.1.Xcode version 13.3.1 (13E500a)Steps to Reproduce: For the devices that crash every time, it seems the issue only happens on devices already logged in after updating to the latest version of our app v9.1.5 (306).For devices that don't crash on startup every time we have found that we need to open lots of apps in the background and then open and close our app and usually after about 5 times a crash occurs.

Hey everyone, we've experienced strange behavior in the iOS system with a GHP profile and the PAC file evaluation when there's no internet connection. The setup: Router is not connected to the internet Device connects to a Wi-Fi provided by the router Device has mobile data disabled Device has a proxy set via GHP with a PAC file URL Device tries to access a website on a local IP address (e.g. 192.168.1.1) PAC file: function FindProxyForURL(url, host) { if (shExpMatch(url, "*:993/*")){ return 'DIRECT';}if (shExpMatch(url, "*:465/*")){ return 'DIRECT';}if (shExpMatch(url, "*:587/*")){ return 'DIRECT';} if (isPlainHostName(host) || shExpMatch(host, "*.local") || isInNet(dnsResolve(host), "10.0.0.0", "255.0.0.0") || isInNet(dnsResolve(host), "172.16.0.0", "255.240.0.0") || isInNet(dnsResolve(host), "192.168.0.0", "255.255.0.0") || isInNet(dnsResolve(host), "127.0.0.0", "255.255.255.0")) return 'DIRECT'; return 'PROXY my.proxy.address;DIRECT'; } The result: The device is not able to connect to local addresses, the request times out. Based on the PAC file rules, when accessing the 192.168.1.1 address, the proxy should have been bypassed and it should go directly: isInNet(dnsResolve(host), "192.168.0.0", "255.255.0.0"). However, it seems, that the device is still trying to go via proxy which is unreachable since the router is not connected to the internet. The GHP profile has even the flag to bypass proxy if unreachable enabled: <key>ProxyCaptiveLoginAllowed</key> <true/> <key>ProxyPACFallbackAllowed</key> <true/> If we remove the GHP profile from the device, everything works. And if the device has cellular data enabled, it works as well. This setup is used by a customer that is connecting to such router in elevators for some maintenance, so they usually have no signal there - the cellular interface is not working and from time to time, the webpage is successfully loaded - I assume that the device had a signal for a short period of time. I just wanted to check with you if there's anything we do wrong in the proxy setup before reporting a bug. Right now we're trying to reproduce this behavior with CFNetworkDiagnostics and NetworkDiagnostics profiles installed so we have more logs. Although, we've noticed the following message in the logs: CFNetworkAgent PAC Fetch failed with cached error [NSURLErrorDomain:-1009] Have anyone experienced something similar? Thanks in advance!

I want to reset the local network privacy. so I try the method mentioned here ( https://developer.apple.com/forums/thread/663839 ). but it doesn't work on my iPhone 13 mini running iOS 15.4.1. anyone knows why?

As part of a security assessment, we discovered that our app is storing sensitive information in the cache. After some research and considering the recommendations, we decide to use .ephemeral configurations for our URLSessions, so far so good. However, taking a look at the content in the cfurl_cache_receiver_data table, we realized that some of those responses are not part of any of our endpoints, meaning that this is probably coming from requests made for third-party libraries that we use and we were able to confirm this by using a tool to inspect network traffic. My understanding is the cache mechanism is attached to a URLSessionConfiguration and, at the same time, this configuration is tied to a URLSession. Since this is not our code and therefore different URLSessions it makes sense that this caches the responses for any request. Please correct me if this is wrong. I am wondering if there is a way to disable the caching across the app (including requests made for third-party libraries?) or if there is a different/better approach to this? I am attaching a screenshot of the cfurl_cache_receiver_data table content. For example: token=[value]. This is not the response of one of our endpoints, but an external one. Thanks in advance! PD: Is there a way to easily map the data in the cache.db with the particular endpoint/request?

The parameters of the completion handler are (data: Optional<Data>, urlResponse: Optional<Data>, error: Optional<Error>). Here is an exhaustive switch statement of the parameter combinations: switch (data, ulrResponse, error) {       case (.some, .some, .some):       case (.some, .some, .none):       case (.some, .none, .some):       case (.some, .none, .none):       case (.none, .some, .some):       case (.none, .none, .some):       case (.none, .some, .none):       case (.none, .none, .none): } Which combinations of values may be provided and which will not? For example, I think it's fair to say that both (.some, .none, .some) and (.some, .none, .none) are invalid because a response would have to be provided in order to receive data to pass to the closure, and the documentation states: If a response from the server is received, regardless of whether the request completes successfully or fails, the response parameter contains that information.

My app is working fine on all devices except on one specific device iPhone 12 Pro Max, that give error "502 Bad Gateway". App is unable to connect to server, what could be the reason for this, is this related to firewall or VPN? This happens only on a single device of the client but on our local testing devices it works perfectly fine. Please do share your thoughts as this issue seems rather unexpected where the app on all other devices is working fine except for one. Thank. you

I'm trying to create a network request mocking infrastructure for my iOS app. I'm using a mock URLProtocol to do this. My challenge is that I want to load custom data for each URLSession. In my setupWithError() in my unit tests, I basically do:         let config = URLSessionConfiguration.ephemeral         config.protocolClasses = [URLProtocolMock.self]         let session = URLSession(configuration: config)         APIManager.shared.session = session         <session.URLProtocolMock>.loadJSMocks(filename: "AddItemUITest.js") All of the examples I see for doing mocks this way, create static variables in the URLProtocolMock to allow configuring data. I'd like to be able to run tests in parallel, so static variables won't work. I couldn't find an obvious way to get the protocol instance from the URLSession. Is there a non-obvious way? ;-) Thanks! Greg P.S. And in the course of writing this, I realized that I have another problem with static APIManager session sharing. But that one I know how to solve :-)