I found that on iPhone 15 and later models, after upgrading to iOS 16.2, if a WKWebView's HTML page frequently receives large WebSocket data packets, it may trigger a rare bug: the already loaded WebView page can no longer establish network connections. Both HTTPS and WebSocket connections time out, and the network in the entire app becomes unusable. Even creating a new WebView instance to load a new page fails—it stays blank. Reloading a previously loaded WebView also results in a blank screen. (call [webview reload])Currently, the only solution when this happens is to restart the app. Reproduction environment: iPhone 15 and later models, iOS 26.2, cellular data (not reproducible on Wi-Fi) Log situation: When the blank screen occurs, the webViewWebContentProcessDidTerminate callback is not triggered. When creating a new webview instance and reloading a page during reproduction, only the didStartProvisionalNavigation callback is triggered, and no failure callbacks in Navigation are triggered.

in ios16.1beta5 meet a crash, the error message is [ViewController _shouldInteractivePopGestureBeEnabled]: unrecognized selector sent instance xxxx, ViewController is UIViewController subclass, it's there anyone knows which feature cause this error ???? It's ok in the iOS 16.0.2（latest release）, if it's cannot be fix before 16.1 release, my app user can't use the app

xcode14.2 archive for apple connect but stuck on "processing symbols for xxx.framwork" but archive for adhoc is ok! it's framework problem or Xcode problem? I tried archive old xcarchive I has upload to apple store but it's stuck on "processing symbols for xxx.framwork" again

In iOS 26.4 beta, I noticed that when loading pages using WKWebView and using WebSocket to establish IP type addresses, the connection duration was several seconds and sometimes even failed to connect (normally, the connection duration should be in milliseconds). However, when establishing WebSocket connections using domain names, the connections were normal. Additionally, I discovered a special scenario: When directly establishing WebSocket connections using IP type addresses, it remained in the "connect" state. At the same time, based on Wireshark packet capture, it was found that no TCP connection was sent at this time. However, if two connections with the same address were established simultaneously, those two connections could successfully connect. This bug has seriously affected the use of my application service. Is there a chance that this version will solve the problem?