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

Hi, Sorry to hear you are occasionally having problems with foundation models and previews working. The best next step will be to file a feedback with diagnostics the next time you hit this so we can take a look. Install the logging profile using instructions available here: https://developer.apple.com/bug-reporting/profiles-and-logs/?name=swift On your mac running Xcode, and on your physical preview device (if you are using one). Install the logging profile using the following instructions on your mac running Xcode; and if you are using one, your physical preview device (iOS or visionOS): https://developer.apple.com/bug-reporting/profiles-and-logs/?name=swift Then when you reproduce the problem in Xcode: Either (a) an error banner will appear, click the Diagnostics button in that banner; or (b) if you're not seeing an error but you still want to provide diagnostics you can get the same diagnostics window by going under the Editor menu in the menu bar, then selecting the Canvas submenu, then selectin

[quote='875266022, TheBeeApplications, /thread/812429?answerId=875266022#875266022, /profile/TheBeeApplications'] is it acceptable that I use my own glass system instead …? [/quote] I don’t think you’ll get a detailed answer to that. When folks ask questions about what is or isn’t acceptable, I can only really point them at the challenge rules, and specifically: Developer > Swift Student Challenge > Eligibility and requirements Developer > Swift Student Challenge > Terms and Conditions [quote='875266022, TheBeeApplications, /thread/812429?answerId=875266022#875266022, /profile/TheBeeApplications'] Also, I am not able to make portrait mode be locked when tested on iPad, is there any method to lock it in SP? [/quote] I recommend that you start a new thread with that specific question. Put it in the UI Frameworks subtopic that’s most appropriate for the UI framework you’re using, and tag it with Swift Student Challenge. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Sup

There is however a problem with this solution. If there is a TextField in the popover, typing in makes it firstResponder ; and the parent window controller do not receive mouseEnter events that triggers the tooltips. Which means I do not need to simulate mouseDown but just makeFirstResponder. So at the end, the question boils down to: how to manage the conflict between popover and its parent window about FirstResponder. Is it possible to have first and second responder, I mean forwarding the mouse messages to the parent ? Considering that The shared NSApplication object performs the important task of receiving events from the window server and distributing them to the proper NSResponder objects. NSApp translates an event into an NSEvent object, then forwards the event object to the affected NSWindow object. All keyboard and mouse events go directly to the NSWindow object associated with the event. … When a window object receives an NSEvent object from NSApp, it distributes it to the objects in its vi

I can confirm there is something crashing my Apps that only have Launchscreen storyboards. I use Autoresizing and not Autolayout. And guys please, make a real effort to build a Launchscreen component in SwiftUI. It makes no sense in 2026, always ten years after and we still have a storyboard file messing/crashing our Apps in Swift.

PS: According to the AlarmKit FAQ (https://developer.apple.com/forums/thread/797158) the stop intent should work also when the user is swiping or pressing the power button, but it seems it doesn't. So this is an issue and is reproducible in iOS 26.2.1.

@DTS Engineer Ideally, I would love to build an SDK for iOS apps. I do intend to support macOS apps too and I guess that'd be fairly straightforward but I want to figure out some way to support iOS apps too. Is there anything at all that could help with this case?

What platform is this on? Specifically, macOS offers a bunch of interesting IPC options but most of those are not supported on iOS and its child platforms. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

What Albert said plus… Some managed capabilities are granted to a specific App ID, while others are granted to your team as a whole. My experience is that the Multicast Networking capability is always granted to your team, so you can use it in any app from that team. And, presuming that you’re working in Team ID H________3, our records show no sign of it deviating from this standard practice. [quote='814969021, idrachman, /thread/814969, /profile/idrachman'] now multicast entitlement is no longer provisioned. [/quote] What do you mean by that? Is Xcode failing to build your app? Or are is your app failing to send or receive multicasts? If it’s the later, be aware that the vast majority of such problems are not tied to the Multicast Networking capability, but rather are caused by code-level problems. I have a bunch of advice about that in Extra-ordinary Networking > Broadcasts and Multicasts, Hints and Tips. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = e

You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for in-depth analysis and may take longer to complete. As you notarise your apps, the system will learn how to recognise them, and you should see fewer delays. For lots of additional info about notarisation, see Notarisation Resources. Specifically, it links to a Q&A with the notary service team that’s quite instructive. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for in-depth analysis and may take longer to complete. As you notarise your apps, the system will learn how to recognise them, and you should see fewer delays. For lots of additional info about notarisation, see Notarisation Resources. Specifically, it links to a Q&A with the notary service team that’s quite instructive. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for in-depth analysis and may take longer to complete. As you notarise your apps, the system will learn how to recognise them, and you should see fewer delays. For lots of additional info about notarisation, see Notarisation Resources. Specifically, it links to a Q&A with the notary service team that’s quite instructive. [quote='814937021, JimWu01, /thread/814937, /profile/JimWu01'] 1- … but 16+ hours with zero feedback seems excessive. [/quote] My experience, based on reports I’ve seen here in the forums, is that when you hit the in-depth analysis path it can take a day or two to clear. I generally don’t bother investigating issues like this until a week has passed. [quote='814937021, JimWu01, /thread/814937, /profile/JimWu01'] 2- Is there any manual configuration Apple needs to do on their end to unblock my team for notarization? [/quote] No, that’s a different issue. [quote='814937021, JimWu01, /thr