Building for iOS Simulator, but the linked and embedded framework ‘XX.framework‘ was built for

@Engineer I am running into this same Springboard crash when posting a Critical Alert notification in the iOS 26 Simulator. @mnydigital Did you ever get a resolution, or even a workaround, to this issue?

Thanks so much for the post. Can you produce an image so we understand exactly what you see? You can upload the picture here. Are you reproducing it with the simulator? Can you also produce a simple focused project that reproduces the issue? 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. Thanks, Albert Pascual
  Worldwide Developer Relations.

I am experiencing a similar issues the past 72 hours. All builds that were being internally tested marked expired Can upload builds, but Internal testing users get an error when trying to download new builds. Can't upload a fresh app to External Testing Beta Review

@DTS Engineer Thanks a lot for the detailed explanation — that makes sense. It seems that when migrating directly from ObservableObject to @Observable, extra care is needed around update ordering and intermediate states. In my case, this behavior leads to unexpected UI results, such as the scroll position ending up in an incorrect state (as shown in the screenshot above). I can consistently reproduce this on a real iPad Pro (M4) running iOS 26.2.1, where the UI visually jumps and then settles at an unintended position. I’ll need to adjust my approach to work around this behavior. I’d also be very interested to hear more from the SwiftUI team on the intended patterns or best practices for avoiding these intermediate states in UI code.

I've just run into this issue and I can confirm that the memory leak does not occur on iPhone (iOS 18.7.1 and iOS 26) even when using UITabs occurs on iPad (iOS 18.7.1) only when using UITabs. It does not occur when setting the tab bar controller children the old way (setViewControllers(:animated:)). A work around is to use a custom TabBarController inheriting from UITabBarController and override viewDidDisappear(:) as follows: override func viewDidDisappear(_ animated: Bool) { super.viewDidDisappear(animated) // HACK: clear the tabs property to prevent memory leaks when using UITabs if #available(iOS 18, *) { setTabs([], animated: false) } } It effectively triggers the children view controllers deinit. App build with Xcode 26.2 on macOS 26.2.

Oh thanks! That might work. I had only tried Xcode 16. I need to be able to work on the project at home and in the college lab. My current home projects won't build in college. There will also be an issue with grading of assignments. I'll try Xcode 16.4. Will that work in college I wonder? They have Xcode 16? I'll try anyway. Thanks so much for you reply!

Hi Quinn, I followed your steps and the profile dump is as below. It has com.apple.developer.payment-pass-provisioning => 1 : { AppIDName => XC com s_ _ _ _ _ _ d ApplicationIdentifierPrefix => [ 0 => 2 _ _ _ _ _ _ 7 ] CreationDate => 2026-02-05 15:09:44 +0000 DER-Encoded-Profile => {length = 3857, bytes = 0x30820f0d 06092a86 4886f70d 010702a0 ... 73b0c49b eb3ffec9 } DeveloperCertificates => [ 0 => {length = 1487, bytes = 0x308205cb 308204b3 a0030201 02021007 ... b474d99f 14730350 } ] Entitlements => { application-identifier => 2 _ _ _ _ _ _ 7.com.s _ _ _ _ _ _ d aps-environment => production beta-reports-active => 1 com.apple.developer.associated-domains => com.apple.developer.in-app-payments => [ 0 => merchant.com.s_ _ _ _ _ _ d ] com.apple.developer.networking.slicing.appcategory => [ 0 => communication-9000 1 => games-6014 2 => streaming-9001 ] com.apple.developer.networking.slicing.trafficcategory => [ 0 => defaultslice-1 1 => video-2 2 =

Thank you, Albert. I have already filed this issue as FB21797091 at the beginning of this thread. I have now added additional diagnostic information to that existing report, including: Detailed swcutil_show.txt comparison between IDN and ASCII domains Entitlement configurations tested over 3 years Testing timeline across iOS 16, 17, and 18 Please reference FB21797091 for the complete bug report. Thank you for your assistance in escalating this issue.

It looks like the underlying issue is still not resolved, and the only workaround is to give things enough time to complete. My suggestion would be to: build+run your app targeting the iOS simulator. This will launch the simulator app and start booting the simulator wait until the simulator finishes launching and your application is now running in it. Please note, the bug is that step 2 takes longer than it should so this is where you'll need to exercise patience. Once that successfully completes you can then quit the simulator, and then try the preview again. This time we'd expect things to work in the preview canvas since the simulator runtime has been primed.

Thanks for those answers. The ultimate consumer of the matchDomainsNoSearch property is actually in Darwin, so you can see how the code works. Start here. As you can see, the behaviour is pretty straightforward: If that property is set, it skips the code that adds the match domains to the search domains. However, it’s still not obvious why this is affecting your setup. One possibility relates to the example you included in your original post, where you have test.com in both the search domains and the match domains. In that case setting matchDomainsNoSearch causes it to add the match domains to the search domains, as shown by the code referenced above, and that code can change the order of items in the search domains. However, without knowing exactly how this is set up, it’s hard to tell whether that’s relevant here. I realise that you’re testing this on iOS, but do you also have the ability to test on macOS as well? If so, you could take advantage of macOS’s additional debugging features to learn mor