Apple Maps Guides

I’ve run into a similar issue in a macOS app and ended up rethinking how to use SwiftUI’s focus system. The app has the usual triple-panel layout: sidebar, content, inspector. The content is two tables, either of which can be focused. Each table has a TableController, exposed via .focused(). The inspector reads the focused controller to update its display, and the sidebar shows its selection—both via @FocusedValue. On paper this works, but there’s a catch: when the sidebar or inspector itself gains focus (e.g. a text field), the focused table controller becomes nil. I tried various .focus modifiers but could never get the behaviour I wanted. What I really needed was a property influenced by focus but not identical to it. For example: Use the focused table controller if one exists. Otherwise fall back to the last focused table controller. Add other rules as needed. The solution was to introduce an active table controller managed by an @Observable object in the environment. The sidebar and inspector observe thi

Hey @DTS Engineer there isn't a sample code at this stage in the documentation. There is only the documentation explaining how to use Wi-Fi Aware on the Apple platform. Can you provide links to a real sample application to just run and test on our end. Would be happy to reproduce it with your sample code. Right now the documentation looks a bit unfinished with missing states between what you actually see in XCode and the way you need to build a real application. Even if that's the case i have been able to build one on my end and test the flow and the current API.

For development , we were facing issue while compiling application, Apple has approved our request of endpoint security entitlements #1 _es_new_client, referenced from: AppNameFileControl.ExtensionMain.(startESClient in _6F8923D12EE413BBE2532B27F937A19F)() -> () in ExtensionMain.o _es_respond_auth_result, referenced from: closure #1 (Swift.OpaquePointer, Swift.UnsafePointer<__C.es_message_t>) -> () in AppNameFileControl.ExtensionMain.(startESClient in _6F8923D12EE413BBE2532B27F937A19F)() -> () in ExtensionMain.o closure #1 (Swift.OpaquePointer, Swift.UnsafePointer<__C.es_message_t>) -> () in AppNameFileControl.ExtensionMain.(startESClient in _6F8923D12EE413BBE2532B27F937A19F)() -> () in ExtensionMain.o _es_subscribe, referenced from: AppNameFileControl.ExtensionMain.(startESClient in _6F8923D12EE413BBE2532B27F937A19F)() -> () in ExtensionMain.o #2 error: link command failed with exit code 1 (use -v to see invocation) ld: framework 'EndpointSecurity' not found clang: erro

Hey @sengui the whole idea of Wi-Fi Aware and having it been exposed by Apple is to be able to use it with other platforms. The current way been exposed on their end and the API that exist right now it isn't possible and that's the whole problem we are facing. What is needed from Apple end is to expose the API raw as any other platform does so the developers can take full advantage of it. We are proposing exactly that. As i understand the whole idea of Wi-Fi Aware is to be dynamic so the term peer database doesn't apply and it shouldn't. In case that somehow applies which i don't believe it does that is where the problem lies i suppose. Can you maybe share more information about your own tests with the @DTS Engineer ? That will be helpful As i mentioned it is designed to be dynamic with preserved privacy by the system when discovering. The system shields MAC address and adds opaque handles as well and advertising frequency is changed constantly. The idea is to be ephemeral (short-lived)

@pcfist Thanks for the link. Does that actually work? Some of the posts after the one you linked indicate that it still doesn't work in the end. Yesterday I took the plunge and updated my Mac to macOS 26.0.1 and added a dual boot of macOS 15.7.1. I need to get my app updated for macOS 26 and still support macOS 15 (and 14) and this was the only possible solution for now. Interestingly, both installs of macOS have the same Provisioning UUID. This actually helps some. I can boot into my main system (now macOS 26) and do a development build and test the app with macOS 26. When I want to verify things still work under macOS 15 I can copy the development build to a shared folder, reboot into the other partition with macOS 15, and run the development build from the shared folder. Since both systems have the same Provisioning UUID the app runs without complaint. No need to bother with Test Flight. It's still a giant pain to have to dual boot just to check on a quick change, but at least it can be done and I don't ha

When we tried using this feature, we were not able to get it to work on iOS 26. We stumbled upon this ticket (https://developer.apple.com/forums/thread/797538?answerId=854825022#854825022) in the Apple Developer forum, in which possibly an Apple engineer claims it is supported ONLY for iPadOS 26. That engineer would be me, and yes, what I said there is correct. Background GPU access is currently only available on iPads. 96% of the users are on iPhone (compared to iPad), and if we refer to the official documentation above, it claims that this feature should work on iOS 26. What the documentation says is that the APIs themselves are available on iOS and iPadOS and that background GPU access is not available on all devices, both of which are true. This both simplifies the implementation on both platforms and allows for future API evolution without requiring major API revision. This is the same basic pattern most of our APIs use when functionality is only available on some hardware. __ Kevin Ell

Hello. Before attempting to modify a playlist you must first check the canEdit attribute (see https://developer.apple.com/documentation/applemusicapi/libraryplaylists/attributes-data.dictionary) to discover if it is possible to modify the playlist. If canEdit is false then attempts to modify the playlist will return an error. In the current version of these APIs, collaborative playlists aways have canEdit set to false. If you would like Apple to consider adding the ability to modify collaborative playlists please file an enhancement request asking for this functionality. You can file an enhancement request using the Feedback Assistant. If you file a request, please post the Feedback number here. If you're not familiar with how to file enhancement requests, take a look at Bug Reporting: How and Why?

Hello! We would like to investigate this issue further. Please file a feedback report with a sysdiagnose (diagnostic logs) from your Apple Vision Pro soon after attempting to install your app from TestFlight and reply to this thread with the feedback ID. You can learn more about filing feedback with Feedback Assistant. We’ll follow up via the feedback report. Thanks!

Thank you for your post. 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. A member of the App Review team will help you with your questions regarding the review process and the App Review Guidelines.

Same issue here. There is not much to be done until Apple fixed their framework, but I'd like to share my workaround. Unfortunately, using UIControl.Event instead of UIEvent does not work as advertised. The call just typecasts the pointer (UIEvent*)nil to the value UIControl.Event; that explains why the event always results in UIControlEvents(rawValue:0). My event handler used to look like this: @IBAction internal func sliderValueChanged(_ sender: Any, forEvent event: UIEvent) { if let touchEvent = event.allTouches?.first { switch touchEvent.phase { case .began: ... case .moved: ... case .ended: ... default: break } } } Since the event is not much of any help anymore, I've replaced the old handler with three distinct ones: @IBAction internal func sliderValueChanged(_ sender: Any, forEvent event: UIEvent) { ... } @IBAction func sliderDidBeginValueChange(_ sender: Any) { ... } @IBAction func sliderDidEndValueChange(_ sender: Any) { ... } The handler sliderDidBeginValueChange is connected to Touch Down