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

FWIW, I reproduced the discrepancy using: Xcode 26.3. In Preview and in Simulator. iPhone 17 Pro and iPhone 17 Pro Max. Didn't test others.

Thank you for your response. I have verified that this issue is still present in iOS/iPadOS version 26.2. Following your recommendation, I have submitted a report through Feedback. Please let me know if any additional information would be helpful.🙏🙏🙏

https://www.wenjuan.com/s/NVRfYrJ/ Here is the link to my questionnaire. I forgot to put it in the post. It is terrible.

Thanks for the question, there are better developers to answer your questions than I am, as I am not in that team. But if you need a device to show your capabilities beyond the simulator it seems like is allowed. Please check this reply: https://developer.apple.com/forums/thread/815172 I believe Swift Playgrounds supports the use of the front-facing camera for detecting body movements. Frameworks such as ARKit and Vision provide capabilities for face tracking and human body pose detection. ARKit's ARFaceTrackingConfiguration. Good luck, hopefully other people from that team jumps in this thread. But reading the Student Challenge Rule webpage, I do not see anything that prevents you. https://developer.apple.com/swift-student-challenge/policy/ Albert Pascual
  Worldwide Developer Relations.

So, let me start by going back to what I said here: ...is an XPC connection failure with callservicesd, typically caused by callservicesd crashing. That's not common, so if your app is causing frequent resets, then that's an issue that might be worth looking into. By definition, that's not a normal failure. Your app is basically being notified of a failure because it's not clear what else we can/should do. That also means I don't necessarily have a great solution, certainly not one I can guarantee to be reliable. That leads to here: there is no initial providerDidBegin for first CXProvider as logger misses early logs Do you have any sense about how long your app is typically able to stay active, both in terms of being awake/active and in absolute terms (wake or suspended)? This primarily comes up with long-running kiosks apps, but one of the issues that can happen to long-running apps is that as they get better and better at working for very long periods of time (in kiosk apps, this is typically days/weeks of

@itsme_joris Thanks I see the bug number. Thanks for filing this. @denisa_toderean1 Why don't you think is related to Universal Links? Is your app registering universal links with a link to a AASA file? Thanks Albert Pascual
  Worldwide Developer Relations.

I investigated further and found your answer! UndoManager is the API in the Foundation framework for undo/redo and SwiftUI has an environment value for that undoManager. This example disables undo on TextField on Mac struct ContentView: View { @Environment(.undoManager) var undoManager: UndoManager? var body: some View { VStack { TextField(Test, text: $text) } .task { undoManager?.disableUndoRegistration() } } } Let me know if this answers your question  Travis Trotto - DTS Engineer

Thank you for the code and post. However, you have not provided the complete code, and the code you provided will not compile due to missing controls that are not defined. I recommend you provide a focused sample project that demonstrates both the unexpected output and the expected output as well the configuration of the project itself. 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. Albert Pascual
  Worldwide Developer Relations.

BLE scanning does not stop in the background. But it slows down. So for your situation, what is probably happening is: while you are juggling your scanning batches, stopping one and starting the other, it is possible that your app is not being able to start the next batch after stopping the previous one. If that happens, you would have stopped the scan but was never able to restart the other for one reason or another. If you believe the scan has actually stopped, you may want to double check the next batch was able to have started, perhaps confirm by logging the start if the next batch and see if you get there. And if you confirm the scan never starts, then debug why this is occurring. the scan is not stopping, but because it slows down when the app is in the background, you think it has stopped due to the inability to discover advertising peripherals. This is a standard behavior of iOS and the only solution would be to increase the advertising frequency of the peripherals. If the advertising interva