“iPhone 16 pro”

Thank you for the great description with code and steps and going over the devices. I do not think there is a bug in that iPad as far as I can tell, so may I ask you to do something to verify? Do you get the same results with just the relevant code in a small test project? If so, please share a link to your test project. That'll help us better understand what's going on. If you're not familiar with preparing a test project, take a look at Creating a test project. On your focused sample should be very simple so can be run on iPhone and iPad with the same code where the didSelect(_:conversation:) method doesn't behave as expected when a message is tapped multiple times without a different message being selected in between. Looking forward to see if you found something interesting! Albert Pascual
  Worldwide Developer Relations.

no, you're not alone, and I'm using a Apple M4 Pro w/24GB, 2024!

I attempted to reproduce the bug in UIKit, but it works correctly there. Notice how the Tab Bar and the accessory view change color simultaneously. final class ViewController: UITabBarController { override func viewDidLoad() { super.viewDidLoad() let firstVC = FirstTabVC() firstVC.tabBarItem = UITabBarItem( title: first, image: UIImage(systemName: 1.circle), tag: 0 ) let secondVC = SecondTabVC() secondVC.tabBarItem = UITabBarItem( title: second, image: UIImage(systemName: 2.circle), tag: 1 ) viewControllers = [firstVC, secondVC] setupBottomAccessory() } func setupBottomAccessory() { let titleLabel = UILabel() titleLabel.text = Title let iconView = UIImageView(image: UIImage(systemName: play.fill)) iconView.preferredSymbolConfiguration = .init(pointSize: 20, weight: .semibold) iconView.tintColor = .label iconView.contentMode = .scaleAspectFit let stackView = UIStackView(arrangedSubviews: [titleLabel, iconView]) stackView.translatesAutoresizingMaskIntoConstraints = false let accessoryView = UIView() accessoryVi

The Developer website is misleading here, at least AFAICT. When you go to create a certificate, the In-House and Ad Hoc option says: Sign your iOS app for In-House or for Ad Hoc distribution. [All emphasis in these quotes is mine.] However, that certificate isn’t limited to iOS. For example: If you create tvOS In House provisioning profile, it will let you select the iOS Distribution certificate. I believe [1] that other platforms, like visionOS, are covered by the In House provisioning profile, despite the fact that the website says: To sign iOS apps for In House Distribution, you need a Certificate. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] It’s actually hard for me to test this right now, so my conclusion is based on an analogy. If I created an Ad Hoc profile, it lets me select the iOS Distribution certificate but it also then lets me select non-iOS devices, like an Apple Vision Pro. So if things work this way for Ad Ho

I have a small external app that puts up a modal dlog on receipt of the openDocuments event. I created a fake job in the big app that sends all the events, and had it send an kAEOpenDocuments to the small app, using kAEWaitReply so it will just sit there until the small app dismisses the modal dlog. I then ran a normal job that hammers InDesign with thousands of scripts. I got this in the Xcode log of the big app: AddInstanceForFactory: No factory registered for id F8BB1C28-BAE8-11D6-9C31-00039315CD46 A few minutes later the big job got stuck and I noticed two of these in the Xcode log: Received XPC error Connection interrupted for message type 1 kCFNetworkAgentXPCMessageTypePACQuery The big job's thread at this point: ProofProcessor - FAKE1 Queue : Job Queue (QOS: USER_INITIATED) (concurrent) #0 0x00000001948e1c34 in mach_msg2_trap () #1 0x00000001948f43a0 in mach_msg2_internal () #2 0x00000001948ea764 in mach_msg_overwrite () #3 0x00000001948e1fa8 in mach_msg () #4 0x0000000194a0ec0c in __CFRunLoopServiceM

Hello. I tested using Xcode Version 26.2 (17C52) on macOS 26.2 (25C56) using your code with the following color format files and I was unable to reproduce a crash. Can you provide a copy of the image file you are using for testing? Formats I tried: RGB_NoneSkipFirst_8bit 8 bits/component, 32 bits/pixel RGBX format (no alpha, skip first byte) sRGB color space AlphaInfo: kCGImageAlphaNoneSkipFirst RGB_NoneSkipLast_8bit 8 bits/component, 32 bits/pixel XRGB format (no alpha, skip last byte) sRGB color space AlphaInfo: kCGImageAlphaNoneSkipLast RGB_AlphaPremultFirst_8bit 8 bits/component, 32 bits/pixel ARGB format with premultiplied alpha sRGB color space AlphaInfo: kCGImageAlphaPremultipliedFirst RGB_AlphaPremultLast_8bit 8 bits/component, 32 bits/pixel RGBA format with premultiplied alpha sRGB color space AlphaInfo: kCGImageAlphaPremultipliedLast RGB_AlphaPremultLast_16bit 16 bits/component, 64 bits/pixel RGBA format with premultiplied alpha sRGB color space AlphaInfo: kCGImageAlphaPremultipliedLast RGB

I don't think this answer actually holds up. Here is how I understand it: I plug in a monitor. Its default resolution is 4K at 240Hz. Fine, I shouldn't be able to plug in another monitor. I change the one monitor to 4K at 120Hz. Now the laptop has one monitor plugged in, running at 4K at 120Hz. I plug in another monitor. Its default resolution is 4K at 240Hz. I understand this is a problem because it would require both of the two display 'pipes' as you described above. That's close, except the problem here is actually at #2, as changing resolution did NOT release the pipe. The issue here is that these pipes are actually tied to the low-level I/O system, not the monitor itself. Putting that in more concrete terms, driving the monitor at 4K/240Hz requires more video bandwidth than a standard cable should provide, so the system plugged in two cables instead. The change at #2 had no effect on that configuration. And, yes, I used refresh rate to describe what was going on above and, no, that wasn't entirely accura

or the SB/AE world that fails So, in the process of writing up the message that follows this one, I actually had a breakthrough about what might be involved in triggering this crash. That is, I don't think it's necessarily CAUSING the crash, but I think it is part of the situation that creates the crash. Here is the crashing thread on all three crashes you sent: 0 com.apple.AE 0x1a7d970cc isMachReplyOutstanding(short) + 92 1 com.apple.AE 0x1a7d89b80 absolveReturnID(short) + 92 2 com.apple.AE 0x1a7d8994c AEEventImpl::AEEventImpl(unsigned int, unsigned int, AEDesc const*, short, int) + 100 3 com.apple.AE 0x1a7d85bfc AECreateAppleEvent + 416 What absolveReturnID actually does is generate the random 16-bit ID used when using kAutoGenerateReturnID, which is then checked as unused by calling isMachReplyOutstanding. However, the interesting detail here is that absolveReturnID also has a fixed cache of the last (~64) IDs, so it can just skip those IDs instead of checking for their use. Under normal circumsta