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

Thank you for providing the code and screenshots. Additionally, I would like to inquire about your filed bug report, instead of submitting two Swift files, would it be possible to upload a focused and simple project to the bug report that demonstrates 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. Also you can share a link for that project in the forums so developers can see the issue and provide workarounds. Albert Pascual
  Worldwide Developer Relations.

Hi @MichaelOShea, I've reviewed this thread and your logs. There are two aspects I want to mention: We suggest using the on-device model for simple tasks with a small context window. You can find a list of capabilities (and what to avoid) under Understand model capabilities. If you can pair down your instructions and prompt to a very basic single task that can be described in a sentence or two, then that may be a good candidate for Foundation Models. For large tasks, especially those with multiple steps to process complex information or more than a few paragraphs, it may be better to utilize a server-side frontier model. The system prompt you linked to likely falls into this category. Depending on how your adapter was trained, it may not be tuned for the on-device environment, which is further contributing to why it exceeds the context window. If this is the case then we suggest using the standard SystemLanguageModel and implementing your custom functionality via instructions and prompting instead. W

Having the same issue. Removed some testers and not getting 422 error. I can't even test builds of my own app on my own hardware anymore.

Sorry for the delay in responding to this. Here are a few bug reports that have gotten no attention. All are macOS 26 bugs (the one with iPhone in the title affects macOS and iOS). I have just now gone through to confirm that each are happening consistently on 26.3. Many have been around since 26.0. Several say Recent Similar Reports: More than 10. The last one is a feature suggestion. Thank you for looking into these, especially the first two. FB20794466 -- Item Numbers shown when Overlay is set to None FB21356190 -- Orange microphone appears in menu bar at all times FB20933185 -- Siri voices break System voice UI FB20934473 -- No option to disable Type to Siri ... Siri window does not go away FB20785769 -- Speak announcements only works with Samantha voice FB20813399 -- Keyboard Shortcuts' Restore Defaults button should read Restore Default FB20875408 -- Reverse sort order only available in list view FB20875564 -- Record Selection Menu Bar Icon does not return to default state after Esc is pressed

I was able to get things syncing reliably between Macs today running internal TestFlight builds after adding CloudKit.Framework to the app target's Frameworks, Libraries, and Embedded Content section as described in this thread.. Once that was set, creating/editing a Project record would sync between the TestFlight apps. I then noticed that creating/editing a related TimeEntry record would cause syncing to completely stop in either direction. I then discovered that only my Project records type had been deployed to Development on the iCloud Console; while TimeEntry had not been deployed for some reason. I re-deployed schema changes from development to production on iCloud Console, and now Project and TimeEntry record types show in iCloud Console in production. Syncing now works for creating/editing/deleting Project and TimeEntry records. So all is syncing well in my Internal TestFlight builds now. Thank you, Ziqiao, for the links. I'm sure those would be helpful if

This is expected on iOS 26. There is no supported means to access the views that represent the toolbar on iOS 26.

Thanks for this very interesting. I would check about the multiple returns the error is complaining about: NSMultipleUnderlyingErrorsKey=(n) I have 2 recommendations, first can you read this thread: https://developer.apple.com/forums/thread/815397?page=1#875810022 Second, I would like you to try to run this on the simulator to see if makes any difference. On the terminal: xcrun simctl status_bar clear I am sure you already went through the clearing and build and restarting the simulator. Open the Console app on your Mac and filter logs for your simulator. Look for any additional error messages or warnings that might provide more context about what's going wrong and post it here. Occasionally, beta versions of macOS and iOS/iPadOS simulators may contain bugs that have been fixed in later beta releases. So please provide me all the versions you are using. As a last resort, consider reinstalling Xcode and the simulators to ensure there aren’t any cor

In the submission form, it asks you to whether you want your project to run through Xcode(which will be run in simulator) or Swift Playground app which on a real device. Pick the second one, and it's done. Of course, if you are currently developing on Xcode, make sure it runs and works as expected in Swift Playground before submitting.