Have been using WKWebView: "loadFileURL:(NSURL *)URL allowingReadAccessToURL:(NSURL *)readAccessURL" to load local html file which loads some text and image files. With the directory that html and images files reside in assigned to "allowingReadAccessToURL", it works fine in iOS 13.X. But this broke in iOS 14 Beta, got "domain = NSURLErrorDomain, code = -1100" which is "NSURLErrorFileDoesNotExist = -1100", so guess NOT being able to access to that local file even though I specify the directory to "allowingReadAccessToURL". Anyone has the same issue in iOS 14 beta?

When clicking some navigation link, "decidePolicyForNavigationAction:" will return (WKNavigationAction *)navigationAction to determine URL request and other info, etc. I want to know the x, y position of the clicking on the WKWebView. I print out "navigationAction.description" below, there seem to be some position info? How do I get that "position" info? Or better, can navigationAction to have this position property I can retrieve? Vincent <WKNavigationAction: 0x7faef025b870; navigationType = 0; syntheticClickType = 1; position x = 412.00 y = 187.00 request = <NSMutableURLRequest: 0x600001d66070> { URL: $dG2192 }; sourceFrame = <WKFrameInfo: 0x7faef02b4a70; webView = 0x7faef0824c00; isMainFrame = YES; request = <NSMutableURLRequest: 0x600001d0cbf0> { URL: about:blank }>; targetFrame = <WKFrameInfo: 0x7faef02b4a70; webView = 0x7faef0824c00; isMainFrame = YES; request = <NSMutableURLRequest: 0x600001d0cbf0> { URL: about:blank }>>

Hi, I have an app distributed to TestFlight beta testers. They reported from time to time when the app running in the background by launching another app for a while, suddenly TestFlight crash report dialog comes up, this happens most often on iPhone. I don't have any tasks processing/running in the background from my app. So I'm wondering TestFlight reports this kind of crash due to iOS removing apps running in the background to clean up system memory management? Is this like the situation - sometimes, when app just goes to background for a while and then launch again, the app will launch like never run before. But somehow, with TestFlight, it'll treat this like crash? Here is the crash log (see screenshot below) which doesn't help much to identify what causes the crash . Thanks for any feedback.

I have one user with some issue running my app in iPadOS 1.6 which uses "Move to Display" to connect to external monitor. Since I don't have M1/M2 iPad to be able to test the above scenario. I did see simulator does have External Displays under I/O menu, but even I check the "1920x1080" option to enable this external display", all I can see is just pop up a titled External Display" with black background and no "Move to Display" option when I click "..." on iPad 12.9" 6th gen. running 16.2. I'm wondering if anyone has found out how to simulate "Move to Display"? Thanks!