Apple Maps Guides

This is tricky. My best guess is that translationTask(_:action:) is missing all the magic concurrency decorations required to make this work nicely. To get this to build right now you can mark the closure as sendable, like so: .translationTask(configuration) { @Sendable session in do { try await session.prepareTranslation() } catch { // Handle any errors. } } This compiles in Xcode 26.1 using the Swift 6 language mode and: Approachable Concurrency enabled Default Actor Isolation set to MainActor Note I’m using prepareTranslation() in my examples because it’s simpler, and that makes it easier to focus on the core issue. The drawback to this is that you can no longer access main-actor-isolated state from the closure. You can work around that using MainActor.run(…): try await session.prepareTranslation() … no isolation … await MainActor.run { … main-actor isolated … } Clearly this is less than ideal and I encourage you to file a bug against… actually, I think it’d be best to file a bug against the Translating te

[quote='868176022, dhoelzl, /thread/808875?answerId=868176022#868176022, /profile/dhoelzl'] revocation check should also be done here like the browsers do. [/quote] OK. I’m going to factor that into my research. Thanks. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Let’s start with the easy one: [quote='868196022, veer_dutta07, /thread/809007?answerId=868196022#868196022, /profile/veer_dutta07'] Does the same behavior apply to the send completion handler as well? [/quote] Yes. [quote='868196022, veer_dutta07, /thread/809007?answerId=868196022#868196022, /profile/veer_dutta07'] If I suspend the dispatch queue on which async events for the NWConnection are delivered [/quote] Suspend for how long? If you suspend the queue indefinitely then you’ll definitely have problems. You can release a suspended queue. Dispatch will trap in that case. Given that, you either end up with a leak (if you ‘forget’ the reference to the queue) or abandoned memory (if you maintain that reference). The queue, any blocks on it, and anything they reference will all hang around in memory indefinitely. It’s fine to suspend and then promptly resume the queue; everything will clean up after the resume. [quote='868196022, veer_dutta07, /thread/809007?answerId=868196022#868196022, /profile/veer_dutta07

[quote='868260022, Infibrite, /thread/809012?answerId=868260022#868260022, /profile/Infibrite'] our earlier “Network Extension” tag was a mistake. [/quote] And presumably so was the reply you posted about 10 hours before this one |-: Anyway, the behaviour you’ve described doesn’t gel with Network Extension at all, so I’ve re-tagged your thread accordingly. When dealing with keychain sharing, there are two factors in play: Build time Run time I’m gonna focus on the build-time stuff, because a) that’s where you seem to be stuck, and b) I’m not familiar with Matter extensions and there could be run-time restrictions I’m not familiar with. So, regarding your build, you wrote: [quote='868260022, Infibrite, /thread/809012?answerId=868260022#868260022, /profile/Infibrite'] Could you enable Keychain Sharing for these iOS App IDs … ? [/quote] There’s nothing for us to enable here. Every App ID supports keychain sharing [1]. To illustrate this: I using Xcode 26.1 to create a new test project from the iOS > App templ

None of this strikes me as particularly surprising. The packet path is extremely ‘hot’, so adding any work to it is costly. The best thing you can do to improve performance is to avoid the .delay verdict, but your test code is already doing that. Before I send you off to file a bug about this, I have a couple of things for you to check: Make sure you reproduce this on a ‘clean’ machine. I often see weird problems being reported by folks only for us to track it down to some enterprise security setup affecting their main work Mac. If you have any additional network debug logging enabled — see the various instructions on our Bug Reporting > Profiles and Logs page — make sure to disable that during your tests. Usually I test NE stuff on a VM, but in this case you’ll want to run your tests on real hardware. VMs are great, but one place where they differ from real machines is performance. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='809205021, vtsang2025, /thread/809205, /profile/vtsang2025'] Is it an expected behaviour or a bug in the Release Candidate? [/quote] I don’t think that actually matters, in that it’s still fundamentally the wrong behaviour )-: Please do file a bug about this. I’d appreciate you posting your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='809183021, kaloramik, /thread/809183, /profile/kaloramik'] My feature request is [/quote] The best way to get this suggestion to the folks who can act on it is to put it in an enhancement request. Please post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='809030021, pankaja, /thread/809030, /profile/pankaja'] This makes me believe something related to local network access … is not being applied correctly in the release/TestFlight environment. [/quote] That’s not impossible, but my experience is that it’s not common. Rather, most folks who see problems like this actually have a Release build issue. I recommend that you check this by following the process in Isolating Code Signing Problems from Build Problems. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Indeed. While this is a long-standing issue, I was kinda surprised that we don’t have existing bug report for it, or at least not one that I could find. So thanks for filing FB21252859. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I recommend that you report this officially by filing a bug. Please post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Are you doing this from Keychain Access? If so, make sure you have the My Certificates tab selected at the top. That shows you the digital identities in your keychain, where each digital identity is the combination of a certificate and a private key that matches the public key in the certificate. If the digital identity is listed there, you should be able to export it as a .p12, which contains both items. OTOH, if that doesn’t list your digital identity then something else is wrong. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='868218022, lis-developer, /thread/809018?answerId=868218022#868218022, /profile/lis-developer'] Now all my subsequential submissions take mere a couple of minutes. [/quote] Yeah, that seems to be a pretty common pattern. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com