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

Thank for the post, I’m not int that team at all nor I have inside information, Im just looking at the eligibility rules. According to the requirements, the project must run on either Swift Playgrounds 4.6 or Xcode 26, or later. Since Swift Playgrounds looks like doesn’t support building .metal shader files the same way Xcode does, it seems like you could technically meet the requirements by only running the project in Xcode. 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” OR is the key word here. Hope this helps, you can also sent that question to that team as they have an email address on their page. Albert Pascual
  Worldwide Developer Relations.

Thanks for the post and happy you want to create a game. But your post does not provide specific questions we can answer. About the development environment you asked in your post if translate worked well: Development Environment: Xcode: This is Apple's integrated development environment (IDE). You'll need it to write and build your iOS or macOS app. Download it from the Mac App Store. Swift (Programming Language): Swift is Apple's preferred language for iOS/macOS development. It's modern, safe, and relatively easy to learn. UIKit or SwiftUI (User Interface Framework): UIKit: The traditional framework. Mature and highly documented. Might be more suitable if your team is already familiar with it. SwiftUI: Apple's newer, declarative UI framework. Easier to write cleaner and more maintainable code, especially for simple layouts. Consider this if you're starting fresh. We will focus on SwiftUI for this guide. Here are a few suggestions that might help it attrac

Whether querying by recordName should work in production CloudKit Yes, in case you have the appropriate indice in the CloudKit production environment. What specifically causes the “Field recordName is not marked queryable” error in TestFlight builds The error is triggered when you try yo query a CloudKit record type and the type doesn't have the index for its recordName field. If the error only occurs in the production environment, which is by default used by a TestFlight build, and not in the development environment, it will indicate that the CloudKit schema in the development environment is not completely deployed to the production environment. To address the error, try to use CloudKit Console to add the indice, as discussed here and here. What steps are required to ensure CloudKit schemas are correctly deployed for cross-platform sync If you can use CKTool to dump the schemas, as discussed in Automate CloudKit tests with cktool and declarative schema, and then compare and contrast them. I

[quote='874740022, JE-H, /thread/813586?answerId=874740022#874740022, /profile/JE-H'] Feedback ID: FB21856584 [/quote] OK. I had a quick look and confirmed it’s with the right folks. I can’t offer any timeline for its investigation. If I were in your shoes I would attempt to speed things up by reducing your upload size, at least in the common case of internal builds (rather than those released to customers). I’ve offered some suggestions for how you might approach that above, and I encourage you to explore them. If you have any follow-up questions about that side of this, I’d be happy to answer those here. OTOH, if you’re looking for updates about your bug report, you can monitor that in Feedback Assistant. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Thanks for taking the time to share your question here. Unfortunately, it hasn't received an answer yet. Here are a few suggestions that might help it attract more attention: Provide more details: Expanding on your post to include any error messages, code snippets, steps you've already taken to troubleshoot, and the expected/actual outcomes would be very helpful. Be specific about your technology stack: Clearly state the programming languages, frameworks, or tools you are using. Check for duplicates: Before posting, make sure your question hasn't been asked before. You can use the search bar to find similar threads. I'm sure someone in the community will be able to help once you have a chance to update your post. Albert Pascual
  Worldwide Developer Relations.

Thank you for that! The bug is being routed to the correct team and they'll provide you feedback on the FB link. For more details on when you'll see updates to your report, please see What to expect after submission. Thanks again. Albert Pascual
  Worldwide Developer Relations.

Dear Illia, Thanks for sending over the storyboard and the screenshot. I wasn't able to detect any immediate issues at first glance. Would it be possible for you to please send it in the form of a small test project that replicates the issue? 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 in advance, Richard Yeh  Developer Technical Support

Hi, Sorry to hear you are having trouble using previews. A few things you could try: Run xcrun simctl --set previews list to see the list of previews sims. Perhaps you'll see the UUID list there Similarly if you wanted to delete all the previews sims run xcrun simctl --set previews delete all If you are still seeing issues we'd suggest filing a feedback report We will need the diagnostics Xcode Previews generates in order to help us understand the error the previews system is encountering. 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 erro

Have a look at this TN to check: TN3117: Resolving architecture build errors on Apple silicon | Apple Developer Documentation

Hi Albert, We were also intrigued by this incident and went ahead and called up the customers affected by it. All the clients had installed iOS 26.2.x. With their feedback, we could reproduce the issue: (EU region, iPhone running 26.2.1) Install an alternative browser, such as Chrome Long press on the Safari icon and choose Remove app Make the alternative browser default Open an app that does a redirect to an external url -> redirect no longer works Reinstalling Safari fixes the issue again.