I noticed a new feature in iOS 27 where someone's birthday will be shown on your phone while you're on a phone call with the birthday person. Is there an API that we can tap into to provide this information? The birthday says "Found in Contacts", but I'm hoping to provide other kinds of dates like Anniversaries through my app where I expose their dates to Siri and Spotlight Search.

Dear Developer Technical Support, I wanted to ask for technical advice regarding the DeviceActivityMonitor which is part of the DeviceActivity framework: The DeviceActivityMonitor has a very strict memory limit of 6MB. That’s not a lot and it doesn't leave a lot of room for any kind of code that accesses permanently stored data. I would therefore like to ask for advice on best-practices on how to share information between the main app and that extension: Is UserDefaults a good idea to use here? Can/should we use CoreData or SwiftData? Should we build super small file-based data sharing (e.g. via .plists)? Why is it necessary to share data? This can be simple things that inform the decision of the device activity monitor in intervalDidStart, intervalDidEnd, eventDidReachThreshold, eventWillReachThresholdWarning. For example a setting where the user decides if they want to receive a push notification on eventWillReachThresholdWarning. Or the list of tokens that is supposed to be blocked in eventDidReachThreshold or intervalDidStart. I’m asking because even though we are super careful and conservative about memory allocations in our DeviceActivityMonitor we are regularly seeing it being killed due to memory pressure. What’s the best way to approach this? I’m grateful for any kinds of hints! Thanks a lot and have a great day! – Frederik

