LLDB crash

Ok, I tested it now but the small app I added to my Feedback is still crashing. Currently on another area, but it is even no longer starting. I updated my Feedback with the requested information

Related to termination, my advice is to NEVER terminate your app. In the past, some of our Apps had a Decline button on the Terms of Service (ToS) screen that terminated the app, but App Review flagged that behavior as a Crash and blocked our app submission. Now our ToS screens only have an Accept button and the user can press that or they can close the app themselves; this always gets through App Review. For Age Verification, we have implemented similar: If an eligible user Declines to share their Age Range or is a minor without parental consent, they see a screen explaining that they are blocked with a link to App Store documents about the law and settings. There is no way out of that screen other than closing the app.

Same piece of code works in iOS 26.1 and earlier even a simple print crashes due to object no longer being available

This happens only in iOS 26.2 prior versions working fine . I’m listening for updates from sampleHandler triggered from web view. The object reference is released when the didReceive message is triggered self.webkit.configuration.userContentController.add(self, name: sampleHandler) self.webkit.load(request) func userContentController(_ userContentController: WKUserContentController, didReceive message: WKScriptMessage) { print(message.name) // works print(message.body) // crashes }

Apologies for the delayed update. Yesterday, we completed the rollout of your workaround solution, and our metrics indicate its effectiveness. The issue count has decreased significantly during the implementation, dropping from 6000 per day to 1000 per day as of today. Fabulous, that's great to hear and thank you for sharing concrete numbers. I was fairly confident it would work, but it's good to get independent confirmation. We would like to express our gratitude for the workaround solution you provided. You're very welcome. Currently, we have implemented the workaround only for incoming calls, as these were the primary source of issues observed in our app. We plan to extend the implementation to outbound calls as well. I don't know this for certain, but my guess is that the difference between the incoming/outgoing rate is mostly due to usage patterns and the details of your existing implementation. In particular, these two factors: I suspect most calls originate from the foreground (the user opening your ap

We update OS to 26.2 this week, and the M4 max crashed issue has been gone. May we know if there is any fixed solution phased into the new OS version? There isn't really any way to answer that with the information you've provided. There are too many changes in any given release to easily review, and it's often the case that the change that resolves a given issue wasn't actually specific to that particular issue. If you upload the panic log to a bug and post the bug number back here, I might be able to say more, but without that, I can't really determine anything. __ Kevin Elliott DTS Engineer, CoreOS/Hardware

I tried to disable swift-tasks-plugin-enabled as you described, but that barely had noticeable effect (<1s difference). With the debugger attached (and iPhone connected with USB) our app becomes responsive after about 6-7 seconds from start, while this time decreases to less than 1s if I turn off Debug executable option in scheme. I collected lldb-rpc-server sample as you described and added it to FB21378487. Hope it would be helpful!

We update OS to 26.2 this week and the M4 max crashed issue has been gone. May we know is there any fixed solution phoased in to the new OS version ? Many thanks for your supporting. cheers, carrie

Hello Justin, As you suggested, I have repeated the tests multiple times, but I was not able to reproduce the crash. As mentioned, it appears to be difficult to encounter the issue consistently. I would also like to share an additional observation: we ran the same application on iPads with iPadOS 18.1 for nearly six months without encountering any crashes. However, after updating the devices to iPadOS 18.6.2, the crashes started occurring. Since the only change during this period was the iPadOS update from 18.1 to 18.6.2, I would appreciate your insight on whether any changes in this OS update could potentially contribute to this behavior?