Posts under App & System Services topic

Post

Replies

Boosts

Views

Activity

StoreKit 2 returns USA/USD in TestFlight but DEU/EUR in local Release build on the same device
Hi everyone, We are currently preparing the release of our Flutter-based iOS application and are experiencing an unusual StoreKit 2 storefront issue that only occurs when the app is installed through TestFlight. The problem When our application is installed through TestFlight, StoreKit 2 consistently returns the United States storefront (USA), and all six auto-renewable subscription products are displayed with USD prices. However, both the regular Apple Account and the Sandbox Apple Account are configured for Germany. We have verified the following: All six subscription products are correctly configured in App Store Connect with EUR prices for Germany. The subscriptions are available in Germany, Austria, and Switzerland. We created a completely new Sandbox tester with Germany selected during account creation, using an email address that had never previously been used for sandbox testing. The issue occurs on two different physical devices (iPhone and iPad). No local StoreKit configuration file is used. Our application does not override the storefront, modify localized prices, or contain any hardcoded USD fallback. Controlled comparison We performed additional tests using the same application code on the same iPhone. The results were: Installation method Storefront Currency Local Debug build via Xcode/Flutter DEU EUR Local development-signed Release build via Flutter DEU EUR TestFlight Release build USA USD The locally installed Release build successfully retrieves all six subscription products with their correct German prices. For example, StoreKit returns the following values for one of our subscriptions: Local Release build: Storefront.current.countryCode = DEU Product currencyCode = EUR Product.displayPrice = 6,99 € TestFlight build: Storefront.current.countryCode = USA Product currencyCode = USD Both builds use the same StoreKit 2 integration and product identifiers. Technical environment Framework: Flutter StoreKit integration: StoreKit 2 Flutter plugin: in_app_purchase_storekit 0.4.11+2 Devices: Physical iPhone and iPad iOS/iPadOS: 26.6.2 Subscription products: Six auto-renewable subscriptions Expected storefront: Germany (DEU) Actual TestFlight storefront: United States (USA) We have traced the storefront country code directly to StoreKit 2’s Storefront.current.countryCode and the localized prices to the product information returned by Product.products(for:). There is no application-level storefront override or price conversion. Questions Why would StoreKit 2 return a different storefront in TestFlight compared with a locally installed development-signed Release build on the same physical device? Could TestFlight use a different sandbox storefront or Apple Account context than a locally installed build? Is there a recommended way to diagnose or reset the storefront association used by TestFlight? Has anyone experienced similar behavior where TestFlight consistently returns USA despite using a German Apple Account and newly created German sandbox testers? We have already contacted Apple Developer Support and followed their recommendation to create a completely new German sandbox tester, but the issue persists. Any guidance from Apple engineers or developers who have encountered similar behavior would be greatly appreciated. Thank you!
4
0
131
3d
StoreKit 2 returns USA/USD in TestFlight but DEU/EUR in local Release build on the same device
Hi everyone, We are currently preparing the release of our Flutter-based iOS application and are experiencing an unusual StoreKit 2 storefront issue that only occurs when the app is installed through TestFlight. The problem When our application is installed through TestFlight, StoreKit 2 consistently returns the United States storefront (USA), and all six auto-renewable subscription products are displayed with USD prices. However, both the regular Apple Account and the Sandbox Apple Account are configured for Germany. We have verified the following: All six subscription products are correctly configured in App Store Connect with EUR prices for Germany. The subscriptions are available in Germany, Austria, and Switzerland. We created a completely new Sandbox tester with Germany selected during account creation, using an email address that had never previously been used for sandbox testing. The issue occurs on two different physical devices (iPhone and iPad). No local StoreKit configuration file is used. Our application does not override the storefront, modify localized prices, or contain any hardcoded USD fallback. Controlled comparison We performed additional tests using the same application code on the same iPhone. The results were: Installation method Storefront Currency Local Debug build via Xcode/Flutter DEU EUR Local development-signed Release build via Flutter DEU EUR TestFlight Release build USA USD The locally installed Release build successfully retrieves all six subscription products with their correct German prices. For example, StoreKit returns the following values for one of our subscriptions: Local Release build: Storefront.current.countryCode = DEU Product currencyCode = EUR Product.displayPrice = 6,99 € TestFlight build: Storefront.current.countryCode = USA Product currencyCode = USD Both builds use the same StoreKit 2 integration and product identifiers. Technical environment Framework: Flutter StoreKit integration: StoreKit 2 Flutter plugin: in_app_purchase_storekit 0.4.11+2 Devices: Physical iPhone and iPad iOS/iPadOS: 26.6.2 Subscription products: Six auto-renewable subscriptions Expected storefront: Germany (DEU) Actual TestFlight storefront: United States (USA) We have traced the storefront country code directly to StoreKit 2’s Storefront.current.countryCode and the localized prices to the product information returned by Product.products(for:). There is no application-level storefront override or price conversion. Questions Why would StoreKit 2 return a different storefront in TestFlight compared with a locally installed development-signed Release build on the same physical device? Could TestFlight use a different sandbox storefront or Apple Account context than a locally installed build? Is there a recommended way to diagnose or reset the storefront association used by TestFlight? Has anyone experienced similar behavior where TestFlight consistently returns USA despite using a German Apple Account and newly created German sandbox testers? We have already contacted Apple Developer Support and followed their recommendation to create a completely new German sandbox tester, but the issue persists. Any guidance from Apple engineers or developers who have encountered similar behavior would be greatly appreciated. Thank you!
1
0
73
3d
TestFlight: StoreKit 2 product metadata shows USD 0.99 and no trial while the purchase sheet reports the configured offer
We are investigating a discrepancy between StoreKit 2 product metadata and the Apple purchase confirmation sheet in an iPad app distributed through internal TestFlight. The app offers one auto-renewable monthly subscription, configured for China mainland at CNY 6.80/month with a two-week introductory free trial. We would appreciate guidance on targeted diagnostics, without assuming that the cause is an Apple platform defect. Observed product metadata: build 1.0 (4) On an iPad (A16) running iPadOS 27.0.1, we independently verified the installed build and captured these public diagnostic fields during one product-loading invocation: Storefront.current.countryCode = CHN Product.priceFormatStyle.currencyCode = USD Product.price = 0.99 Product.displayPrice = US$0.99 Product.subscription.introductoryOffer = nil Product.subscription.isEligibleForIntroOffer = trueThe product and subscription-group identifiers matched the configured identifiers. Product metadata and Storefront.current were read sequentially with asynchronous calls, so this is not an atomic StoreKit snapshot. The currency and offer fields above are logged values, rather than an inference from the custom UI. For this build and product, the tester reported that the Apple system purchase sheet displayed a two-week free trial followed by CNY 6.80/month. We did not capture a screenshot of that system sheet, and no successful purchase or charge is being claimed. Subsequent replacement product: build 1.0 (5) The developer subsequently deleted the original product and created a replacement in the same subscription group. We saved and refreshed App Store Connect to check the replacement's China-mainland availability, CNY 6.80 monthly price, and two-week free-trial offer. Build 1.0 (5) uses the replacement identifier and is available in the existing internal TestFlight group. The tester confirmed installing build 5 and supplied an App screenshot showing US$0.99/month without the trial overview. The screenshot itself does not contain the build number; that attribution relies on the installation report. We have not yet captured fresh raw Product fields for this replacement. The tester also reports that its system purchase sheet is normal, but has not supplied its exact current wording or a screenshot. We therefore keep this evidence separate from the build 4 log values. Changing the ordinary Apple account under Media & Purchases did not change the reported App display. This was not a dedicated Sandbox Apple Account comparison. We have not established the replacement product's propagation state or the platform root cause. Relevant implementation path The following condensed excerpts show the production path, not a standalone reproduction project. Validation, state handling, and transaction verification are omitted here: // Product loading: let values = try await Product.products(for: [id]) guard values.count == 1, let product = values.first, product.id == id else { throw SubscriptionClientError.invalidProduct } products[id] = product // The UI model copies product.displayPrice directly. // Later, in the purchase method: guard let product = products[productID] else { throw SubscriptionClientError.unavailable } return try resolvePurchase(try await product.purchase(confirmIn: scene))Within a single completed load, the UI fields and cached purchase Product come from the same result and configured identifier. We do not convert the display price to USD or configure a separate CNY price for the system sheet. The trial overview requires an eligible two-week free-trial offer in the product data. Audited distribution artifacts did not contain a local StoreKit testing configuration or price fixture. What diagnostics would help distinguish product-metadata/storefront behavior from application state handling? Is a dedicated Sandbox-account storefront comparison the appropriate next control? Are there documented refresh requirements or known TestFlight issues relevant to this discrepancy? The existing build already logs product identifiers, raw price, currency, offer structure, and eligibility, so we can collect a targeted replacement-product observation if useful.
3
0
101
3d
MapKit route animation exported to MP4: permitted use and appropriate Apple contact
Hello, I am Rabia, publisher of RotaTakip, a pre-launch iOS outdoor GPS app being developed with my son. We are evaluating Apple Maps for a user-initiated route-video feature and would appreciate a reference to official guidance or the appropriate Apple contact before enabling it. Proposed use: A user selects their own recorded GPS route and creates a short animated recap over an Apple map. The app saves an MP4 to Photos, and the user may share it on social media or play it on non-Apple devices. Rendering would happen on the user's device using public APIs. Required Apple and third-party attribution would remain visible. We would not extract raw tiles, scrape map data, build a map database, or perform bulk/server-side rendering. The app is planned as a paid, one-time-purchase GPS app. The map would be a main visual element in the exported recap. Video export remains disabled pending clarification. We are considering two approaches separately: MKMapSnapshotter images with our own route overlays, potentially a sequence of camera views, encoded with AVFoundation. A user-initiated ReplayKit recording of an animated MKMapView, with the required system consent and recording indication. I have reviewed Attachment 6 of the Apple Developer Program License Agreement, especially sections 2.1-2.5, and the snapshot documentation. I found guidance on static snapshots, but not a clear explanation of this MP4 export and end-user sharing scenario. Questions: Is either approach a supported, permitted use under the standard agreement and documentation? Is there an official document addressing it? Does the answer differ for standard versus satellite/hybrid or 3D views, or for a fixed map with an animated route versus a moving camera? How should attribution and the Legal link be handled in a non-interactive exported video, and are there specific limits on intermediate-frame retention or rendering frequency? If separate permission or a different implementation is required, which Apple team or support category should we contact? We have submitted a Rights and Permissions inquiry and would appreciate guidance on the correct channel for this MapKit-specific question. Apps such as ReRun advertise route-video export, and Huawei Health offers dynamic route videos. We do not know the map source used in every exported video or whether these apps have separate agreements, so we are not assuming their availability grants permission for our implementation. We are looking for the documented path available to other developers. Thank you for any official references or routing guidance. Rabia / RotaTakip
0
0
35
3d
CloudKit sync fails in macOS TestFlight build – sandbox denies com.apple.cloudd
I have a macOS SwiftUI app using SwiftData with CloudKit synchronization. Bundle ID: com.mjsapps.PhrasePin CloudKit container: iCloud.com.mjsapps.PhrasePin CloudKit synchronization works when running the app from Xcode using the Development environment. However, synchronization does not work in the TestFlight / Production build. The Production schema has been deployed successfully. The TestFlight build has the expected entitlements, including: com.apple.developer.icloud-container-environment = Production com.apple.developer.icloud-container-identifiers = iCloud.com.mjsapps.PhrasePin com.apple.developer.icloud-services = CloudKit com.apple.security.app-sandbox = true com.apple.security.network.client = true The TestFlight build is signed as: Authority=TestFlight Beta Distribution Identifier=com.mjsapps.PhrasePin TeamIdentifier=8D6TX86CQK CloudKit/Core Data logging shows that the app is trying to use: container=iCloud.com.mjsapps.PhrasePin:Production but synchronization fails with: CKErrorDomain Code=6 Error connecting to CloudKit daemon NSCocoaErrorDomain Code=4099 The macOS sandbox log shows: Sandbox: PhrasePin(...) deny(1) mach-lookup com.apple.cloudd As a result, no com.apple.coredata.cloudkit.zone is created in the Production private database and no SwiftData records are synchronized. The problem has been reproduced on: macOS Sequoia 15.7.7 macOS Sequoia 15.7.9 The same app works with CloudKit in Development when run from Xcode. I have already submitted a Feedback Assistant report, but have not received a response. Has anyone seen this behavior with SwiftData + CloudKit in a sandboxed macOS TestFlight build? Is there an additional entitlement or provisioning requirement needed for access to com.apple.cloudd in Production?
1
0
56
3d
Cellular data unavailable while an underwater-depth WKExtendedRuntimeSession is running (Wi-Fi unaffected)
Our freediving app for Apple Watch Ultra declares WKBackgroundModes "underwater-depth" and "workout-processing". During a session it runs an HKWorkoutSession, enables Water Lock and starts a WKExtendedRuntimeSession. While the diver is at the surface it sends small URLSession uploads: a live position share for the people watching from shore. On an Apple Watch Ultra with its own cellular plan and the paired iPhone switched off, every URLSession request fails while the underwater-depth runtime session is running. We tested each piece on its own, checking connectivity every 10 seconds and logging URLSessionTaskTransactionMetrics.isCellular and NWPathMonitor. Cellular only: with nothing running, 26 of 27 requests succeeded over cellular. Within seconds of the underwater-depth runtime session starting, requests time out (-1001) and NWPathMonitor reports no available interface. With the HKWorkoutSession and Water Lock running but the runtime session ended, 8 of 8 succeeded over cellular. Cellular returns within about 5 seconds of the runtime session ending. Wi-Fi only (iPhone switched off, known Wi-Fi): 34 of 34 requests succeeded over the watch's own Wi-Fi in every stage, including while the underwater-depth runtime session was running. Another shipping dive app loses cellular the same way when its dive session starts, so it does not appear to be specific to our app. Steps to reproduce: on an Apple Watch Ultra with an active cellular plan, switch the paired iPhone off and move away from any known Wi-Fi network. In an app with the underwater-depth background mode, start a WKExtendedRuntimeSession, then make a URLSession request. It times out while the session runs, and succeeds again within seconds of the session ending. Our questions: Q1. Is cellular data intentionally unavailable to apps while an underwater-depth session runs, while Wi-Fi remains available? Q2. Is there a supported way to send a small amount of data over cellular during an underwater-depth session (for example while the diver is at the surface) without ending the session? Q3. If neither, we have filed FB25362581 asking for cellular to be allowed at the surface, as Wi-Fi already is. We have a focused test project (about 140 lines) that reproduces it and can share it with DTS. watchOS 27.0.1, Apple Watch Ultra 2, Xcode 27.1.
1
0
97
3d
App Review device never reaches our domain (NSURLErrorDomain -1001, no requests in server or Cloudflare logs)
Hello, Our iOS app has been rejected four times under Guideline 2.1(a) because sign-in fails on the review iPad. The latest rejection showed NSURLErrorDomain error -1001 (the request timed out) on an iPad Air 11-inch (M3) with iPadOS 27.0, on November 5, 2026, at about 11:54 UTC. The same happened on October 16, 2026. Setup: API: https://wp.pavilion.az, HTTPS on port 443, fixed DNS name DNS and proxy on Cloudflare (IPv4 and IPv6), publicly trusted certificate The app uses URLSession, with no custom certificate checks and no proxy settings What we checked: Neither our origin server nor Cloudflare logged any request from the review device on either day. Other clients were served normally during the same minutes. The domain resolves normally from many public DNS resolvers in the United States and Europe, over IPv4 and IPv6. The app signs in in under one second on an iPad simulator in a data center in Los Angeles, and on our own devices through TestFlight. This looks similar to https://developer.apple.com/forums/thread/773444, where a Cloudflare-hosted domain resolved to a wrong address inside Apple's network. Could someone from Apple check how wp.pavilion.az resolves, and whether it is reachable, from the App Review network? We have resubmitted a build that adds a short network check to the error message (the DNS result and which connection step fails), but each review cycle takes many days. Thank you.
5
0
325
3d
Egress addresses of the URL filter OHTTP relay
Hello, I am wondering about the egress addresses of the Oblivious HTTP relay that Apple runs for Network Extension URL filters. I am building an iOS app that uses NEURLFilterManager. The app builds a Bloom filter from the block lists a user picks. The system only asks our server about a site when that filter has a hit. Each lookup is encrypted with keyword PIR and carries a Privacy Pass token instead of anything tied to the user. It reaches our server through your relay, which strips the device's address. We run our own PIR server, Privacy Pass issuer and OHTTP gateway instead of a hosted service. The gateway is the one part of the setup that should only ever hear from your relay. Since every real lookup comes through the relay, I would really like to drop all other traffic to it at the firewall. Right now I can't do that. I also can't rate limit by address because every legitimate request shares the relay's addresses. As a result the gateway just has to stay open to everyone and rely on global limits, which is a far cry from what I'd want for a service that only one client is meant to reach. I have three questions about this. 1) Are the relay's egress address ranges published somewhere, or can they be shared with developers who have been onboarded? 2) If they are shared, how would we find out when they change and how much notice there is? 3) If the addresses can't be shared, is there another way to tell that a request came from the relay, such as a header or a client certificate? Please let me know if any of this is unclear or if there is a better place to ask. Thank you in advance, Alexander
1
0
89
3d
macos 27 - unexpected/new errno from BSD socket connect() when pending connections exceed backlog
Please consider the trivial C program attached to this thread. The code creates a socket() and listen()s for connections, but (intentionally) doesn't accept() the connections. The listen() is done using a small backlog (of 1). This test then does several connect() attempts and expects that the connect() attempts will accumulate in the pending queue and once the queue exceeds the backlog limit, then as specified in man listen: The backlog parameter defines the maximum length for the queue of pending connections. If a connection request arrives with the queue full, the client may receive an error with an indication of ECONNREFUSED. then the connect() attempt will receive a ECONNREFUSED. However, in macos 27, such a connect() attempt leads to ECONNRESET (Connection reset by peer) instead of ECONNREFUSED. Is this expected? Experiments show that prior versions of macos were returning a ETIMEDOUT for such connect() attempts. If this new error is expected from connect() when the backlog limit has exceeded, should it be specified in the man listen documentation? Rename the attached main.c.txt to main.c. Compiling the attached program on macos 27, using clang main.c and then running ./a.out results in: ----------------------- MacOS version: 27.0.1 Kernel version: Darwin Kernel Version 27.0.0: Tue Aug 11 21:02:16 PDT 2026; root:xnu-13432.1.9~1/RELEASE_ARM64_T8112 ----------------------- started server at at 127.0.0.1:52753 with a backlog of 1 connect() attempt 1 - connected connect() attempt 2 - connected connect() attempt 3 - connected connect() attempt 4 - connected connect() attempt 5 - failed to connect() - Connection reset by peer <-- FAILURE: Unexpected error code, expected either ETIMEDOUT or ECONNREFUSED but got 54 connect() attempt 6 - connected connect() attempt 7 - connected connect() attempt 8 - connected connect() attempt 9 - failed to connect() - Connection reset by peer <-- FAILURE: Unexpected error code, expected either ETIMEDOUT or ECONNREFUSED but got 54 connect() attempt 10 - failed to connect() - Connection reset by peer <-- FAILURE: Unexpected error code, expected either ETIMEDOUT or ECONNREFUSED but got 54 connect() attempt 11 - failed to connect() - Connection reset by peer <-- FAILURE: Unexpected error code, expected either ETIMEDOUT or ECONNREFUSED but got 54 On a related note, it's unclear why several of the connect() attempts succeeded instead of just 1 of them succeeding. On prior versions of macos, the output of the same program is: ----------------------- MacOS version: 26.7.1 Kernel version: Darwin Kernel Version 25.6.0: Tue Aug 18 17:49:13 PDT 2026; root:xnu-12377.161.15.700.19~2/RELEASE_ARM64_T6000 ----------------------- started server at at 127.0.0.1:52451 with a backlog of 1 connect() attempt 1 - connected connect() attempt 2 - failed to connect() - Operation timed out connect() attempt 3 - failed to connect() - Operation timed out connect() attempt 4 - failed to connect() - Operation timed out connect() attempt 5 - failed to connect() - Operation timed out connect() attempt 6 - failed to connect() - Operation timed out connect() attempt 7 - failed to connect() - Operation timed out connect() attempt 8 - failed to connect() - Operation timed out connect() attempt 9 - failed to connect() - Operation timed out connect() attempt 10 - failed to connect() - Operation timed out connect() attempt 11 - failed to connect() - Operation timed out and this output is much more understandable and deterministic. main.c.txt
3
0
380
3d
Instructions for debugging recent macos kernel versions?
Is there any recent and a bit authoritative documentation which explains how to debug recent versions of macos kernel? I have found some blog posts from other users but those are either outdated or don't work for some other reason. I am guessing kernel debugging is pretty common for developers working on macos itself, so I'm hoping someone in this forum would have some working instructions for that.
20
1
1.6k
3d
AccessoryAccess for a Developer ID virtualization app: can it replace a root daemon for USB storage devices?
I build AVM, the Accessible Virtual Machine, a free, open source Mac app that runs Windows 11 for ARM in QEMU. It's built for blind people who use VoiceOver on the Mac and a screen reader in Windows. It's on GitHub at https://github.com/allisonfm85/accessible-virtual-machine. AVM ships with Developer ID, it's notarized, and it isn't sandboxed. QEMU runs as a child process, signed by the same team, and does the USB work itself through usbredir and libusb. I asked DTS about this (case 23107052), and Quinn pointed me to thread 851767. Today AVM captures USB devices from a root daemon registered with SMAppService. That works for braille displays and microphones. It fails for USB flash drives. Opening interface 0 returns 0xe00002c9. I measured why with a small IOUSBHost tool: Run with sudo from a terminal that has Removable Volumes: works. Same command with Removable Volumes turned off: fails with 0xe00002c9. Run as a launchd daemon in the system domain: fails. Full Disk Access makes no difference. So the block is the Removable Volumes permission, and a daemon has no responsible app to carry it. Granting it to AVM doesn't help the daemon. Thread 851767 shows a flash drive working through AccessoryAccess and IOUSBHostDevice, with interfaces opened through IOUSBLib. That looks like the path I should be on. My questions: Is the Claim USB Accessory capability (com.apple.developer.accessory-access.usb) available to Developer ID apps outside the Mac App Store? Does it require the App Sandbox? Does the user's AccessoryAccess consent cover a USB storage device's interfaces? In other words, would it get past the Removable Volumes check that stops my daemon? Can AVM pass createXPCRepresentation to QEMU, a non-sandboxed child process from the same team, and have QEMU open the accessory there? libusb opens interfaces through IOUSBLib. Given FB25324561, is it reasonable to ship on that path for now? If AccessoryAccess isn't available to Developer ID apps, I'd still welcome guidance on a supported way, such as com.apple.vm.device-access. I'm happy to share my sample project or logs. Thank you, Allison Meloy
1
0
121
3d
Foundation reports false for encryption on two encrypted external APFS volumes
We request clarification of a Foundation API discrepancy from existing read-only diagnostics. Environment: the user has personally run sw_vers on the currently running Mac and confirmed ProductName: macOS; ProductVersion: 27.0.1; BuildVersion: 26A434. This is the currently confirmed system version. The reviewed records do not establish an unambiguous temporal link between that confirmation and the APFS/Foundation measurements on 15 November 2026; we therefore do not assert that it proves the OS version used for those measurements. Earlier macOS 26.6.2 (25G83) records are historical and are not presented as the current system. Observed volumes: External APFS Volume A and External APFS Volume B, both external APFS volumes connected over USB. For BOTH volumes, the recorded diskutil results are: Encryption=true; EncryptionThisVolumeProper=true; CryptoMigrationOn=false; GlobalPermissionsEnabled=true. Both were mounted and unlocked after completed in-place APFS encryption. For BOTH volumes, direct Foundation queries at the volume root return: NSURLVolumeUUIDStringKey: the correct UUID for the respective volume (omitted here for privacy); NSURLVolumeURLKey: the same volume-root URL as queried; NSURLVolumeIsEncryptedKey: present, explicit false (__NSCFBoolean, description 0). The canonical mount path and diskutil volume identity match. This is not an inquiry against a parent volume, a missing key converted to false, or an inferred mapping based only on a display name. Minimal read-only observation procedure, describing the existing successful queries (not rerun for this request): Select the already mounted APFS volume root and verify its UUID against diskutil. Construct a fresh NSURL using fileURLWithPath for that root. Query resourceValuesForKeys:error: for NSURLVolumeUUIDStringKey, NSURLVolumeURLKey and NSURLVolumeIsEncryptedKey. Compare the returned UUID/root URL and explicit encryption Boolean with the recorded diskutil fields. The successful queries used Foundation through JavaScript for Automation's Objective-C bridge, in separate helper processes. An equivalent full Swift application runtime result has not been established. A separate failed JXA enumeration attempt is excluded from the evidence. We understand URL resource values may be cached; caching has not been established as the cause. Expected: an encryption indication consistent with the completed APFS encryption, or documented semantics explaining why these indicators differ. Actual: explicit false on both volumes. Questions: Are there documented limitations or known issues for this property on external, mounted and unlocked APFS volumes encrypted in place? What does false mean when the recorded diskutil encryption fields are positive? Is any additional read-only evidence necessary to interpret it? Which supported public read-only API and validation procedure should an application use to establish completed APFS volume encryption without weakening its policy? Could the observed behavior be affected by accessing NSURL resource values through the JavaScript for Automation Objective-C bridge rather than directly from a native Swift application? We are requesting interpretation of existing evidence. No further encryption, lock/unlock experiment, drive modification or application build was performed for this inquiry. No credentials, private paths or customer data are included. Thank you.
1
0
131
3d
Is it possible to run an iPadOS virtual machine inside an iOS app?
Hi everyone, I am researching the technical feasibility of a project named Kairavox. The goal is to run a genuine, unmodified iPadOS installation as a guest VM inside a standalone app on an ordinary, unjailbroken iPhone. Our first research target is iPadOS 27.2.1 on an iPad 9th-generation (A13) guest. This is not an iPadOS-style interface or a remote desktop. We want to boot and run actual iPadOS in the guest. Proposed approach Apple’s public virtualization and hypervisor documentation appears to cover Mac hosts, not iPhone hosts. We are therefore investigating a native software AArch64 interpreter inside a normal iOS app. JIT is not assumed; we would consider it only if Apple confirms an applicable, supported development path. We are considering personal development signing and sideloading tools such as AltStore or SideStore. App Store distribution is not a project requirement. We understand that these tools do not themselves grant Apple entitlements, and that free Personal Team provisioning has limits. We are also investigating Apple’s documented Increased Memory Limit and Extended Virtual Addressing entitlements. We do not know whether either is available for this app and signing route, or what memory budget would actually be available to guest RAM. Projects such as Henge and GetMoreRam are useful points of comparison, but we understand that they do not establish an Apple-supported route for an iPadOS guest. We will not rely on private APIs, unauthorized entitlements, Secure Boot bypasses, or firmware patches. Questions Is there a documented iOS API or entitlement that lets a third-party iPhone app host a virtual CPU or VM? If not, is a native software interpreter a supported way for an app to interpret AArch64 guest instructions? Does Apple permit that interpreter to run an unmodified iPadOS guest in a sideloaded development app? Are there specific code-execution or licensing restrictions we should review? Apple documents virtual hardware identities and restore workflows for macOS VMs. Is there an analogous supported guest identity and image-personalization process for iPadOS, including an iPadOS 27.2.1 guest? Does Apple document a virtual SEP model, or another supported way to meet SEP-dependent boot, storage, and platform-service requirements for an iPadOS guest? Development Signing & JIT: For development on our own stock iPhone, can free Personal Team signing support this kind of application? Are there documented JIT permissions available through this signing route? If not, does JIT require a different signing arrangement or entitlement? Can an independent developer request the Increased Memory Limit entitlement for an iOS app through a documented process? How should we distinguish that process from Extended Virtual Addressing and the development-only Increased Debugging Memory Limit entitlement? If these questions are better directed to Developer Technical Support or another Apple team, please point us to the appropriate channel. We are looking for a documented, authorized path and will not assume one exists. Thanks for any guidance.
1
0
231
3d
Can a third-party iOS app automatically launch in the foreground at a scheduled time without user interaction?
Hello, I would like to clarify whether iOS provides any supported public API for automatically bringing a third-party app to the foreground at a scheduled time. The requirements are: The user has explicitly opted in to this behavior in advance. The app may be in the background, suspended, or not running. At a specified time, the app should automatically appear in the foreground without the user tapping a notification or performing any other action. The app should then automatically display and play media. Ideally, this should also work when the iPhone is locked. I understand that iOS has restrictions on background execution and that frameworks such as AlarmKit provide system-managed alarm experiences. My questions are: Is there any supported public API, entitlement, or combination of frameworks that enables this behavior? Can AlarmKit or another framework automatically launch a third-party app into the foreground without user interaction? If this is not supported, is it an intentional platform restriction? I am specifically asking about automatic foreground activation, not simply delivering a notification or running background tasks. Thank you for your guidance.
1
0
48
3d
Supported App Sandbox metadata access through an inherited file descriptor, without reopening the object
We are evaluating a macOS design before implementation. This is a platform-support question, not a report of an observed runtime failure. No actual controller executable, helper executable or deployment configuration has been selected or qualified. Our objective is to let a small, fixed-purpose helper examine an already-open object’s identity and access control list (ACL) metadata while preserving the original object reference and ownership. Proposed configuration A trusted controller would launch one native C helper using an explicit executable target and posix_spawn. The controller would need to qualify for the documented nonsandboxed-parent case, without a conflicting inherited sandbox. We do not assume that an absent entitlement alone establishes this. The helper would be the main executable of its own signed application bundle, using its own ordinary App Sandbox rather than inheriting the controller’s sandbox. Its proposed additional filesystem permission would be com.apple.security.temporary-exception.files.absolute-path.read-only, containing exactly two fixed directory entries beneath a user’s development workspace, outside the helper’s container. The literal private paths are omitted. The controller would already own a read-only file descriptor for one regular file or directory within those trees. It would retain its original reference and pass a known duplicate referring to the same open object to the helper. The helper would perform one metadata observation. The proposed operations are fstat for object identity and fgetattrlist requesting ATTR_CMN_RETURNED_ATTRS and ATTR_CMN_EXTENDED_SECURITY, with FSOPT_REPORT_FULLSIZE and without FSOPT_PACK_INVAL_ATTRS. Required boundaries The helper must use only the inherited descriptor for the subject observation. The design does not permit: Reopening or resolving the subject through a pathname, bookmark or URL. Substituting a copied file or another object reference. Reading file contents, enumerating directories, changing permissions, or modifying shared descriptor flags or file offsets. Expanding the exception to an ancestor, home directory or broader workspace. Disabling an existing sandbox or using private interfaces to bypass restrictions. Parent-side traversal and identity checks remain separate responsibilities. Strict ancestor directories are not additional helper ACL subjects. We understand that a read-only directory exception and ordinary sandbox/container capabilities may permit more than the helper’s intended metadata operations. Metadata-only behaviour would be a reviewed-code obligation; we are not asking App Sandbox to enforce an exact metadata-only operation filter. Questions Supported launch and activation: Under what documented parent-context, signing, bundle, container and launch conditions can this helper establish its own ordinary App Sandbox? What supported mechanism or guarantee establishes that the sandbox is effective before the subject metadata operation? Required metadata permissions: Does the proposed read-only exception support fstat and the specified extended-security fgetattrlist request through an inherited read-only descriptor, for both regular files and directories? Please distinguish descriptor survival from permission to perform these operations, including any additional access-control conditions. Scope, identity and lifetime: What documented behaviour applies to descendant coverage, aliases, hard links, renames or namespace changes after the descriptor was opened? Please distinguish the lifetime of the inherited object reference from the lifetime of the static directory permission. Our design would refuse uncertainty rather than reopen, rebind or widen access. Evidence and support boundary: Which public documentation, interfaces or authoritative guarantees support this exact composition, and which parts require separate empirical qualification? Please identify applicable macOS versions and restrictions. Distinguish platform support from any distribution or App Store review requirements. If these requirements cannot be combined through supported interfaces, please identify the incompatible requirement. An approach requiring broader access, pathname reopening, a replacement object or a different handoff architecture would be a design change requiring separate review, not a solution within the stated constraints. Permission failures, unsupported requests and incomplete metadata would remain unavailable results. They would not be interpreted as proof that an ACL is absent. Complete ACL-absence interpretation and native resource bounds remain separate qualification questions. Apple material already reviewed Resolving App Sandbox Inheritance Problems App Sandbox Temporary Exception Entitlements Accessing files from the macOS App Sandbox
1
0
237
3d
macOS 26.x App Sandbox: supported disk-image attachment and descriptor-based unmount
On macOS 26.x, is there a public, supported way for an App Sandbox application with com.apple.security.virtualization to attach a new disk-image file held in its own container and mount its APFS filesystem within that container, without root, privileged or unsandboxed helpers, private/temporary exception entitlements, Full Disk Access, or weakening App Sandbox? We distinguish attaching the image from mounting an already attached virtual device. DTS threads 655767, 780965 and 775835 discuss these separately. Which supported API or tool and entitlements apply on 26.x, if such a path exists? If attachment is supported, what ownership and sandbox checks apply to a later normal funmount(fd, 0) using an O_EVTONLY descriptor for that exact mount's root? Is this combination supported, including when another actor has already unmounted it? If not, what supported alternative preserves the same restricted profile and avoids force or whole-disk unmount?
0
0
83
3d
NSE Filtering for encrypted incoming calls: what technical details should we provide?
We’re preparing the first iOS release of ANTINTWRK, an encrypted messenger with voice and video calls. Our push gateway sends a regular APNs alert for the encrypted event. On the receiving device, the Notification Service Extension fetches and decrypts the referenced event. In this delivery path, the gateway does not distinguish an encrypted call invitation from a message. When the extension identifies a ringing call, it uses CXProvider.reportNewIncomingVoIPPushPayload to hand it off to CallKit and suppresses the original alert to avoid a duplicate notification. Our Notification (NSE) Filtering request, submitted on October 25, 2026, still shows Submitted. Xcode cannot export the App Store build because the extension’s distribution profile lacks com.apple.developer.usernotifications.filtering. We have contacted Developer Support under Entitlements. We’re following Apple’s Sending End-to-End Encrypted VoIP Calls guidance. For this design, what technical details or test evidence should we provide so the capability review team can evaluate the request? Is there a recommended way to attach that material to the existing request? We can provide the request and support case IDs privately if needed.
0
0
135
4d
HKStatisticsCollectionQueryDescriptor intermittently returns no data for certain date ranges on iOS 27
We are seeing inconsistent results from HKStatisticsCollectionQueryDescriptor on iOS 27. Using the same quantity type, statistics options, anchor date, interval components, and predicate configuration, some date ranges return the expected statistics, while other ranges unexpectedly return empty results or buckets with no quantity. The affected ranges do contain HealthKit samples: HKSampleQueryDescriptor finds samples in the same date range. HKStatisticsQueryDescriptor returns the expected value when run separately for an affected bucket. HKStatisticsCollectionQueryDescriptor returns no quantity for that same bucket. Slightly expanding or shifting the date range may cause the collection query to return data again. A simplified version of the query looks like this: let datePredicate = HKQuery.predicateForSamples( withStart: startDate, end: endDate, options: .strictStartDate ) let descriptor = HKStatisticsCollectionQueryDescriptor( predicate: .quantitySample( type: quantityType, predicate: datePredicate ), options: .cumulativeSum, anchorDate: anchorDate, intervalComponents: DateComponents(day: 1) ) let collection = try await descriptor.result(for: healthStore) collection.enumerateStatistics(from: startDate, to: endDate) { statistics, _ in let quantity = statistics.sumQuantity() print(statistics.startDate, quantity as Any) } Expected behavior Every interval containing matching samples should return the corresponding statistics, regardless of the overall requested date range. Actual behavior Some date ranges produce missing or empty buckets even though matching samples exist and an individual HKStatisticsQueryDescriptor can calculate the expected value. Changing only the date range can make the data appear or disappear. The samples are visible to the app in the affected range, so this does not appear to be explained solely by iOS 27’s Limited History authorization. This behavior was not observed with the same query flow on earlier iOS versions. Is this a known regression in HKStatisticsCollectionQueryDescriptor on iOS 27, or has the expected date-range or predicate behavior changed?
4
3
1.1k
4d
CKKS zone deletions return success but stale 2019 key hierarchy persists; "Delete iCloud Data" not offered (FB25584356)
I filed FB25584356 for this and would appreciate any pointers. Setup: Mac mini on macOS 27.2.1 and an iPhone on iOS 27.2, same Apple Account, HSA2, Advanced Data Protection off. Octagon is healthy (otctl status = Ready, both devices trusted). Symptoms: AirDrop to my own iPhone fails when I pick the device (rapportd: "PairVerify server M2 failed: copy identity"), iPhone Mirroring ends with noCompatiblePhone, and various clients log CKErrorDomain 111 / 5009 "Keychain Sync Incomplete". What I see in CKKS: seven zones (AutoUnlock, LimitedPeersAllowed, Home, Manatee, ApplePay, Health, Engram) still hold a key hierarchy from August 2019. The only TLKShare was issued by a device that left the account years ago, so neither current device can unwrap the TLK ("No trusted TLKShares", CKKSErrorDomain 35). secd then does what I would expect: tlkmissing → "No other devices claim to have the TLK. Resetting zone..." → CKKSDeleteCKZoneOperation → local reset → zones recreated. The delete appears to succeed. With debug logging, cloudd shows status:200 and "RecordZone ... was successfully deleted from the server" for each zone. The next fetch returns the same 2019 records with an identical server change token. Over about 11 hours: 124 reset cycles, 869 zone deletions reported as successful, 182 consecutive AutoUnlock fetches with the same change token. When not throttled it runs roughly every 5 seconds; CloudKit eventually answers "Service Unavailable" (CKError 6/2009) with a ~59 minute retry-after, and all 23 zones are unusable in the meantime. ckksctl -v AutoUnlock reset-cloudkit behaves the same way. Reset path: Support article 120862 describes "Don't know passcode?" → "Forgot all passcodes?" → "More Options" → "Delete iCloud Data". With the Mac signed in but not yet trusted, "Don't know passcode?" only offered Cancel / Try Again Later, in the sign-in flow and in both System Settings follow-ups. After three wrong passcodes the alert had a single "Try Again Later" button, although cdpd logged "Creating recovery option: Reset". Questions: Is a client-side zone delete expected to be a no-op for these zones while the server reports success? Is there a supported way to reach performCKServerUnreadableDataRemoval / "Delete iCloud Data" when another trusted device exists? I am fine with losing the end-to-end encrypted data in those zones. Logs and a sysdiagnose are attached to the Feedback.
0
0
125
4d
StoreKit 2 returns USA/USD in TestFlight but DEU/EUR in local Release build on the same device
Hi everyone, We are currently preparing the release of our Flutter-based iOS application and are experiencing an unusual StoreKit 2 storefront issue that only occurs when the app is installed through TestFlight. The problem When our application is installed through TestFlight, StoreKit 2 consistently returns the United States storefront (USA), and all six auto-renewable subscription products are displayed with USD prices. However, both the regular Apple Account and the Sandbox Apple Account are configured for Germany. We have verified the following: All six subscription products are correctly configured in App Store Connect with EUR prices for Germany. The subscriptions are available in Germany, Austria, and Switzerland. We created a completely new Sandbox tester with Germany selected during account creation, using an email address that had never previously been used for sandbox testing. The issue occurs on two different physical devices (iPhone and iPad). No local StoreKit configuration file is used. Our application does not override the storefront, modify localized prices, or contain any hardcoded USD fallback. Controlled comparison We performed additional tests using the same application code on the same iPhone. The results were: Installation method Storefront Currency Local Debug build via Xcode/Flutter DEU EUR Local development-signed Release build via Flutter DEU EUR TestFlight Release build USA USD The locally installed Release build successfully retrieves all six subscription products with their correct German prices. For example, StoreKit returns the following values for one of our subscriptions: Local Release build: Storefront.current.countryCode = DEU Product currencyCode = EUR Product.displayPrice = 6,99 € TestFlight build: Storefront.current.countryCode = USA Product currencyCode = USD Both builds use the same StoreKit 2 integration and product identifiers. Technical environment Framework: Flutter StoreKit integration: StoreKit 2 Flutter plugin: in_app_purchase_storekit 0.4.11+2 Devices: Physical iPhone and iPad iOS/iPadOS: 26.6.2 Subscription products: Six auto-renewable subscriptions Expected storefront: Germany (DEU) Actual TestFlight storefront: United States (USA) We have traced the storefront country code directly to StoreKit 2’s Storefront.current.countryCode and the localized prices to the product information returned by Product.products(for:). There is no application-level storefront override or price conversion. Questions Why would StoreKit 2 return a different storefront in TestFlight compared with a locally installed development-signed Release build on the same physical device? Could TestFlight use a different sandbox storefront or Apple Account context than a locally installed build? Is there a recommended way to diagnose or reset the storefront association used by TestFlight? Has anyone experienced similar behavior where TestFlight consistently returns USA despite using a German Apple Account and newly created German sandbox testers? We have already contacted Apple Developer Support and followed their recommendation to create a completely new German sandbox tester, but the issue persists. Any guidance from Apple engineers or developers who have encountered similar behavior would be greatly appreciated. Thank you!
Replies
4
Boosts
0
Views
131
Activity
3d
StoreKit 2 returns USA/USD in TestFlight but DEU/EUR in local Release build on the same device
Hi everyone, We are currently preparing the release of our Flutter-based iOS application and are experiencing an unusual StoreKit 2 storefront issue that only occurs when the app is installed through TestFlight. The problem When our application is installed through TestFlight, StoreKit 2 consistently returns the United States storefront (USA), and all six auto-renewable subscription products are displayed with USD prices. However, both the regular Apple Account and the Sandbox Apple Account are configured for Germany. We have verified the following: All six subscription products are correctly configured in App Store Connect with EUR prices for Germany. The subscriptions are available in Germany, Austria, and Switzerland. We created a completely new Sandbox tester with Germany selected during account creation, using an email address that had never previously been used for sandbox testing. The issue occurs on two different physical devices (iPhone and iPad). No local StoreKit configuration file is used. Our application does not override the storefront, modify localized prices, or contain any hardcoded USD fallback. Controlled comparison We performed additional tests using the same application code on the same iPhone. The results were: Installation method Storefront Currency Local Debug build via Xcode/Flutter DEU EUR Local development-signed Release build via Flutter DEU EUR TestFlight Release build USA USD The locally installed Release build successfully retrieves all six subscription products with their correct German prices. For example, StoreKit returns the following values for one of our subscriptions: Local Release build: Storefront.current.countryCode = DEU Product currencyCode = EUR Product.displayPrice = 6,99 € TestFlight build: Storefront.current.countryCode = USA Product currencyCode = USD Both builds use the same StoreKit 2 integration and product identifiers. Technical environment Framework: Flutter StoreKit integration: StoreKit 2 Flutter plugin: in_app_purchase_storekit 0.4.11+2 Devices: Physical iPhone and iPad iOS/iPadOS: 26.6.2 Subscription products: Six auto-renewable subscriptions Expected storefront: Germany (DEU) Actual TestFlight storefront: United States (USA) We have traced the storefront country code directly to StoreKit 2’s Storefront.current.countryCode and the localized prices to the product information returned by Product.products(for:). There is no application-level storefront override or price conversion. Questions Why would StoreKit 2 return a different storefront in TestFlight compared with a locally installed development-signed Release build on the same physical device? Could TestFlight use a different sandbox storefront or Apple Account context than a locally installed build? Is there a recommended way to diagnose or reset the storefront association used by TestFlight? Has anyone experienced similar behavior where TestFlight consistently returns USA despite using a German Apple Account and newly created German sandbox testers? We have already contacted Apple Developer Support and followed their recommendation to create a completely new German sandbox tester, but the issue persists. Any guidance from Apple engineers or developers who have encountered similar behavior would be greatly appreciated. Thank you!
Replies
1
Boosts
0
Views
73
Activity
3d
TestFlight: StoreKit 2 product metadata shows USD 0.99 and no trial while the purchase sheet reports the configured offer
We are investigating a discrepancy between StoreKit 2 product metadata and the Apple purchase confirmation sheet in an iPad app distributed through internal TestFlight. The app offers one auto-renewable monthly subscription, configured for China mainland at CNY 6.80/month with a two-week introductory free trial. We would appreciate guidance on targeted diagnostics, without assuming that the cause is an Apple platform defect. Observed product metadata: build 1.0 (4) On an iPad (A16) running iPadOS 27.0.1, we independently verified the installed build and captured these public diagnostic fields during one product-loading invocation: Storefront.current.countryCode = CHN Product.priceFormatStyle.currencyCode = USD Product.price = 0.99 Product.displayPrice = US$0.99 Product.subscription.introductoryOffer = nil Product.subscription.isEligibleForIntroOffer = trueThe product and subscription-group identifiers matched the configured identifiers. Product metadata and Storefront.current were read sequentially with asynchronous calls, so this is not an atomic StoreKit snapshot. The currency and offer fields above are logged values, rather than an inference from the custom UI. For this build and product, the tester reported that the Apple system purchase sheet displayed a two-week free trial followed by CNY 6.80/month. We did not capture a screenshot of that system sheet, and no successful purchase or charge is being claimed. Subsequent replacement product: build 1.0 (5) The developer subsequently deleted the original product and created a replacement in the same subscription group. We saved and refreshed App Store Connect to check the replacement's China-mainland availability, CNY 6.80 monthly price, and two-week free-trial offer. Build 1.0 (5) uses the replacement identifier and is available in the existing internal TestFlight group. The tester confirmed installing build 5 and supplied an App screenshot showing US$0.99/month without the trial overview. The screenshot itself does not contain the build number; that attribution relies on the installation report. We have not yet captured fresh raw Product fields for this replacement. The tester also reports that its system purchase sheet is normal, but has not supplied its exact current wording or a screenshot. We therefore keep this evidence separate from the build 4 log values. Changing the ordinary Apple account under Media & Purchases did not change the reported App display. This was not a dedicated Sandbox Apple Account comparison. We have not established the replacement product's propagation state or the platform root cause. Relevant implementation path The following condensed excerpts show the production path, not a standalone reproduction project. Validation, state handling, and transaction verification are omitted here: // Product loading: let values = try await Product.products(for: [id]) guard values.count == 1, let product = values.first, product.id == id else { throw SubscriptionClientError.invalidProduct } products[id] = product // The UI model copies product.displayPrice directly. // Later, in the purchase method: guard let product = products[productID] else { throw SubscriptionClientError.unavailable } return try resolvePurchase(try await product.purchase(confirmIn: scene))Within a single completed load, the UI fields and cached purchase Product come from the same result and configured identifier. We do not convert the display price to USD or configure a separate CNY price for the system sheet. The trial overview requires an eligible two-week free-trial offer in the product data. Audited distribution artifacts did not contain a local StoreKit testing configuration or price fixture. What diagnostics would help distinguish product-metadata/storefront behavior from application state handling? Is a dedicated Sandbox-account storefront comparison the appropriate next control? Are there documented refresh requirements or known TestFlight issues relevant to this discrepancy? The existing build already logs product identifiers, raw price, currency, offer structure, and eligibility, so we can collect a targeted replacement-product observation if useful.
Replies
3
Boosts
0
Views
101
Activity
3d
MapKit route animation exported to MP4: permitted use and appropriate Apple contact
Hello, I am Rabia, publisher of RotaTakip, a pre-launch iOS outdoor GPS app being developed with my son. We are evaluating Apple Maps for a user-initiated route-video feature and would appreciate a reference to official guidance or the appropriate Apple contact before enabling it. Proposed use: A user selects their own recorded GPS route and creates a short animated recap over an Apple map. The app saves an MP4 to Photos, and the user may share it on social media or play it on non-Apple devices. Rendering would happen on the user's device using public APIs. Required Apple and third-party attribution would remain visible. We would not extract raw tiles, scrape map data, build a map database, or perform bulk/server-side rendering. The app is planned as a paid, one-time-purchase GPS app. The map would be a main visual element in the exported recap. Video export remains disabled pending clarification. We are considering two approaches separately: MKMapSnapshotter images with our own route overlays, potentially a sequence of camera views, encoded with AVFoundation. A user-initiated ReplayKit recording of an animated MKMapView, with the required system consent and recording indication. I have reviewed Attachment 6 of the Apple Developer Program License Agreement, especially sections 2.1-2.5, and the snapshot documentation. I found guidance on static snapshots, but not a clear explanation of this MP4 export and end-user sharing scenario. Questions: Is either approach a supported, permitted use under the standard agreement and documentation? Is there an official document addressing it? Does the answer differ for standard versus satellite/hybrid or 3D views, or for a fixed map with an animated route versus a moving camera? How should attribution and the Legal link be handled in a non-interactive exported video, and are there specific limits on intermediate-frame retention or rendering frequency? If separate permission or a different implementation is required, which Apple team or support category should we contact? We have submitted a Rights and Permissions inquiry and would appreciate guidance on the correct channel for this MapKit-specific question. Apps such as ReRun advertise route-video export, and Huawei Health offers dynamic route videos. We do not know the map source used in every exported video or whether these apps have separate agreements, so we are not assuming their availability grants permission for our implementation. We are looking for the documented path available to other developers. Thank you for any official references or routing guidance. Rabia / RotaTakip
Replies
0
Boosts
0
Views
35
Activity
3d
CloudKit sync fails in macOS TestFlight build – sandbox denies com.apple.cloudd
I have a macOS SwiftUI app using SwiftData with CloudKit synchronization. Bundle ID: com.mjsapps.PhrasePin CloudKit container: iCloud.com.mjsapps.PhrasePin CloudKit synchronization works when running the app from Xcode using the Development environment. However, synchronization does not work in the TestFlight / Production build. The Production schema has been deployed successfully. The TestFlight build has the expected entitlements, including: com.apple.developer.icloud-container-environment = Production com.apple.developer.icloud-container-identifiers = iCloud.com.mjsapps.PhrasePin com.apple.developer.icloud-services = CloudKit com.apple.security.app-sandbox = true com.apple.security.network.client = true The TestFlight build is signed as: Authority=TestFlight Beta Distribution Identifier=com.mjsapps.PhrasePin TeamIdentifier=8D6TX86CQK CloudKit/Core Data logging shows that the app is trying to use: container=iCloud.com.mjsapps.PhrasePin:Production but synchronization fails with: CKErrorDomain Code=6 Error connecting to CloudKit daemon NSCocoaErrorDomain Code=4099 The macOS sandbox log shows: Sandbox: PhrasePin(...) deny(1) mach-lookup com.apple.cloudd As a result, no com.apple.coredata.cloudkit.zone is created in the Production private database and no SwiftData records are synchronized. The problem has been reproduced on: macOS Sequoia 15.7.7 macOS Sequoia 15.7.9 The same app works with CloudKit in Development when run from Xcode. I have already submitted a Feedback Assistant report, but have not received a response. Has anyone seen this behavior with SwiftData + CloudKit in a sandboxed macOS TestFlight build? Is there an additional entitlement or provisioning requirement needed for access to com.apple.cloudd in Production?
Replies
1
Boosts
0
Views
56
Activity
3d
Cellular data unavailable while an underwater-depth WKExtendedRuntimeSession is running (Wi-Fi unaffected)
Our freediving app for Apple Watch Ultra declares WKBackgroundModes "underwater-depth" and "workout-processing". During a session it runs an HKWorkoutSession, enables Water Lock and starts a WKExtendedRuntimeSession. While the diver is at the surface it sends small URLSession uploads: a live position share for the people watching from shore. On an Apple Watch Ultra with its own cellular plan and the paired iPhone switched off, every URLSession request fails while the underwater-depth runtime session is running. We tested each piece on its own, checking connectivity every 10 seconds and logging URLSessionTaskTransactionMetrics.isCellular and NWPathMonitor. Cellular only: with nothing running, 26 of 27 requests succeeded over cellular. Within seconds of the underwater-depth runtime session starting, requests time out (-1001) and NWPathMonitor reports no available interface. With the HKWorkoutSession and Water Lock running but the runtime session ended, 8 of 8 succeeded over cellular. Cellular returns within about 5 seconds of the runtime session ending. Wi-Fi only (iPhone switched off, known Wi-Fi): 34 of 34 requests succeeded over the watch's own Wi-Fi in every stage, including while the underwater-depth runtime session was running. Another shipping dive app loses cellular the same way when its dive session starts, so it does not appear to be specific to our app. Steps to reproduce: on an Apple Watch Ultra with an active cellular plan, switch the paired iPhone off and move away from any known Wi-Fi network. In an app with the underwater-depth background mode, start a WKExtendedRuntimeSession, then make a URLSession request. It times out while the session runs, and succeeds again within seconds of the session ending. Our questions: Q1. Is cellular data intentionally unavailable to apps while an underwater-depth session runs, while Wi-Fi remains available? Q2. Is there a supported way to send a small amount of data over cellular during an underwater-depth session (for example while the diver is at the surface) without ending the session? Q3. If neither, we have filed FB25362581 asking for cellular to be allowed at the surface, as Wi-Fi already is. We have a focused test project (about 140 lines) that reproduces it and can share it with DTS. watchOS 27.0.1, Apple Watch Ultra 2, Xcode 27.1.
Replies
1
Boosts
0
Views
97
Activity
3d
App Review device never reaches our domain (NSURLErrorDomain -1001, no requests in server or Cloudflare logs)
Hello, Our iOS app has been rejected four times under Guideline 2.1(a) because sign-in fails on the review iPad. The latest rejection showed NSURLErrorDomain error -1001 (the request timed out) on an iPad Air 11-inch (M3) with iPadOS 27.0, on November 5, 2026, at about 11:54 UTC. The same happened on October 16, 2026. Setup: API: https://wp.pavilion.az, HTTPS on port 443, fixed DNS name DNS and proxy on Cloudflare (IPv4 and IPv6), publicly trusted certificate The app uses URLSession, with no custom certificate checks and no proxy settings What we checked: Neither our origin server nor Cloudflare logged any request from the review device on either day. Other clients were served normally during the same minutes. The domain resolves normally from many public DNS resolvers in the United States and Europe, over IPv4 and IPv6. The app signs in in under one second on an iPad simulator in a data center in Los Angeles, and on our own devices through TestFlight. This looks similar to https://developer.apple.com/forums/thread/773444, where a Cloudflare-hosted domain resolved to a wrong address inside Apple's network. Could someone from Apple check how wp.pavilion.az resolves, and whether it is reachable, from the App Review network? We have resubmitted a build that adds a short network check to the error message (the DNS result and which connection step fails), but each review cycle takes many days. Thank you.
Replies
5
Boosts
0
Views
325
Activity
3d
Egress addresses of the URL filter OHTTP relay
Hello, I am wondering about the egress addresses of the Oblivious HTTP relay that Apple runs for Network Extension URL filters. I am building an iOS app that uses NEURLFilterManager. The app builds a Bloom filter from the block lists a user picks. The system only asks our server about a site when that filter has a hit. Each lookup is encrypted with keyword PIR and carries a Privacy Pass token instead of anything tied to the user. It reaches our server through your relay, which strips the device's address. We run our own PIR server, Privacy Pass issuer and OHTTP gateway instead of a hosted service. The gateway is the one part of the setup that should only ever hear from your relay. Since every real lookup comes through the relay, I would really like to drop all other traffic to it at the firewall. Right now I can't do that. I also can't rate limit by address because every legitimate request shares the relay's addresses. As a result the gateway just has to stay open to everyone and rely on global limits, which is a far cry from what I'd want for a service that only one client is meant to reach. I have three questions about this. 1) Are the relay's egress address ranges published somewhere, or can they be shared with developers who have been onboarded? 2) If they are shared, how would we find out when they change and how much notice there is? 3) If the addresses can't be shared, is there another way to tell that a request came from the relay, such as a header or a client certificate? Please let me know if any of this is unclear or if there is a better place to ask. Thank you in advance, Alexander
Replies
1
Boosts
0
Views
89
Activity
3d
macos 27 - unexpected/new errno from BSD socket connect() when pending connections exceed backlog
Please consider the trivial C program attached to this thread. The code creates a socket() and listen()s for connections, but (intentionally) doesn't accept() the connections. The listen() is done using a small backlog (of 1). This test then does several connect() attempts and expects that the connect() attempts will accumulate in the pending queue and once the queue exceeds the backlog limit, then as specified in man listen: The backlog parameter defines the maximum length for the queue of pending connections. If a connection request arrives with the queue full, the client may receive an error with an indication of ECONNREFUSED. then the connect() attempt will receive a ECONNREFUSED. However, in macos 27, such a connect() attempt leads to ECONNRESET (Connection reset by peer) instead of ECONNREFUSED. Is this expected? Experiments show that prior versions of macos were returning a ETIMEDOUT for such connect() attempts. If this new error is expected from connect() when the backlog limit has exceeded, should it be specified in the man listen documentation? Rename the attached main.c.txt to main.c. Compiling the attached program on macos 27, using clang main.c and then running ./a.out results in: ----------------------- MacOS version: 27.0.1 Kernel version: Darwin Kernel Version 27.0.0: Tue Aug 11 21:02:16 PDT 2026; root:xnu-13432.1.9~1/RELEASE_ARM64_T8112 ----------------------- started server at at 127.0.0.1:52753 with a backlog of 1 connect() attempt 1 - connected connect() attempt 2 - connected connect() attempt 3 - connected connect() attempt 4 - connected connect() attempt 5 - failed to connect() - Connection reset by peer <-- FAILURE: Unexpected error code, expected either ETIMEDOUT or ECONNREFUSED but got 54 connect() attempt 6 - connected connect() attempt 7 - connected connect() attempt 8 - connected connect() attempt 9 - failed to connect() - Connection reset by peer <-- FAILURE: Unexpected error code, expected either ETIMEDOUT or ECONNREFUSED but got 54 connect() attempt 10 - failed to connect() - Connection reset by peer <-- FAILURE: Unexpected error code, expected either ETIMEDOUT or ECONNREFUSED but got 54 connect() attempt 11 - failed to connect() - Connection reset by peer <-- FAILURE: Unexpected error code, expected either ETIMEDOUT or ECONNREFUSED but got 54 On a related note, it's unclear why several of the connect() attempts succeeded instead of just 1 of them succeeding. On prior versions of macos, the output of the same program is: ----------------------- MacOS version: 26.7.1 Kernel version: Darwin Kernel Version 25.6.0: Tue Aug 18 17:49:13 PDT 2026; root:xnu-12377.161.15.700.19~2/RELEASE_ARM64_T6000 ----------------------- started server at at 127.0.0.1:52451 with a backlog of 1 connect() attempt 1 - connected connect() attempt 2 - failed to connect() - Operation timed out connect() attempt 3 - failed to connect() - Operation timed out connect() attempt 4 - failed to connect() - Operation timed out connect() attempt 5 - failed to connect() - Operation timed out connect() attempt 6 - failed to connect() - Operation timed out connect() attempt 7 - failed to connect() - Operation timed out connect() attempt 8 - failed to connect() - Operation timed out connect() attempt 9 - failed to connect() - Operation timed out connect() attempt 10 - failed to connect() - Operation timed out connect() attempt 11 - failed to connect() - Operation timed out and this output is much more understandable and deterministic. main.c.txt
Replies
3
Boosts
0
Views
380
Activity
3d
Instructions for debugging recent macos kernel versions?
Is there any recent and a bit authoritative documentation which explains how to debug recent versions of macos kernel? I have found some blog posts from other users but those are either outdated or don't work for some other reason. I am guessing kernel debugging is pretty common for developers working on macos itself, so I'm hoping someone in this forum would have some working instructions for that.
Replies
20
Boosts
1
Views
1.6k
Activity
3d
AccessoryAccess for a Developer ID virtualization app: can it replace a root daemon for USB storage devices?
I build AVM, the Accessible Virtual Machine, a free, open source Mac app that runs Windows 11 for ARM in QEMU. It's built for blind people who use VoiceOver on the Mac and a screen reader in Windows. It's on GitHub at https://github.com/allisonfm85/accessible-virtual-machine. AVM ships with Developer ID, it's notarized, and it isn't sandboxed. QEMU runs as a child process, signed by the same team, and does the USB work itself through usbredir and libusb. I asked DTS about this (case 23107052), and Quinn pointed me to thread 851767. Today AVM captures USB devices from a root daemon registered with SMAppService. That works for braille displays and microphones. It fails for USB flash drives. Opening interface 0 returns 0xe00002c9. I measured why with a small IOUSBHost tool: Run with sudo from a terminal that has Removable Volumes: works. Same command with Removable Volumes turned off: fails with 0xe00002c9. Run as a launchd daemon in the system domain: fails. Full Disk Access makes no difference. So the block is the Removable Volumes permission, and a daemon has no responsible app to carry it. Granting it to AVM doesn't help the daemon. Thread 851767 shows a flash drive working through AccessoryAccess and IOUSBHostDevice, with interfaces opened through IOUSBLib. That looks like the path I should be on. My questions: Is the Claim USB Accessory capability (com.apple.developer.accessory-access.usb) available to Developer ID apps outside the Mac App Store? Does it require the App Sandbox? Does the user's AccessoryAccess consent cover a USB storage device's interfaces? In other words, would it get past the Removable Volumes check that stops my daemon? Can AVM pass createXPCRepresentation to QEMU, a non-sandboxed child process from the same team, and have QEMU open the accessory there? libusb opens interfaces through IOUSBLib. Given FB25324561, is it reasonable to ship on that path for now? If AccessoryAccess isn't available to Developer ID apps, I'd still welcome guidance on a supported way, such as com.apple.vm.device-access. I'm happy to share my sample project or logs. Thank you, Allison Meloy
Replies
1
Boosts
0
Views
121
Activity
3d
Foundation reports false for encryption on two encrypted external APFS volumes
We request clarification of a Foundation API discrepancy from existing read-only diagnostics. Environment: the user has personally run sw_vers on the currently running Mac and confirmed ProductName: macOS; ProductVersion: 27.0.1; BuildVersion: 26A434. This is the currently confirmed system version. The reviewed records do not establish an unambiguous temporal link between that confirmation and the APFS/Foundation measurements on 15 November 2026; we therefore do not assert that it proves the OS version used for those measurements. Earlier macOS 26.6.2 (25G83) records are historical and are not presented as the current system. Observed volumes: External APFS Volume A and External APFS Volume B, both external APFS volumes connected over USB. For BOTH volumes, the recorded diskutil results are: Encryption=true; EncryptionThisVolumeProper=true; CryptoMigrationOn=false; GlobalPermissionsEnabled=true. Both were mounted and unlocked after completed in-place APFS encryption. For BOTH volumes, direct Foundation queries at the volume root return: NSURLVolumeUUIDStringKey: the correct UUID for the respective volume (omitted here for privacy); NSURLVolumeURLKey: the same volume-root URL as queried; NSURLVolumeIsEncryptedKey: present, explicit false (__NSCFBoolean, description 0). The canonical mount path and diskutil volume identity match. This is not an inquiry against a parent volume, a missing key converted to false, or an inferred mapping based only on a display name. Minimal read-only observation procedure, describing the existing successful queries (not rerun for this request): Select the already mounted APFS volume root and verify its UUID against diskutil. Construct a fresh NSURL using fileURLWithPath for that root. Query resourceValuesForKeys:error: for NSURLVolumeUUIDStringKey, NSURLVolumeURLKey and NSURLVolumeIsEncryptedKey. Compare the returned UUID/root URL and explicit encryption Boolean with the recorded diskutil fields. The successful queries used Foundation through JavaScript for Automation's Objective-C bridge, in separate helper processes. An equivalent full Swift application runtime result has not been established. A separate failed JXA enumeration attempt is excluded from the evidence. We understand URL resource values may be cached; caching has not been established as the cause. Expected: an encryption indication consistent with the completed APFS encryption, or documented semantics explaining why these indicators differ. Actual: explicit false on both volumes. Questions: Are there documented limitations or known issues for this property on external, mounted and unlocked APFS volumes encrypted in place? What does false mean when the recorded diskutil encryption fields are positive? Is any additional read-only evidence necessary to interpret it? Which supported public read-only API and validation procedure should an application use to establish completed APFS volume encryption without weakening its policy? Could the observed behavior be affected by accessing NSURL resource values through the JavaScript for Automation Objective-C bridge rather than directly from a native Swift application? We are requesting interpretation of existing evidence. No further encryption, lock/unlock experiment, drive modification or application build was performed for this inquiry. No credentials, private paths or customer data are included. Thank you.
Replies
1
Boosts
0
Views
131
Activity
3d
Is it possible to run an iPadOS virtual machine inside an iOS app?
Hi everyone, I am researching the technical feasibility of a project named Kairavox. The goal is to run a genuine, unmodified iPadOS installation as a guest VM inside a standalone app on an ordinary, unjailbroken iPhone. Our first research target is iPadOS 27.2.1 on an iPad 9th-generation (A13) guest. This is not an iPadOS-style interface or a remote desktop. We want to boot and run actual iPadOS in the guest. Proposed approach Apple’s public virtualization and hypervisor documentation appears to cover Mac hosts, not iPhone hosts. We are therefore investigating a native software AArch64 interpreter inside a normal iOS app. JIT is not assumed; we would consider it only if Apple confirms an applicable, supported development path. We are considering personal development signing and sideloading tools such as AltStore or SideStore. App Store distribution is not a project requirement. We understand that these tools do not themselves grant Apple entitlements, and that free Personal Team provisioning has limits. We are also investigating Apple’s documented Increased Memory Limit and Extended Virtual Addressing entitlements. We do not know whether either is available for this app and signing route, or what memory budget would actually be available to guest RAM. Projects such as Henge and GetMoreRam are useful points of comparison, but we understand that they do not establish an Apple-supported route for an iPadOS guest. We will not rely on private APIs, unauthorized entitlements, Secure Boot bypasses, or firmware patches. Questions Is there a documented iOS API or entitlement that lets a third-party iPhone app host a virtual CPU or VM? If not, is a native software interpreter a supported way for an app to interpret AArch64 guest instructions? Does Apple permit that interpreter to run an unmodified iPadOS guest in a sideloaded development app? Are there specific code-execution or licensing restrictions we should review? Apple documents virtual hardware identities and restore workflows for macOS VMs. Is there an analogous supported guest identity and image-personalization process for iPadOS, including an iPadOS 27.2.1 guest? Does Apple document a virtual SEP model, or another supported way to meet SEP-dependent boot, storage, and platform-service requirements for an iPadOS guest? Development Signing & JIT: For development on our own stock iPhone, can free Personal Team signing support this kind of application? Are there documented JIT permissions available through this signing route? If not, does JIT require a different signing arrangement or entitlement? Can an independent developer request the Increased Memory Limit entitlement for an iOS app through a documented process? How should we distinguish that process from Extended Virtual Addressing and the development-only Increased Debugging Memory Limit entitlement? If these questions are better directed to Developer Technical Support or another Apple team, please point us to the appropriate channel. We are looking for a documented, authorized path and will not assume one exists. Thanks for any guidance.
Replies
1
Boosts
0
Views
231
Activity
3d
Can a third-party iOS app automatically launch in the foreground at a scheduled time without user interaction?
Hello, I would like to clarify whether iOS provides any supported public API for automatically bringing a third-party app to the foreground at a scheduled time. The requirements are: The user has explicitly opted in to this behavior in advance. The app may be in the background, suspended, or not running. At a specified time, the app should automatically appear in the foreground without the user tapping a notification or performing any other action. The app should then automatically display and play media. Ideally, this should also work when the iPhone is locked. I understand that iOS has restrictions on background execution and that frameworks such as AlarmKit provide system-managed alarm experiences. My questions are: Is there any supported public API, entitlement, or combination of frameworks that enables this behavior? Can AlarmKit or another framework automatically launch a third-party app into the foreground without user interaction? If this is not supported, is it an intentional platform restriction? I am specifically asking about automatic foreground activation, not simply delivering a notification or running background tasks. Thank you for your guidance.
Replies
1
Boosts
0
Views
48
Activity
3d
Supported App Sandbox metadata access through an inherited file descriptor, without reopening the object
We are evaluating a macOS design before implementation. This is a platform-support question, not a report of an observed runtime failure. No actual controller executable, helper executable or deployment configuration has been selected or qualified. Our objective is to let a small, fixed-purpose helper examine an already-open object’s identity and access control list (ACL) metadata while preserving the original object reference and ownership. Proposed configuration A trusted controller would launch one native C helper using an explicit executable target and posix_spawn. The controller would need to qualify for the documented nonsandboxed-parent case, without a conflicting inherited sandbox. We do not assume that an absent entitlement alone establishes this. The helper would be the main executable of its own signed application bundle, using its own ordinary App Sandbox rather than inheriting the controller’s sandbox. Its proposed additional filesystem permission would be com.apple.security.temporary-exception.files.absolute-path.read-only, containing exactly two fixed directory entries beneath a user’s development workspace, outside the helper’s container. The literal private paths are omitted. The controller would already own a read-only file descriptor for one regular file or directory within those trees. It would retain its original reference and pass a known duplicate referring to the same open object to the helper. The helper would perform one metadata observation. The proposed operations are fstat for object identity and fgetattrlist requesting ATTR_CMN_RETURNED_ATTRS and ATTR_CMN_EXTENDED_SECURITY, with FSOPT_REPORT_FULLSIZE and without FSOPT_PACK_INVAL_ATTRS. Required boundaries The helper must use only the inherited descriptor for the subject observation. The design does not permit: Reopening or resolving the subject through a pathname, bookmark or URL. Substituting a copied file or another object reference. Reading file contents, enumerating directories, changing permissions, or modifying shared descriptor flags or file offsets. Expanding the exception to an ancestor, home directory or broader workspace. Disabling an existing sandbox or using private interfaces to bypass restrictions. Parent-side traversal and identity checks remain separate responsibilities. Strict ancestor directories are not additional helper ACL subjects. We understand that a read-only directory exception and ordinary sandbox/container capabilities may permit more than the helper’s intended metadata operations. Metadata-only behaviour would be a reviewed-code obligation; we are not asking App Sandbox to enforce an exact metadata-only operation filter. Questions Supported launch and activation: Under what documented parent-context, signing, bundle, container and launch conditions can this helper establish its own ordinary App Sandbox? What supported mechanism or guarantee establishes that the sandbox is effective before the subject metadata operation? Required metadata permissions: Does the proposed read-only exception support fstat and the specified extended-security fgetattrlist request through an inherited read-only descriptor, for both regular files and directories? Please distinguish descriptor survival from permission to perform these operations, including any additional access-control conditions. Scope, identity and lifetime: What documented behaviour applies to descendant coverage, aliases, hard links, renames or namespace changes after the descriptor was opened? Please distinguish the lifetime of the inherited object reference from the lifetime of the static directory permission. Our design would refuse uncertainty rather than reopen, rebind or widen access. Evidence and support boundary: Which public documentation, interfaces or authoritative guarantees support this exact composition, and which parts require separate empirical qualification? Please identify applicable macOS versions and restrictions. Distinguish platform support from any distribution or App Store review requirements. If these requirements cannot be combined through supported interfaces, please identify the incompatible requirement. An approach requiring broader access, pathname reopening, a replacement object or a different handoff architecture would be a design change requiring separate review, not a solution within the stated constraints. Permission failures, unsupported requests and incomplete metadata would remain unavailable results. They would not be interpreted as proof that an ACL is absent. Complete ACL-absence interpretation and native resource bounds remain separate qualification questions. Apple material already reviewed Resolving App Sandbox Inheritance Problems App Sandbox Temporary Exception Entitlements Accessing files from the macOS App Sandbox
Replies
1
Boosts
0
Views
237
Activity
3d
macOS 26.x App Sandbox: supported disk-image attachment and descriptor-based unmount
On macOS 26.x, is there a public, supported way for an App Sandbox application with com.apple.security.virtualization to attach a new disk-image file held in its own container and mount its APFS filesystem within that container, without root, privileged or unsandboxed helpers, private/temporary exception entitlements, Full Disk Access, or weakening App Sandbox? We distinguish attaching the image from mounting an already attached virtual device. DTS threads 655767, 780965 and 775835 discuss these separately. Which supported API or tool and entitlements apply on 26.x, if such a path exists? If attachment is supported, what ownership and sandbox checks apply to a later normal funmount(fd, 0) using an O_EVTONLY descriptor for that exact mount's root? Is this combination supported, including when another actor has already unmounted it? If not, what supported alternative preserves the same restricted profile and avoids force or whole-disk unmount?
Replies
0
Boosts
0
Views
83
Activity
3d
NSE Filtering for encrypted incoming calls: what technical details should we provide?
We’re preparing the first iOS release of ANTINTWRK, an encrypted messenger with voice and video calls. Our push gateway sends a regular APNs alert for the encrypted event. On the receiving device, the Notification Service Extension fetches and decrypts the referenced event. In this delivery path, the gateway does not distinguish an encrypted call invitation from a message. When the extension identifies a ringing call, it uses CXProvider.reportNewIncomingVoIPPushPayload to hand it off to CallKit and suppresses the original alert to avoid a duplicate notification. Our Notification (NSE) Filtering request, submitted on October 25, 2026, still shows Submitted. Xcode cannot export the App Store build because the extension’s distribution profile lacks com.apple.developer.usernotifications.filtering. We have contacted Developer Support under Entitlements. We’re following Apple’s Sending End-to-End Encrypted VoIP Calls guidance. For this design, what technical details or test evidence should we provide so the capability review team can evaluate the request? Is there a recommended way to attach that material to the existing request? We can provide the request and support case IDs privately if needed.
Replies
0
Boosts
0
Views
135
Activity
4d
HKStatisticsCollectionQueryDescriptor intermittently returns no data for certain date ranges on iOS 27
We are seeing inconsistent results from HKStatisticsCollectionQueryDescriptor on iOS 27. Using the same quantity type, statistics options, anchor date, interval components, and predicate configuration, some date ranges return the expected statistics, while other ranges unexpectedly return empty results or buckets with no quantity. The affected ranges do contain HealthKit samples: HKSampleQueryDescriptor finds samples in the same date range. HKStatisticsQueryDescriptor returns the expected value when run separately for an affected bucket. HKStatisticsCollectionQueryDescriptor returns no quantity for that same bucket. Slightly expanding or shifting the date range may cause the collection query to return data again. A simplified version of the query looks like this: let datePredicate = HKQuery.predicateForSamples( withStart: startDate, end: endDate, options: .strictStartDate ) let descriptor = HKStatisticsCollectionQueryDescriptor( predicate: .quantitySample( type: quantityType, predicate: datePredicate ), options: .cumulativeSum, anchorDate: anchorDate, intervalComponents: DateComponents(day: 1) ) let collection = try await descriptor.result(for: healthStore) collection.enumerateStatistics(from: startDate, to: endDate) { statistics, _ in let quantity = statistics.sumQuantity() print(statistics.startDate, quantity as Any) } Expected behavior Every interval containing matching samples should return the corresponding statistics, regardless of the overall requested date range. Actual behavior Some date ranges produce missing or empty buckets even though matching samples exist and an individual HKStatisticsQueryDescriptor can calculate the expected value. Changing only the date range can make the data appear or disappear. The samples are visible to the app in the affected range, so this does not appear to be explained solely by iOS 27’s Limited History authorization. This behavior was not observed with the same query flow on earlier iOS versions. Is this a known regression in HKStatisticsCollectionQueryDescriptor on iOS 27, or has the expected date-range or predicate behavior changed?
Replies
4
Boosts
3
Views
1.1k
Activity
4d
CKKS zone deletions return success but stale 2019 key hierarchy persists; "Delete iCloud Data" not offered (FB25584356)
I filed FB25584356 for this and would appreciate any pointers. Setup: Mac mini on macOS 27.2.1 and an iPhone on iOS 27.2, same Apple Account, HSA2, Advanced Data Protection off. Octagon is healthy (otctl status = Ready, both devices trusted). Symptoms: AirDrop to my own iPhone fails when I pick the device (rapportd: "PairVerify server M2 failed: copy identity"), iPhone Mirroring ends with noCompatiblePhone, and various clients log CKErrorDomain 111 / 5009 "Keychain Sync Incomplete". What I see in CKKS: seven zones (AutoUnlock, LimitedPeersAllowed, Home, Manatee, ApplePay, Health, Engram) still hold a key hierarchy from August 2019. The only TLKShare was issued by a device that left the account years ago, so neither current device can unwrap the TLK ("No trusted TLKShares", CKKSErrorDomain 35). secd then does what I would expect: tlkmissing → "No other devices claim to have the TLK. Resetting zone..." → CKKSDeleteCKZoneOperation → local reset → zones recreated. The delete appears to succeed. With debug logging, cloudd shows status:200 and "RecordZone ... was successfully deleted from the server" for each zone. The next fetch returns the same 2019 records with an identical server change token. Over about 11 hours: 124 reset cycles, 869 zone deletions reported as successful, 182 consecutive AutoUnlock fetches with the same change token. When not throttled it runs roughly every 5 seconds; CloudKit eventually answers "Service Unavailable" (CKError 6/2009) with a ~59 minute retry-after, and all 23 zones are unusable in the meantime. ckksctl -v AutoUnlock reset-cloudkit behaves the same way. Reset path: Support article 120862 describes "Don't know passcode?" → "Forgot all passcodes?" → "More Options" → "Delete iCloud Data". With the Mac signed in but not yet trusted, "Don't know passcode?" only offered Cancel / Try Again Later, in the sign-in flow and in both System Settings follow-ups. After three wrong passcodes the alert had a single "Try Again Later" button, although cdpd logged "Creating recovery option: Reset". Questions: Is a client-side zone delete expected to be a no-op for these zones while the server reports success? Is there a supported way to reach performCKServerUnreadableDataRemoval / "Delete iCloud Data" when another trusted device exists? I am fine with losing the end-to-end encrypted data in those zones. Logs and a sysdiagnose are attached to the Feedback.
Replies
0
Boosts
0
Views
125
Activity
4d