Apple Maps Guides

Thanks for this post. You have seen the issue on the usage of the NSSheetMoveHelper. Even if you believe Apple is aware of this issue, I recommend posting a focused sample here to demonstrate the specific problem and how the NSSheetMoveHelper is causing it. 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. If the issue persists after updating to the latest version, I will request that you submit a bug report. Could you please provide the focused sample? Albert Pascual
  Worldwide Developer Relations.

Thank you for your post. This is definitely a huge delay. We recommend that you sign up for a session with App Review during the weekly Meet with Apple event. Sign in with your Developer ID and select Request a one-on-one App Review consultation. https://developer.apple.com/events/view/upcoming-events A member of the App Review team will help you with your questions regarding the review process and the App Review Guidelines. Or contact them https://developer.apple.com/contact/#!/topic/select Looking forward to see your app in the store! Albert Pascual
  Worldwide Developer Relations.

Thank you for your post. Migrating your Swift project from a free Apple Developer account to a paid one does not necessitate rebuilding the project from scratch. Here is a step-by-step guide to facilitate a seamless transition: Log into Your Paid Account: Sign in to your Mac using the Apple Account associated with your paid Developer account. Open Xcode and navigate to Xcode > Preferences > Accounts. Click the “+” button to add your paid Apple ID if it is not already listed. Update Code Signing: Open your Xcode project. Select your project in the Project Navigator to access the project settings. Navigate to the “Signing & Capabilities” tab for your target. Ensure that your team is configured to your paid account. If not, click on the team dropdown and select your paid developer account. Adjust Provisioning Profiles: Xcode typically automates the downloading of provisioning profiles when signed in with the paid account. You can force a refresh by visiting Window &g

Hi @ManojS, You can learn more about Apple Intelligence here and specifically learn about the Image Playground API here. Can you please rephrase the question you're asking so that I can assist? Best, -J

Please familiarize yourself with the Developer News page. https://developer.apple.com/news/ As of today, Apple has posted two articles about this topic: New requirements for apps available in Texas Next steps for apps distributed in Texas I'd highly encourage watching these WWDC25 videos a few times to catch all the details: Deliver age-appropriate experiences in your app - WWDC25 Enhance child safety with PermissionKit - WWDC25

This is not legal advice, nor a statement from Apple. I will share what I'm going to do in my apps and recommend to others. How I interpret 121.056 (B) (1) is basically, use the signals when they're available. If they're not available, you can't use them. You can't do the impossible. So if you have an app update that supports iOS 26, implement it there, and < 26 you simply can't. As a developer, it is impossible to use the age signals provided by the App Store if they don't exist. If you're not comfortable with this approach, file feedback asking for support on devices < 26. Hypothetically, if Apple were to add support to, say iOS 18, it would still be something like iOS 18.8.x or higher. I am closely following the OS Usage page and waiting for an update to show the adoption of 26. https://developer.apple.com/support/app-store/ For my specific usage, I'm moving my apps to 26+ for my updates. However, I have apps that include watch extensions, and an Apple Vision Pro target. Th

Any chance you can take this code, put it in a small test project that reproduces the issue, and then attach that to your bug (FB21240977)? I tried grabbing the code snippet from your bug and putting it in my own test project, but that didn’t reproduce the problem. Given that, I’m not sure whether that’s because I’m not seeing the problem in my environment or whether I made a mistake when building my test project. If you can share a test project that reproduces the problem, that’ll eliminate that second possibility. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

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