Hi,I'm using a NSURLSession with the backgroundSessionConfiguration to send a NSURLSessionUploadTask in the background.I noticed that sometimes after waking by the OS in the app delegate's handleEventsForBackgroundURLSession, I get a call on the NSURLSessionDataDelegate for URLSession:dataTask:didReceiveData *directly before* URLSession:task:didCompleteWithError. They seem to be called by two different threads in the same time. Naturally, processing the didComplete before getting the data in didReceive results in bugs. Is this the normal behavior for background tasks and I should support these parallel out of order calls to the delegate for the same task, or is it a bug and just open a rdar?Thanks

Since iOS 16 it is possible to use content filter on managed apps instead of supervised devices using the new ContentFilterUUID attribute. I built a simple test project for this and found that even when targeting browser apps, no flow in the data filter is NEFilterBrowserFlow and thus can be remediated with a blocking page. All received flows are socket flows. When changing the configuration via NEFilterManager to filterSockets=false and filterBrowsers=true nothing passes through the content filter. Is this by design? is there no way to show blocking pages using per app content filter?