Just an update in case it helps anybody.... A function was called unexpectedly twice in quick succession leading to the NSSString being de-allocated before NSURL got to use it. I put some defensive code in and it seems to have fixed it

Yes.... it was confirmed to me that the 60 sec behaviour is by design. I would suggest you file an enhancement request with them if you believe as I do that this is too short. For PABX behaviour calls can ring for longer than that in busy situations. Also as far as I know the callback we get from Callkit doesnt allow me to distinguish between a caller rejecting the call rather than this 60 sectimeout. In that case it looks to our call records that the user rejected the call rather than it being a missed call :-(

I'm also having same issues with QuickLookPreviewController. I too have been ignoring these warnings. However I now have a particular Testflight user having problems with playing Videos in the QuickLookPreviewController so I believe this is because of the constraints It is a very useful ViewController if it could work properly:-) Here is my Debug... 2024-11-20 20:42:38.128950+0000 My App[82215:2024054] [LayoutConstraints] Unable to simultaneously satisfy constraints. Probably at least one of the constraints in the following list is one you don't want. Try this: (1) look at each constraint and try to figure out which you don't expect; (2) find the code that added the unwanted constraint or constraints and fix it. (Note: If you're seeing NSAutoresizingMaskLayoutConstraints that you don't understand, refer to the documentation for the UIView property translatesAutoresizingMaskIntoConstraints) ( "<NSAutoresizingMaskLayoutConstraint:0x6000021ca620 h=-&- v=--& UINavigationBar:0x11afbadc0.minY == 0 (active, names: '|':UILayoutContainerView:0x11afcf730 )>", "<NSAutoresizingMaskLayoutConstraint:0x6000021ca6c0 h=-&- v=--& UINavigationBar:0x11afbadc0.height == 44 (active)>", "<NSLayoutConstraint:0x6000021d23f0 V:[UINavigationBar:0x11afbadc0]-(0)-[UIFocusContainerGuide:0x600003d283c0'UINavigationControllerContentFocusContainerGuide'] (active)>", "<NSLayoutConstraint:0x6000021d24e0 UIFocusContainerGuide:0x600003d283c0'UINavigationControllerContentFocusContainerGuide'.bottom == UILayoutContainerView:0x11afcf730.bottom (active)>", "<NSLayoutConstraint:0x6000021d2bc0 V:|-(0)-[UILayoutContainerView:0x11afcf730] (active, names: QLPreviewControllerView:0x119c86e70, '|':QLPreviewControllerView:0x119c86e70 )>", "<NSLayoutConstraint:0x6000021d2c10 V:[UILayoutContainerView:0x11afcf730]-(0)-| (active, names: QLPreviewControllerView:0x119c86e70, '|':QLPreviewControllerView:0x119c86e70 )>", "<NSLayoutConstraint:0x6000021ca760 'UIView-Encapsulated-Layout-Height' QLPreviewControllerView.height == 0 (active, names: QLPreviewControllerView:0x119c86e70 )>"

Further to this in case it helps anybody. When I build my Code with Xcode 16.0 then this problem does not happen. It had been using Xcode 15.2 The only devices that we had seen with the problem had been running iOS18.0 or iOS18..0.1 . Even iOS18.1 had been OK.

Thanks Kevin... This original post is from 8 years ago. I just tested it again now and there is in fact an alert tone given. So it must have been fixed sometime in teh last 8 years. Happy days!