Apple Maps Guides

As you’ve noticed, Swift Playground currently doesn’t support the iOS 26 SDK. We understand that there’s strong demand for that, but I can’t offer any advice as to when it’ll happen. If you need you use iOS 26 SDK features right now, your only real option is to create your playground with Xcode. Make sure to create an app playground, as explained on Developer > Swift Student Challenge > Get ready. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

This came up in a different context, and I wanted to post the associated bug number (FB21271237) here, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I love a question with an easy answer! No. Currently the Foundation Models framework only has access to the on-device model. PCC is never used. Ever. Inference is entirely on-device. For an added layer of privacy and security assurance, Apple does not log anything about the inference other than counting that your app called the model (since it's a shared operating system resource). Apple does not log input or output, so Apple has no access to your prompts, inputs, or results.

It would be really nice if RealityView could be kept in sync for all platforms. ViewAttachmentComponents are a very useful addition and it is a shame that it is only available on VisionOS, and not iOS. Is there an easy way to add simple SwiftUI views to a RealityView in iOS? I know ViewAttachmentComponents are visionOS only, but can we achieve the same functionality by building Entities manually and somehow mapping SwiftUI views onto it? Is there sample code somewhere we could look at? Thanks

Hi Albert, Thank you for the links. After reviewing both documentation pages, I've implemented a complete test following the specifications, but password autofill is not working. Test Implementation AASA File (accessible at http://localhost:8080/.well-known/apple-app-site-association): { webcredentials: { apps: [ZW962TGA3F.com.test.PasswordAutofillTest] } } ✅ Served with Content-Type: application/json ✅ Verified accessible via curl ✅ Team ID matches Apple Developer account Associated Domains Entitlement: webcredentials:localhost:8080 ✅ Configured in both Debug and Release entitlements ✅ Bundle ID: com.test.PasswordAutofillTest SwiftUI Implementation: TextField(Email, text: $email) .textContentType(.username) SecureField(Password, text: $password) .textContentType(.password) Authentication Flow: App sends POST to http://localhost:8080/login with credentials Server returns 200 OK App displays Login successful Server logs confirm request received and processed Result ❌ No Save Password prompt a

It might seem like the mechanism to build the list of cypher suites in the Client Hello is simple — you start out with some defaults and then every call to sec_protocol_options_append_tls_ciphersuite adds one to the end — but that’s not the case. Like pretty much everything in TLS, it’s ridiculously complicated, based on factors like TLS version, policy, hardware capabilities, and so on. You can get an inkling of this in the BoringSSL open source but the Apple version of that is significantly more complicated. After spending way too much time down that rabbit hole, I came to the conclusion that I was actually trying to describe the implementation, not the API, and that’s not good [1]. I think the only thing you can safely say about the sec_protocol_options_append_tls_ciphersuite API is that it adds the cypher suite to the list of cypher suites that the implementation might choose to use. Which brings me to a question: What’s your high-level goal here? Why do you need these specific cypher suites enab

It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits. The screenshot above is the iOS system's crash log Just clarify what we’re talking about here, this is an Apple crash report from iOS 26.1: Exception Type: EXC_BAD_ACCESS (SIGKILL) Exception Subtype: KERN_PROTECTION_FAILURE at 0x0000000000000000 … Thread 0 name: Dispatch queue: com.apple.main-thread Thread 0 Crashed: 0 ??? 0x0 ??? 1 Test808813 0x10058c128 -[MainViewController tableView:didSelectRowAtIndexPath:] + 100 2 UIKitCore 0x1a563bc98 -[UITableView _selectRowAtIndexPath:animated:scrollPosition:notifyDelegate:isCellMult… 3 UIKitCore 0x1a563bfbc -[UITableView _userSelectRowAtPendingSelectionIndexPath:animatedSelection:] + 255 4 UIKitCore 0x1a563c0c8 -[UITableView _userSelectRowAtPendingSelectionIndexPath:] + 215 5 UIKitCore 0x1a407d878 -[_UIAfterCACommitBlock run] + 71 … You’re concern is with that SIGKILL, where prior to iOS 18 this was a SIGSEGV. That doesn’t strike me as

Thanks for your explanation of how you got to where you are. My natural inclination here is to use a UIApplication background task with an expiration handler. It sounds like you’re already doing most of that. If you simply delete the preflight code and rely on your expiration handler, does that work in practice? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’ve attached my test project to FB21240977. Thanks for that. I did some poking around and I believe this error is being triggered by the echoed pong frame containing no data. If I change this line: try await connection.ping(Data()) { to this: try await connection.ping(Data(hello.utf8)) { I don’t see the error. ps It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Hmmm, that wasn’t the answer I was expecting. Something is clearly borked on your machine. You wrote: [quote='868691022, swdev-sos, /thread/809359?answerId=868691022#868691022, /profile/swdev-sos'] Does the pkgbuild command have a cache that can be deleted? [/quote] AFAIK that’s not the case. [quote='868691022, swdev-sos, /thread/809359?answerId=868691022#868691022, /profile/swdev-sos'] We are both using [Xcode] 16.2. [/quote] The Xcode version doesn’t matter here, but rather the OS version. Are you both on the same version of macOS? If you create a new user account on your Mac, does the problem reproduce there? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com