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

Hey @DTS Engineer thanks for your reply. I am using the release version, no Beta. Xcode Version 26.2 (17C52) Simulator iPhone 13 mini, iOS 18.5 Version 26.0 (1062.1) SimulatorKit 954.5 CoreSimulator 1051.17.7

Hi @SuyashBel, To run Foundation Models in Simulator, ensure that macOS is up to date. Utilizing Foundation Models framework in the Simulator requires macOS Tahoe, with Apple Intelligence enabled on the Mac. (System Settings -> Apple Intelligence) This will trigger a download of the model, which can also take a little time. Additionally, make sure the simulator is running 26 or later. It can also be helpful to ensure you're using the latest version of Xcode. If everything is updated and you're still having trouble, try restarting your Mac. If all that still fails, let us know and also please file Feedback so we can track this issue. Best, -J

Thanks for your post. Please check this post about this issue here: https://developer.apple.com/forums/thread/807280 Last Update? beta or release? Can you provide the version of Xcode and Simulator? What's that simulator iOS version? Albert Pascual
  Worldwide Developer Relations.

Thanks for the post, I have only questions for you to narrow down and make sure I understand the platform not working. Can you provide me the version of Xcode and what simulator are you using to ensure that the simulator you're using is compatible with the Foundation Model framework. Since your M1 Air and iPad Pro M5 are both Apple silicon devices, the simulator should generally support the latest frameworks. Make sure you have the latest version of Xcode installed. Update the simulator images to the latest version available. If possible, try running your app on a different simulator that you know works well with your app. You can choose from a list of simulators available in Xcode. Can you provide me that? Can you provide me exactly the error you are getting in the simulator. Look at the error logs in Xcode for more specific information about what might be causing the issue. This can help in diagnosing the problem more accuratel

Dear s_petrovskiy2, Just for clarification, can you please answer: By mirroring, you mean that the external device would be displaying identical content to what is on your iPhone, correct? Are you using storyboards, and defining your scenes in your Info.plist? If so, then you would not need to handle scene:willConnectToSession:options: for the default configuration of your root view controller main device screen. (If you are loading it programmatically, you would need to, as seen in Tech Note TN3187: Migrating to the UIKit scene-based life cycle; but since your window has already been created, it sounds like you are using the Info.plist method. In which UIWindowSceneDelegate delegate method are you seeing a second scene created? When does it take place during your app's operation? After connecting to the AirPlay receiver (your MacBook)? How are you initiating an AirPlay connection with your app- are you using the built-in Screen Mirroring button in iOS? Please let me know, Richard Yeh  Deve

The updated profile is now live and can be downloaded from this link (found inside the Apple Matter OTA - User Guide). __ Kevin Elliott DTS Engineer, CoreOS/Hardware

@flerbs thanks for mentioning that. I checked and I can see you added mention of the WebKit link you mentioned to your bug report. I don't see any other activity in that as of yet. Please continue updating your bug report as you test in future system software updates.

Is this expected AirPrint behavior for image jobs, or could this be a bug in how iOS constructs the IPP request for photos? Based on your description, it sounds like a bug. Have you filed a bug and, if so, what's the bug number? __ Kevin Elliott DTS Engineer, CoreOS/Hardware

I am going to suggest that your issue is more structural than a Bluetooth connection problem if even print(App initializing) is not printing. Once you get that working (perhaps start with a clean Hello world! project to make sure your code is running. And then you can add the Bluetooth functionality to it using examples. Unfortunately our sample projects are a bit dated, and outside the watchOS sample Interacting with Bluetooth peripherals during background app refresh, we don't have any SwiftUI examples that demonstrate CoreBluetooth. Currently, the CoreBluetooth framework is not fully compatible with SwiftUI, and requires the use of @UIApplicationDelegateAdaptor var delegate: ApplicationDelegate and handle your CoreBluetooth logic in a UIKit class. In the above example, you will find an iOS target BARBluetooth, which will show how the SwiftUI/UIKit integration is handled. (do not consider the code there as a full example though, as that is a specific app that only accompanies the watchOS a

Thanks for your post, I do not know of any issues with UserDefaults in iOS 26, so this is interesting, I would like to learn a little bit more how you use this I'm sorry to hear about the persistent issue you're facing with data loss in your app on iOS 26. Ensure your app and the iOS device are running the latest system updates. Verify that your app has the necessary background modes enabled, such as Background fetch or Background location updates. These modes can help ensure your app can read and write data even when not actively running. However going to the background will not lose any data. Ensure that your app is not inadvertently clearing data in a location that's causing issues. Conduct extensive testing on real devices across different configurations and environments to see if the issue is device-specific or platform-specific. Not in the simulator. My recommendation is to create a simple focus project that you can show the issue that I can run on a device. Implement

Thanks for the post, this is very interesting, can you provide a little more context about how Xcode marks the string as stale? Screenshots or a way to reproduce it quickly? This is the key you ad adding into your Info.plist? https://developer.apple.com/documentation/BundleResources/Information-Property-List/NSAlarmKitUsageDescription Ensure there are no hidden characters or encoding issues in your InfoPlist.xcstrings file that might confuse Xcode. What happens when you keep it only in the Info.plist? 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. Thanks, Albert Pascual
  Worldwide Developer Relations.