Apple Maps Guides

Hi Ed, Thank you for confirming that the native animation APIs are effectively non-interruptible. This validation saves us from chasing a magic configuration that doesn't exist. Sharing a bit about our use cases that the user must be able to interrupt the route preview immediately (e.g., to pan or zoom while the camera is moving on for example, 10 seconds of zooming). Regarding the performance spikes I mentioned: We have already implemented several optimizations to mitigate the 120Hz/8.33ms constraint you highlighted: Capping Frame Rate: We set preferredFrameRateRange to target 30-45 FPS (avoiding the 120Hz ProMotion tax) to reduce the workload and changed it depends on the device spec, how close or far is the zooming. Visual Thresholds: We try to skip rendering frames during CADisplayLink ticking with some threshold. Even with these throttles in place, simply calling setVisibleMapRect(..., animated: false) 30 times a second drives CPU usage to 80-100% on the simulator, likely due to the heavy vector tile re-

Thank you for your response and for taking the time to read the Technical Note. I believe you have now realized that Universal Links function consistently well, but there could be several reasons for their behavior deviating from expectations: When encountering issues related to Apple-app-site-association files and associated domains, particularly when they function correctly on the first attempt but fail on subsequent attempts within the same tab, several potential security and configuration factors could be at play: JavaScript Logic Errors: Although you mentioned that the code execution is identical, race conditions or state mismanagement within your JavaScript could lead to differing outcomes on successive runs. Please verify for such possibilities. Error Handling and Logs: Enhance error handling surrounding the associated domain validation logic and ensure comprehensive logging to capture any discrepancies during the second invocation. By systematically examining these areas, you should be able t

There is a good example of animating a map using MKMapCamera in our Look Around sample code project. Using the map camera gives you better control over writing your own animation sequences, as the animations provided by setting the animation parameter of setVisibleMapRect to true will be decided by the system. However, as you found, those animations are effectively non-interruptible in practice due to how MapKit manages animations, regardless if you use the UIView family of animation methods, or UIViewPropertyAnimator. Enhancement requests for better integration across the animation APIs are welcomed! I've tried using CADisplayLink to manually animate the camera per system fresh rate, it works very well, I can stop the camera movement anytime there are touches, but it causes the resource CPU spikes. While you can use CADisplayLink to control rendering of any UIView on a frame-by-frame basis, you have to keep in mind the stringent performance targets you need to hit in order to not introduce

Have you tried to just upload the app again with a new Build number so it will be reviewed again? My experience is that every now and then this problem occurs in Apple's test environment, without anybody really knowing why. And the reviewers are not really investigating this. On the next review it will probably work. At least this is my year long experience.

Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem, and post the Feedback number here once you do. If you post the Feedback number here I'll check the status next time I do a sweep of forums posts where I've suggested bug reports. Bug Reporting: How and Why? has tips on creating your bug report.

Hello, I recently had an unusual experience, and I’m wondering if this is related to Apple’s policies, so I wanted to ask. It's not really about policy as such, but is actually about how the system handles notifications generally. While a call is in Picture-in-Picture (PIP) mode, notification pushes from the same app do not appear. The API is being triggered, but the notification banner does not show on the device. The issue here isn't PIP, it's the fact that the app is awake and considered active. When an app is active, the system does not directly present notifications, but instead delivers them directly to the app through userNotificationCenter(_:willPresent:withCompletionHandler:). The app then has control over whether or not the notification is presented. Note that this is the same reason notifications don't necessarily appear when the app is foregrounded. The only difference here is that PIP is a slightly different variation of active/foreground. Once PIP is closed, the notifications start appe

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.