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

@DTS Engineer For my loadHTMLString issue I did report via Feedback Assistant with a minimal test case to reproduce the problem (case: FB21630407). @jfahrenkrug I haven't found a solution or a workaround. It's oddly an issue only on macOS 26.2, not on iOS/iPadOS 26.2 or 26.2.1.

@sergey_nikitin we noticed a huge issue: the events started to fire (reach the threshold) in the DeviceActivityMonitorExtension prematurely, almost immediately after scheduling. This is a known issue in iOS 26, which is actively investigated. I encourage you to file a Feedback report of your own using Feedback Assistant, then post the Feedback ID here. By filing a bug report, you’ll be able to track the issue, update Apple Engineering with additional information, learn if the issue is already known, and get notified of problem resolution.

I am just tired waiting, I have created tool https://www.gotoapplemaps.com tool that helps users migrate Google Maps saved places into Apple Maps Guides. Would love to connect and share what I’ve built, in case it’s relevant to your work Input: https://maps.apple.com/guides?user=CgZOb3J3YXkSDQiuTRC%2Ftp738KjgnkgSDQiuTRDTvNu52eDB8yASDQiuTRCsttyBoo2Y9ksSDQiuTRDs8sbj4ti70DcSDgiuTRDK3uiNlO2%2F8aYBEg0Irk0Q1ZXczsXCt4cV Step-by-step: Extract query param user=. Percent-decode %2F -> /. Base64-decode into 99 bytes. Protobuf parse yields: Field 1 (string): Norway Field 2 (repeated submessage): 6 entries For this sample, each Field 2 entry is a tiny submessage containing exactly two varints: Entry message Field 1 (varint): constant 9902 across all entries Entry message Field 2 (varint): a 64-bit identifier-like value (varies per entry) Example Field 2 entries decoded from this sample (showing entry submessage fields): entry 1: {1: 9902, 2: 5205458886502882111} entry 2: {1: 9902, 2: 2370871449427041875} entry

Thanks for the post. When you said you were granted an entitlement for your bundleID? Can you explain where that entitlement came from? More background information: https://developer.apple.com/forums/thread/799000 For support regarding entitlement application and requests: https://developer.apple.com/contact/topic/SC1102/subtopic/30072/solution/select So would you mind provide more information about that entitlement and a few checks I always recommend is, in your Apple Developer portal, review Access Groups and Entitlements to ensure nothing has changed or been revoked. Sometimes, older tooling may cache incorrect provisioning data, try cleaning build folders and restarting Xcode. When you said is not longer provisioned? I would, revoke existing distribution certificates and provisioning profiles, then generate new ones. Looking forward to know more about that entitlement. But we have other experts here that will jump into this thread when you provide the information probably. Cheers, Albert Pascual


Thank you for replying, Albert. I'm focusing on developing a macOS app using non-SwiftUI app lifecycle. I would need some SwiftUI-AppKit bridging in this project, and I might want to use Xcode Previews also on AppKit view controllers. I'm encountering the problem described in the first post, meaning that I can't experience both Xcode Previews and Storyboard well as expected. That popup window can be moved away, but it reappears back at the initial position every time I write source code. I created the first post a bit prematurely. Sorry for that. I noticed that it's nothing about the entry point. Instead, it's about making any instance of window controller from storyboards — instantiateInitialController() I used before, and other instantiate… methods. Just make a window controller from a storyboard and show its window (e.g. in applicationDidFinishLaunching(_:)). Only NSStoryboard trigger the problem, while NSNib don't. I also noticed that the mechanism behind the problem also works when the Xcode window is no

There are a few different issues that are at play here, so I'll try to untangle it a bit. Firstly to highlight what I send back to all reports of this symptom. This is what you probably saw in email already, but sharing here for everyone else's benefit: This symptom (Failed to start launchd_sim: could not bind to session, launchd_sim may have crashed or quit responding) occurs when launchd_sim (the principal process that kicks off the simulator) doesn't respond to an initial checkin message within a set time window. It is known to be caused by a variety of issues. Incorrect permissions on system temporary directories: Some users inadvertently change the permissions on system temporary directories, which can lead to this issue as well as problems in other software. If this is the issue, it can be fixed by running sudo chmod 1777 /private/var/tmp /private/tmp. 3rd Party Security Software: Some 3rd party security software can cause significant performance delays loading processes from the simulator

Thanks for the post and thanks for the patience. Thank you for providing your app details and suggesting an efficient way to reproduce the issue. Using your existing App Store build is a great approach since all entitlements and deep linking configurations are already configured. Please include the APP ID in the bug. What I want from the team is an answer if AASA files allow none unicode URLs and with your code showing what you are trying to do will help get across to all the teams involved. In the focused sample, ddd your team’s App ID to your App Association File (AASA) so we can build and run your app directly. Looking forward to get to a resolution on this issue. Albert Pascual
  Worldwide Developer Relations.

Thanks for your post @Yashya From: https://developer.apple.com/swift-student-challenge/eligibility/ “Your app playground must be built with and run on Swift Playground 4.6 or Xcode 26” Answered here: https://developer.apple.com/forums/thread/814690 Hope this helps and good luck on your project!! Albert Pascual
  Worldwide Developer Relations.

Is there a documentation or even a public sample code for this anywhere, which I could check? Sort of? Several years ago, we released the HomeKit ADK (Accessory Development Kit) as open source. The ADK is the platform we've been recommending creating HomeKit accessories with for several years, so by definition, it can create a fully functional accessory. However, the project itself is designed to run on an embedded platform, so getting it to run on macOS would be a bit of work. For what it's worth, there are also third-party projects that implement HAP (for example, Homebridge), which make it fairly easy to bridge into HomeKit. None of that is formally supported by Apple, but it's certainly possible to get it working. __ Kevin Elliott DTS Engineer, CoreOS/Hardware

Thanks for your post, on your screenshots you show the simulators not the devices. Also, your Xcode is one version old, you should update the Xcode version from the App Store. Ok, this message usually means Xcode can’t find a connected physical device that matches the deployment target or provisioning profile settings of your project. If you planning to use the simulator as shown in your screenshot, select a Simulators, go to the device toolbar in Xcode → choose a simulator (e.g., iPhone 17 Pro). Build & run, the project will launch in the simulator instead of looking for a physical device. Or better yet, connect a Physical Device. Connect your iPhone/iPad via USB. Trust the Mac when prompted on the device. In Xcode, the device should appear under “Connected Devices” in the toolbar. Check Deployment Target & Provisioning Profile. Make sure the deployment target supports your device’s iOS version. In Signing & Capabilities, confirm a va

Thank you for your post and your screenshot. While the screenshot depicts the app as a SwiftUI View, your post explicitly mentions that the app is built using UIKit Storyboards? When utilizing Xcode Previews with a storyboard-based macOS application that retains the default window controller entry point, it is important to note that the app’s entry point is typically defined by a window controller in the storyboard (often linked to the initial scene). In full-screen mode, macOS may preserve this state across UI refreshes. Could you please isolate the entry point of the app and create a new focused project that displays it? Additionally, I recommend providing your expectations so that we can assist you in fulfilling them. If you intend to use SwiftUI, I would suggest sticking to that framework. Albert Pascual
  Worldwide Developer Relations.