I wrote a python script MXSymbolicate to symbolicate crash reports produced by MetricKit. To symbolicate a given frame, it needs the symbol file for that frame's library. For system libraries, my system only has the requisite files on disk if I've plugged an iOS device of that type at that iOS version into my computer at some point (I assume these symbol files from the device are generated by Xcode when it's preparing to debug on a new device). All these different versions of the symbol files take up a fair bit of space on my machine over time, and it means the symbolication process isn't very portable. Is there a better way to get ahold of symbol files for system libraries? Or is the expectation that we (as third party developers) only symbolicate the frames from our own apps?

Xcode26.2, xcode26.3: with each Xcode version upgrading from xcode26.0 to Xcode 26.2, xcode26.3, we saw size increased with same code running on different Xcode versions, freeze happened when run app on simulator, also our same XCtest cases randomly failure on Mac Mini, but successfuly on Mac book with same OS and xcode version

My app has a meaningful number of 0xdead10cc terminations because it deals with sqlite files in a shared app container. Are there any tips to diagnose them or track down which files are most often held open? Are they delivered to MetricKit as crash diagnostics? They're hard to identify in the Xcode organizer - I have to right-click on a suspect, Show in Finder, Show Package Contents, navigate into the proper sub-folder for my filter, then into the Logs subfolder, and look through the raw crash reports. And these crash reports don't identify the file that the lock is held open to, and they don't identify the correct culprit thread. Not all of them even show any of my code doing file IO. FB12292887

Hi everyone, I’m the developer of one sec, an app used by a large number of users globally to reduce time spent on social media and to build healthier digital habits. Because of this, we rely heavily on Apple’s Screen Time / DeviceActivity / FamilyControls, ManagedSettings APIs – and unfortunately, we’re seeing increasingly severe issues in production that directly impact hundreds of thousands of real iOS users. During the past years, we have been busy filing dozens of feedback requests for different Screen Time issues – and there has been no response from Apple at all. Developer Relations might be able to "confirm" that the bugs are present and that they ended up with the right team – but they are never addressed, neither are workarounds provided. Instead, the situation gets worse and worse. iOS 26 introduced a series of heavy regressions (which have been reported via Apple’s official bug report tool "Feedback Assistant" on iOS 26 beta 1 in June 2025 – and have not been addressed 10 Months later). This is very frustrating for us as developers, but also for our end-users who run into these issues every day. In the end this impacts our ability to build an amazing product and hurts revenue (which affects both us and Apple). 1. DeviceActivity thresholds are not firing at all This affects both: our app’s usage of the API and Apple’s own Screen Time limits Radars: FB22304617, FB20526837, FB15491936, FB12195437, FB15663329, FB18198691, FB18289475, FB19827144 2. Screen Time usage data is clearly corrupted Websites showing hundreds of hours per week Up to ~20 hours per day of usage reported for a single domain Radars: FB22304617, FB17777429, FB18464235 3. DeviceActivity thresholds reaching threshold immediately Newly introduced with iOS 26 Reported on iOS 26 beta 1 in June No response so far / no workaround DeviceActivity calls didReachThreshold immediately after creating the DeviceActivityEvent – instead of waiting till the defined threshold is actually reached. Radars: FB13696022, FB18351583, FB21320644, FB18927456, FB18061981 4. Randomly Randomizing ApplicationTokens From time to time, and without consistency, Screen Time suddenly provides new, random, unknown tokens to my app in the ShieldConfigurationDataSource and ShieldActionDelegate. This has been reported on many times before here on the dev forms, many many years back already: https://forums.developer.apple.com/forums/thread/756440 https://forums.developer.apple.com/forums/thread/758325 https://forums.developer.apple.com/forums/thread/758325?answerId=793267022#793267022 Radars: FB14082790 and FB18764644 5. Moving Tokens from one ManagedSettingsStore to Another Removing an ApplicationToken from one SettingsStore and then adding it to another while the target app remains in foreground leads to the re-use of the ShieldConfiguration. Which can be wrong in many scenarios. It is not possible to request a re-request of the ShieldConfiguration in that scenario. Radar: FB14237883 6. Unable to Open Parent App (one sec) from Shield Many times, when a target app is blocked by a shield, the user wants to perform some action (e.g. to unlock more time for the target app via an intervention). That means, that somehow I have to forward the user from a ShieldActionDelegate back into my target app. Unfortunately, there’s no API for that. Many apps on the App Store rely on private API to achieve that, but that’s too risky for a popular app like one sec. Radar: FB15079668 7. Unable to Open Target App from an ApplicationToken When a user has completed an intervention within one sec, and they indend to to continue to the target app, there is no way that one sec can open the target app just from the token alone. Sure, there are URL schemes, but that means the user has to manually assign URL schemes to each ApplicationToken. That is not a very user friendly process (and in many cases impossible, because not every app registers URL schemes). It would be better if there was a way that my app could open a target app directly from an ApplicationToken, e.g. via an AppIntent that can be run on a button press. This way, the selected apps would remain fully private while still offering advanced functionality: struct OpenTargetAppIntent: AppIntent, OpenAppFromApplicationTokenIntent { func perform() { return .result(openAppFromApplicationToken: applicationToken) } } Radar: FB15500695 Summary Thanks a lot for taking the time to read my feedback. If you have any questions, please feel free to reach out to me any time. I’m always happy to provide more details, logs, and steps to reproduce in my radars / feedback requests or in-person in Cupertino. It would be extremely helpful if someone from the Screen Time / DeviceActivity engineering team could: Take a look at the listed radars. Work on bug fixes and be transparent about when fixes will be shipped. Provide workarounds in the meantime. We genuinely want to build great, reliable experiences on top of Screen Time – but in its current state, it’s becoming very difficult to depend on. – Frederik

Hi Apple Developer Support / WeatherKit team, I’m trying to use native iOS WeatherKit through WeatherService.shared in a SwiftUI app. Every request fails before weather data is returned because WeatherDaemon cannot generate the WeatherKit JWT. I am not using the REST API or manually generating a JWT. This is the native Swift WeatherKit API. import WeatherKit import CoreLocation let current = try await WeatherService.shared.weather( for: CLLocation(latitude: 25.76, longitude: -80.19), including: .current ) I also tested the same pattern used in Apple’s sample project, “Fetching weather forecasts with WeatherKit,” which calls: WeatherService.shared.weather(for: location, including: .current) The error I get is: Failed to generate jwt token for: com.apple.weatherkit.authservice with error: Error Domain=WeatherDaemon.WDSJWTAuthenticatorServiceListener.Errors Code=2 "(null)" Encountered an error when fetching weather data subset; error=WeatherDaemon.WDSJWTAuthenticatorServiceListener.Errors 2 Error Domain=WeatherDaemon.WDSJWTAuthenticatorServiceListener.Errors Code=2 "(null)" Setup details: Paid Apple Developer Program account Native iOS SwiftUI app Physical iPhone, not Simulator WeatherKit capability enabled in Developer portal App ID has WeatherKit enabled Xcode Signing & Capabilities includes WeatherKit Automatic signing enabled Provisioning profile regenerated through Xcode App deleted and reinstalled after configuration changes Clean Build Folder / DerivedData cleanup attempted Bundle ID in Xcode matches the App ID in Developer portal Tested .current, .hourly, and .daily WeatherKit subset requests Ensured I am not running on “My Mac Designed for iPhone/iPad” I verified the built app’s entitlements. They include: application-identifier = [REDACTED_TEAM_ID].[REDACTED_BUNDLE_ID] com.apple.developer.team-identifier = [REDACTED_TEAM_ID] com.apple.developer.weatherkit = true get-task-allow = true The embedded provisioning profile also includes: com.apple.developer.weatherkit = true Because the entitlement and provisioning profile appear correct, and the failure happens during JWT generation before weather data is returned, this seems like either a WeatherKit entitlement propagation issue or a backend authorization issue. Can Apple staff clarify what WeatherDaemon.WDSJWTAuthenticatorServiceListener.Errors Code=2 means, and whether there is a way to verify that WeatherKit JWT generation is enabled for my App ID? I can provide my Team ID, Bundle ID, provisioning profile details, and full device logs privately if needed.

Are there any limitations with the new Trust Insights framework one should be aware of? Will it be available in all geographic regions? Does it work with all languages?

What was added in the version2 of the feature set?

I have a time tracking app that has sync between devices. I am using background push notifications and PKPushRegistry to react to updates from other devices - to perform a sync with the server from the watch app and afterwards to reload the complications. My question is: after I move to using WidgetKit for my complications, can I still reload my complications from the background, within the pushRegistry(_ registry: PKPushRegistry, didReceiveIncomingPushWith:..) method? Or is it subject to strict limits for updating from the background such as on iOS? If the above is not possible, what is the recommended way of keeping WidgetKit-based complications on the user's watch face up to date? Considering that I also need to do a sync with the server from the watch app before it has the latest data to be able to display the correct state of the complication.

We are encountering an issue with our App Clip invocation behavior: When attempting to invoke an Advanced App Clip Experience from a link in an email (digital invocation), the App Clip is not recognized. However, the Default App Clip Experience works correctly when invoked the same way. Interestingly, the Advanced App Clip Experience does launch successfully via physical invocation (scanning a QR code that encodes the same URL). Question: Is there any additional configuration required to enable an Advanced App Clip Experience for digital invocation (e.g., email, Messages, Safari), as opposed to physical invocation? Are there specific requirements—such as associated domains, Apple App Site Association (AASA) file setup, or App Store Connect configuration—that differ between digital and physical invocation methods?

My app is distributed through Unlisted App Distribution as it's for a specific audience. I was hoping to share a link to an App Clip experience to allow users to easily get started with it and the initial features, then allow them to install through StoreKit within the clip. When trying to open the App Clip, is shows the card, but I with an error: The operation could not be completed. (ASDErrorDomain error 507.)

Are there any plans to support multiple App Clips per app? Thank you.

Does the App Clip banner require the app to be live on the App Store, even for testing? Does Apple's CDN need time to cache/validate the AASA file, and is there a way to force re-validation? Are there known limitations with App Clip banners on non-production domains? Is there a diagnostic tool to verify our AASA file is being correctly read by iOS?

Will core motion ever be available to App Clips? Are there any workarounds for gathering device data. We use the camera and need to know coremotion data to verify the angles of the images coming in From the camera. We have an app that has some perfect use cases for app clips in measuring and returning results however we need the angles of the device for accuracy.

App Clips serve a useful purpose, a temporary or temporal mini app experience. I'd like to see this come to both unlisted and custom apps. Unlisted, easier argument. Same as public, just not searchable on the store. You need a link for an unlisted app ...... or an app clip code!!! For custom apps, a few use cases might be an internal conference that is short lived, or brief support sessions via a support app. The argument falls down for enterprise owned devices because why not just install everything you'd ever need--but for employee owned devices they can still enroll into an MDM, and we wouldn't want every single app available to be there. An app clip could be provisioned as eligible for that user / device and only there on-demand. FB11723876 - App Store Connect / App Clips: Add support to Unlisted and Custom Apps the ability to work with an App Clip (Oct 2022) Similar to https://developer.apple.com/forums/thread/832043 which was asking for just unlisted.

Renewing this request across another release cycle. App Clips remain unsupported on visionOS in 27 (Xcode 27 still can't create a visionOS App Clip target; the App Clips entry now showing in visionOS 27 Siri settings is a known issue per the beta release notes, FB178269460 — not the feature shipping). Background: FB13348462 (filed Nov 2023) Sep '24 thread (https://developer.apple.com/forums/thread/763818): an Apple engineer noted the request and invited more enhancement reports; a second developer added it would be a game-changer for teasing Vision Pro content. Why it matters: on iOS, App Clips are how we distribute native-quality AR/RealityKit experiences with the frictionlessness of a link — no full-app install. It's a core revenue driver. Our platform already runs the same experiences on Vision Pro, so App Clip support is the one missing piece. We've deferred multiple Vision Pro commercial projects (marketing activations, location-based and cultural-heritage installs) specifically because a visitor can't tap a code and drop into a spatial experience without installing a full app. Install-free entry is arguably more important on visionOS than iOS — walk-up headset experiences depend on it. Request: prioritize opening App Clips (or an equivalent link/code-triggered ephemeral launch) to third-party developers on visionOS. We've shipped this exact pattern on iOS at scale and would gladly act as a design partner / beta tester. Anyone else needing this: please file an enhancement report and paste the number here, per Apple's request in the original thread. Thank you!

I'd like to know if there are any official, out-of-the-box tools available for handwriting and PaperKit that can help lower the input barrier for older adults and users with disabilities.

I have a Siri/widget-oriented app that would benefit from some sort of watchOS presence and I am trying to figure out the best approach. Can you help me understand the current options available? Initially I thought there was a kind of watchOS app that depended on an iPhone for nearly everything, but I am not clear if that approach has been deprecated. My app uses CloudKit for storage and is intended to be friendly to multiple devices, so theoretically the watch could stand on its own but in terms of staying closely in sync with the phone I am not clear that is the best approach. Further, it would seem to me better for Siri requests on the watch to directly update the phone if that were possible. My app heavily uses AppIntents, currently within the iPhone target. I am unclear if using an AppIntent extension would be a good path. I have found limited information about these extensions. I did an experiment with AppIntents in a watchOS app and had a lot of trouble getting the watch to recognize my shortcut phrases (or even to show the shortcuts in the watch Shortcuts app). With all of this in mind, can you offer me some recommendations about architecting a watch-friendly AppIntents approach.

I enabled Developer Mode on my watch but seemed to experience significant battery drain, so I tried to disable it (filed a feedback for the drain). But even after turning off dev mode on the watch and unpairing the watch from Xcode devices, I get prompted about trusting my computer. Is that expected behavior? I don’t remember it before turning on dev mode.