Posts under App & System Services topic

Post

Replies

Boosts

Views

Activity

Subject: Critical APFS Data Loss Bug & Error 1110 Loop during official Finder Update on iPhone 14 (A15)
Hello, I am requesting an engineering escalation regarding a critical bug in Apple's APFS update pipeline that trapped an iPhone 14 (A15, 128 GB) in recovery mode during an official Finder update from iOS 16.6 to iOS 18 (27.2.1, 24B156) on macOS 14.5. The device hardware is 100% healthy (Apple MRI diagnostics all green), the passcode is known, and 101,175 MB (341,967 files) of user data remain intact on the flash storage. However, the device cannot boot or complete an update due to a corruption caused by Apple's own restore tools. --- ### What Happened (Verified in Logs): 1. **Initial Full Storage State:** The device had ~105 GB utilized and was updated via Finder using "Update" (not Restore). 2. **Destructive fsck Behavior:** In pass 3, the restore ramdisk ran `/sbin/fsck_apfs -dy /dev/disk2`. On the nearly full container, fsck erroneously flagged 8,182 live omap mappings as "orphans" and deallocated them, causing extent-ref b-tree node `0x10bb3` to be zeroed out (TRIMmed by the flash controller). 3. **Split Failure:** In pass 4, the iOS 18 System volume installed and sealed, but `split_data_volume` failed in 4 seconds when `apfs_migrator` encountered block `0x10bb3` (`obj_read` checksum failure returning EILSEQ / error 92). 4. **False Error 1110 Loop:** Every subsequent attempt now halts immediately at `space_checks` with Error 1110. --- ### Reverse Engineering Proof: Disassembly of `restored_update` (arm64e, VA 0x10001afcc / 0x10001b0e8) confirms a major error-handling bug: When `splitter_dump` encounters the unreadable block `0x10bb3`, it fails with `EILSEQ` (92). Instead of handling this error, `restored_update` executes: `mov x19, #-1; mov x0, x19; ret` The caller receives `-1 bytes of free space`, logs: "Data volume requires splitting. Splitter will leave -1 bytes of free space after completion. Current free space on device: 6620069888 bytes. Insufficient space on device to run splitter" and aborts with **CHECKPOINT FAILURE:(FAILURE:1110)**. The device is NOT out of space (it has 6.3 GB free); it is blocked solely because `restored_update` misinterprets an EILSEQ filesystem error as negative free space. --- ### Current State & Request: - The encryption keys and SEP/gigalocker are intact (`gigalocker: ONLINE`). - In the restore ramdisk, `/dev/disk2s2` mounts cleanly as read-write on `/mnt2`. - Zero APFS snapshots remain on the volume, meaning the extent-ref tree is theoretically fully reconstructible from the valid fsroot inode tree. I am requesting assistance from CoreOS / APFS engineering: 1. Is there an engineering update ramdisk or build that can bypass the `splitter_dump` EILSEQ check, or rebuild the extent-ref tree, so the update can finalize? 2. Alternatively, can an engineering liaison facilitate a non-destructive extraction given that the volume mounts read-write and the user passcode is known? I can immediately provide full terminal transcripts, Finder updater logs (`iPhoneUpdater-*.log`), and disassembly details. Thank you, Samuel Journo
1
0
106
3d
macOS APFS: com.apple.macl and UF_TRACKED appear after creating a hard link — safe file replacement and rollback?
I'm investigating an unexpected metadata change during a controlled file deployment on macOS. Environment and observed state Two regular configuration files are used by a local service. Before replacement, the first file had: SHA-256: verified. File flags: 0. Extended attributes: none. Hard-link count: 1. Owner/group: 501/20. Permissions: 0644. ACL: empty. A backup procedure created a hard link to preserve the original inode before replacing the active pathname with an independently created file. Immediately after creating and verifying the hard link, the original file was observed with: The same SHA-256 and inode. Flags: 64 (UF_TRACKED). Extended attribute: com.apple.macl. Hard-link count: 2. No file content was replaced. The procedure stopped because the metadata no longer matched the original baseline. Additional observations Other backup methods also encountered unexpected metadata changes during destination creation. Tests using renamex_np with RENAME_SWAP successfully exchanged and restored artificial files with flags 0 and empty extended attributes. A test with artificial files already containing com.apple.provenance also succeeded. We could not reproduce the specific UF_TRACKED + com.apple.macl + two-hard-link state in an isolated fixture using ordinary documented operations. The operational original and its second hard link currently share the same inode. No attempt has been made to remove the protected attribute or change its flags. Questions for Apple filesystem/security specialists Under what documented circumstances can creating a hard link or related Finder/TCC document-tracking behavior cause UF_TRACKED and com.apple.macl to appear on an existing file? Are these metadata changes expected for a file accessed through a user-authorized Documents location? What supported mechanism can preserve the current original inode and provide a verifiable rollback when replacing its active pathname? Is renamex_np(..., RENAME_SWAP) appropriate for this situation, and what special considerations apply to the existing second hard link and protected extended attributes? What verification criteria would you recommend before permitting a production replacement? I am looking for a documented, reversible procedure that preserves macOS security protections. I do not want to disable SIP, forcibly remove com.apple.macl, or bypass TCC. I can provide sanitized metadata comparisons and a minimal reproduction if needed.
1
0
153
3d
watchOS — Continuous Core Motion monitoring in the background for independent fall detection
I'm developing an independent fall-detection application for Apple Watch using Core Motion (CMMotionManager) at 20 Hz. The goal is to identify potential falls using accelerometer, gyroscope and orientation data, then notify nominated family contacts. The application is deliberately independent of Apple's built-in Fall Detection and Emergency SOS. Test environment Physical Apple Watch running watchOS 27.2 Xcode 27.2 Core Motion device-motion callbacks on a dedicated serial OperationQueue Motion processing on the MainActor Tests performed without the Xcode debugger attached Observed results With the Watch display awake: 2,300 processed samples Longest sensor timestamp gap: 0.05 seconds Longest callback arrival gap: 0.66 seconds Callback interruptions over one second: 0 With the Watch dimmed/backgrounded: 3,229 processed samples Longest sensor timestamp gap: 0.30 seconds Longest callback arrival gap: 29.11 seconds Callback interruptions over one second: 6 Maximum sample delivery lag: 29.065 seconds The motion timestamps appear nearly continuous, but callback delivery becomes substantially delayed after the app enters the background. The monitoring flag remains true, and no explicit call to stop motion updates occurs when the app becomes inactive. Questions Is there an Apple-supported background execution mechanism or entitlement allowing a third-party watchOS app to continuously process accelerometer and gyroscope data for independent fall detection, without requiring an active workout session? Would CMBatchedSensorManager provide any useful background delivery capability for this application, or would its callbacks remain subject to normal watchOS suspension? Is there a recommended architecture for detecting a potential fall and initiating a timely family notification while the Watch app is backgrounded, without relying on Apple's built-in Fall Detection or Emergency SOS? We understand that workout sessions and extended runtime sessions have specific intended purposes. We want to implement this correctly rather than use an unrelated background mode to prevent suspension. Any guidance from Apple engineers or developers experienced with watchOS background Core Motion processing would be greatly appreciated.
2
0
109
3d
NEURLFilterManager: inconsistent per-domain blocking (some sites never block, one flaps) - confirmed PIR database is correct
Hello, Some context: DropBet is an app that helps people with gambling addiction stay off gambling sites and apps, using NEURLFilterManager/PIR to block a large list of known gambling domains system-wide. For a lot of our users this filter is a core part of their recovery > reliability really matters here. Since fixing an unrelated HPKE encryption bug (separate thread, now closed), the filter works end-to-end for the first time, but blocking is inconsistent per domain in a way I can't explain from my side: winamax.fr and the Winamax app: blocked reliably, every single time > clean "connection failed" style block, confirmed to load fine with protection off. unibet.fr and betclic.fr: never blocked, consistently > confirmed even after a full device reboot (rules out stale caching), and confirmed identical across both Safari and Chrome on iOS tested side-by-side (so not browser-specific). olybet.fr: flaps > the page reloads every 2-3 seconds with protection on, also identical across both browsers. Confirmed this only happens with the filter enabled (tested toggling protection off/on against the same page). unibet.fr auto-redirects into the native Unibet app via a Universal Link before the page loads, unlike betclic.fr which stays in the browser > different code path, possibly relevant. To rule out any issue on our end, I wrote a standalone test that queries our deployed PIR database shards directly - bypassing OHTTP, the app, and the device entirely - for all of the domains above plus their www. variants. All of them correctly return the blocked value, no exceptions, including unibet.fr and betclic.fr which never block on the actual device. So the database, the PIR protocol implementation, and the server are confirmed correct for every domain I've tested. This points at something in how NEURLFilterManager/ciphermld applies a correctly-received PIR verdict on-device - possibly related to query batching, an evaluation-key edge case, or Universal Link handling bypassing the filter before a web request is even made. Is there anything you can share about how the client applies results once decrypted, or known issues around any of this?
7
0
347
3d
StoreKit introductoryOfferEligibility: safe retry after JWS expiration
How should a server safely retire or renew an unused JWS for Product.PurchaseOption.introductoryOfferEligibility(compactJWS:) after cancellation or interruption? Our application allows a first-purchase discount once per application account across payment platforms. We bind the signed eligibility request to a verified Apple app transaction, product, and purchase attempt, persist the exact JWS, and reuse it for the same attempt. Once a paid purchase is verified, we consume the application's eligibility. We do not automatically issue another nonce after cancellation, a signature error, or an empty transaction history. Apple's JWS documentation describes a one-time nonce and expiration calculated from iat, and says not to include exp: https://developer.apple.com/documentation/storekit/generating-jws-to-sign-app-store-requests I could not find the lifetime or a supported retirement/renewal procedure for the introductory-offer-eligibility audience. Keeping an unusable authorization forever would prevent the customer from trying another checkout; replacing it without retiring the original might leave two redeemable authorizations. What we observed Environment: Xcode 27.2 (27B52), macOS 26.6.2, physical iPhone 16 with iOS 27.0, Apple Sandbox. Verify the Apple-signed AppTransaction and issue one eligibility JWS. Start the purchase using that JWS, then cancel the payment sheet (userCancelled). Terminate and relaunch the app without resetting purchase history or replacing the authorization. Retry the same product and Apple account using the byte-for-byte identical JWS. Complete the Sandbox purchase and verify the Apple-signed transaction on an isolated server. The successful verification happened about 164 seconds after issuance. This is one successful cancellation/retry observation, not a reproduced expiration failure or proof of a general validity/nonce-consumption rule. It also did not verify our intended introductory price. The purchase call uses the persisted value: let result = try await product.purchase(options: [ .introductoryOfferEligibility(compactJWS: existingJWS) ])Supported lifecycle questions What is the validity period derived from iat, including clock-skew allowances and any Sandbox/production differences? Which API or documented error can establish that a previously issued authorization is definitively unusable, rather than merely absent from transaction history? When is the nonce consumed, and what happens after userCancelled, interruption, pending approval, expiration, or an uncertain result? Is invalidOfferSignature specific enough to distinguish expiration from consumption, account mismatch, or a bad signature? Is it supported to keep the same nonce and all bindings, update only iat, and re-sign? If so, is one-time use enforced across every version and for what retention period? If renewal requires a new nonce, how can the prior authorization be invalidated first? Is there another recommended recovery flow that prevents duplicate redemption without indefinitely blocking checkout? DTS directed us to ask this lifecycle question on the forums. A sanitized minimal Xcode project was already supplied privately to DTS; it demonstrates the observed cancel/relaunch/same-JWS retry, not an expiration failure. We would appreciate a supported procedure or documentation reference.
1
0
84
3d
Supported publication of HID Report Reference descriptor 0x2908 on iOS
Supported publication of HID Report Reference descriptor 0x2908 on iOS We request clarification of the supported Core Bluetooth API contract for one specific call: publishing the Bluetooth Low Energy HID Report Reference descriptor (0x2908) using CBMutableDescriptor on iOS. Our iPhone application uses CBPeripheralManager to publish a Human Interface Device over GATT Profile (HOGP) service for an iPad. Its Report characteristics use two-byte Report Reference values containing the report ID and report type. The relevant call is: let reportReference = CBMutableDescriptor( type: CBUUID(string: "00002908-0000-1000-8000-00805F9B34FB"), value: Data([0x01, 0x01]) )The initializer documentation lists only CBUUIDCharacteristicUserDescriptionString and CBUUIDCharacteristicFormatString as supported types. The iPhoneOS 27.2 SDK CBDescriptor.h also limits supported mutable descriptors to those types. This appears to exclude Report Reference. Is constructing and publishing 0x2908 in this way officially supported on iOS? If yes, please identify the supported OS versions, value format, restrictions, and an authoritative document or sample. Does spelling the assigned UUID in its full Bluetooth-base 128-bit form change the support contract? If it is unsupported, please confirm that runtime acceptance should not be relied on, and whether a documentation correction or API enhancement request is appropriate. Existing physical-device records from the full application include remote descriptor reads and notification subscriptions through an independent Central application. The owner also reports successful input, automatic reconnection and a 60-minute session after initiating a connection with nRF Connect. These are observations, not evidence of a supported API contract or a verified bonding sequence. They are not results from the attached reduced sample. The attached ReportReferenceProbe.swift isolates construction and an add-service request. It does not advertise or send input and is not a complete HOGP implementation. It has been compiled to an object file against the iPhoneOS SDK but has not been linked, installed or run on a device. No runtime error or success is claimed for it. A didAdd error would not, by itself, identify the descriptor as the rejected attribute because other required HID attributes are omitted. A successful callback would not prove official support or remote visibility. Please answer the API-support question independently of our observed interoperability. We are not asking for private APIs or an App Review approval prediction. Attachments: ReportReferenceProbe.swift, README.en.md, ENVIRONMENT.en.md. References: https://developer.apple.com/documentation/corebluetooth/cbmutabledescriptor https://developer.apple.com/documentation/corebluetooth/cbmutabledescriptor/init(type:value:)
1
0
47
3d
Healthkit forces 30 days of data or all data
I feel like this should be a bug report but at the very least it is a bad design decision. Confirmed by this documentation Authorizing access to health data Apple is now only allowing the backfill of either 30 days or all data. This is ridiculous as this amounts to all or nothing. We used to sync 90 days worth of data as that was enough to establish trends from the start, 30 days wasn't enough. Now our only option is to backfill years worth of data that is going to bloat our database unacceptably. Could somebody please explain to me the logic behind this? We should absolutely have the ability to choose the backfill window that meets our requirements. My app has been doing the initial backfill for over an hour now and I am storing 100Ks of rows of data I don't want.
1
0
115
3d
APNs delivery when the device has both cellular and Wi-Fi: which connection gets a pending push?
We're investigating alert pushes (priority 10, mutable-content, short expiration) that occasionally arrive 2-4 minutes late, usually around a cellular -> Wi-Fi handover. The provider gets HTTP 200 immediately. What we've observed with the APNs logging profile: apsd logs mention "dual channel is enabled" and "Connected on N interfaces", and per-interface states for WWAN and NonCellular. When we silently break the device's push connection (no RST), the device notices via a keep-alive timeout, reconnects (falling back to 443 when 5223 is blocked), and pending pushes arrive within ~0.3s of the new connection. In the field, a push sent later can arrive first: push 1 is held ~2-3 minutes while push 2, sent ~60s after it, arrives over Wi-Fi in ~2s. Questions: Can a device hold APNs connections over cellular and Wi-Fi at the same time, and if so, how does APNs choose which one to deliver a push on? If a push was sent on one connection and isn't acknowledged, does APNs keep retrying on that same connection until it times out, or does it move the push to another live connection for the same device? What is the retry/backoff behaviour for an unacknowledged push (intervals, any jitter, the timeout before it's re-queued), and does that schedule reset when the device opens a new connection? On the device side, how does apsd back off between reconnect attempts after consecutive failures, and can anything (for example network changes) cut that wait short? Anything a provider can do to reduce this (for example apns-expiration choices), or is this expected best-effort behaviour? Separate from the questions: I've been genuinely impressed by how resilient the push connection is. Even when I silently killed the connection, the device noticed, fell back to another port, and APNs delivered the pending pushes within a fraction of a second of reconnecting. It's an amazing piece of engineering and I wish I got to see behind the curtain.
1
0
62
3d
Can an iOS CarPlay app reliably identify the active head unit to enable features on approved units only?
We’re developing, an iOS navigation app with CarPlay support, for a managed vehicle fleet. We want to enable certain in-app features only when the application is running on an approved physical CarPlay head unit. The allowlist needs to distinguish individual units, including several units of the same make and model. The same iPhone may be used in both approved and unapproved vehicles. This application already uses CPTemplateApplicationSceneDelegate to detect when its CarPlay scene connects or disconnects. The scene’s persistentIdentifier is scoped to the UIKit scene session. We’re looking for a stable identity that we can reliably associate with the head unit hosting the current CarPlay session. Is there a supported iOS API or Apple-approved entitlement that lets a third-party navigation app identify the currently active physical CarPlay head unit? Ideally, the identifier would persist across reconnects and be available over both wired and wireless CarPlay. If this requires manufacturer cooperation, is an iAP2 protocol exposed through ExternalAccessory and EASession the recommended approach? Can the app reliably determine that the EAAccessory it is communicating with is the same head unit hosting the current CarPlay session, or would the manufacturer need to provide that binding in firmware? Can an existing third-party navigation app use this integration with an OEM partner, or is it reserved for apps published by the vehicle manufacturer? Which entitlement or Apple program would apply? The use case is to gate specific features inside this application while keeping the standard CarPlay experience available. We can request the required entitlements and work with the hardware vendor if needed. Any guidance on the supported integration path or the appropriate Apple team to contact would be appreciated.
1
0
67
3d
How does the driverkit serve as a bridge between hardware and the system?
I want to use DriverKit to develop a USBDriver, which serves as a bridge between USB devices and the system. All messages between USB devices and the system will be forwarded through the USBDriver. Can anyone give me some tips or suggestions? What API should I use? I couldn't find anything like this in the documentation or sample code. class MyUSBDriver: public IOUserClient { public: virtual bool init() override; virtual kern_return_t Start(IOService * provider) override; virtual kern_return_t Stop(IOService * provider) override; virtual void free() override; virtual kern_return_t GetRegistryEntryID(uint64_t * registryEntryID) override; virtual kern_return_t NewUserClient(uint32_t type, IOUserClient** userClient) override; virtual kern_return_t ExternalMethod(uint64_t selector, IOUserClientMethodArguments* arguments, const IOUserClientMethodDispatch* dispatch, OSObject* target, void* reference) override; }; I am now able to retrieve the device descriptor in the Start method IOUSBHostDevice *device = OSDynamicCast(IOUSBHostDevice, provider); if (device) { const IOUSBDeviceDescriptor *deviceDescriptor = device->CopyDeviceDescriptor(); if (deviceDescriptor) { uint16_t idVendor = deviceDescriptor->idVendor; uint16_t idProduct = deviceDescriptor->idProduct; uint8_t iSerialNumber = deviceDescriptor->iSerialNumber; IOUSBHostFreeDescriptor(deviceDescriptor); } }
1
0
921
3d
StoreKit Sandbox returns 0 products after TN3186 checks — catalog association issue?
We are testing two auto-renewable subscriptions for a new iOS app. In Apple Sandbox, StoreKit 2 Product.products(for:) always returns an empty array. Legacy SKProductsRequest independently reports both identifiers as invalid. Environment: Physical iPhone, iOS 26.5 Xcode development build with automatic signing Storefront.current = USA (143441) canMakePayments = true No StoreKit Configuration file in the Run scheme Direct native StoreKit 2 diagnostics, without a third-party purchase SDK TN3186 checks completed: Explicit Bundle ID matches the App Store Connect app, installed app, and provisioning profile In-App Purchase is enabled for the App ID Developer membership, Paid Apps Agreement, banking, and tax are active One subscription group with monthly and yearly subscriptions is visible Pricing, localizations, and availability are configured Neither subscription is Rejected or Developer Action Needed The scheme is using real Sandbox data, not local StoreKit testing Results: StoreKit 2 batch query: rawCount = 0 SKProductsRequest: valid = []; both identifiers are invalid StoreKit 2 individual monthly query: 0 StoreKit 2 individual yearly query: 0 No exception; failure occurs during product discovery Related reports: https://developer.apple.com/forums/thread/839313 — TN3186 verified and USA storefront valid, but still 0 products; no replies https://developer.apple.com/forums/thread/841722 — Apple Commerce mentioned Rejected or Developer Action Needed states; ours have neither https://developer.apple.com/forums/thread/820656 — Apple DTS confirmed first subscriptions do not require review before Sandbox testing Apple Developer Support referred us to TN3186, and we verified every applicable item. The individual subscription detail route in App Store Connect also intermittently remains on a loading indicator although the group and both records are visible. Could an App Store Commerce or StoreKit engineer check whether the app-to-IAP catalog association is populated correctly on Apple's side, or advise an official escalation path to have the Sandbox catalog reprocessed? Exact account, app, product, device, email, and support-case identifiers are omitted from this public post and can be supplied privately through Apple Support or Feedback Assistant.
1
0
522
3d
Support requested: Notification Service Extension Filtering entitlement requests blocking app updates
Hello, We’re seeking assistance with two pending Notification Service Extension Filtering Entitlement Requests, both submitted on October 27, 2026: HX7DQ5G2R4 3T2KH34RB3 The requests cover our production app and its TestFlight beta. Our production app previously had this entitlement, but after transferring it to a new Apple Developer account, we needed to request it again. Our app provides end-to-end encrypted messaging. Its notification service extension decrypts incoming content and determines whether a visible notification is appropriate. The entitlement is needed to suppress notifications for events that don’t require a user-facing alert. The full technical justification is included in our submissions. While these requests are pending, we’re unable to release updates and bug fixes to important clients who rely on the app. Could Apple staff help us check the status of these requests or direct us to the appropriate support channel? Please let us know if any additional information is needed to move the review forward. Thank you.
0
0
84
3d
macOS 27/APFS: Supported ACL Absence Verification When acl_get_fd_np Returns ENOENT
Subject: Supported fail-closed ACL absence verification on macOS 27.0.1 / APFS Environment: macOS 27.0.1, build 26A434; APFS; installed macOS 27.0 SDK. We need a supported, documented way to determine whether an existing filesystem object has no effective ACL entries, while rejecting genuine retrieval failures and unsupported or unavailable ACL evidence. We are seeking clarification of the public interface contract, not alleging an Apple defect. For existing directory and regular-file fixtures, pathname metadata and descriptor metadata identify the same object. Errno is cleared immediately before each native call and captured immediately afterward. ACL retrieval uses ACL_TYPE_EXTENDED: acl_get_file(path, ACL_TYPE_EXTENDED) acl_get_fd_np(fd, ACL_TYPE_EXTENDED) On fresh objects, both return NULL with ENOENT. Explicit one-entry fixture ACLs are retrieved successfully. Explicit zero-entry fixture ACLs can also yield NULL/ENOENT, while attribute queries return a serialized zero-entry ACL. The attribute queries use getattrlist() and descriptor-bound fgetattrlist(), requesting ATTR_CMN_RETURNED_ATTRS | ATTR_CMN_EXTENDED_SECURITY, with FSOPT_NOFOLLOW | FSOPT_REPORT_FULLSIZE and WITHOUT FSOPT_PACK_INVAL_ATTRS. Buffer lengths, variable-reference bounds and returned-attribute validity are checked. For the existing directories of interest, both calls succeed but omit the ATTR_CMN_EXTENDED_SECURITY returned bit. Explicit populated and zero-entry fixture records do set the bit. APFS reports valid VOL_CAP_INT_EXTENDED_SECURITY support; we do not assume that volume capability proves per-object ACL availability. On macOS 27.0.1, build 26A434, using APFS, which supported interface and documented conditions allow software to distinguish an absent ACL from unavailable or unsupported ACL evidence when descriptor-bound attribute queries succeed but omit ATTR_CMN_EXTENDED_SECURITY and native ACL getters return ENOENT for an existing object? Please clarify: Whether ENOENT has a supported ACL-absence interpretation, and under exactly which checked conditions. Whether an omitted extended-security attribute can establish ACL absence, rather than unavailable or unsupported evidence. How explicit zero-entry ACLs differ from absent ACL records through supported interfaces. How KAUTH_FILESEC_NOACL should be interpreted through supported APIs. How genuine retrieval failures, including permission, I/O, allocation and unsupported-operation errors, must remain distinguishable. Whether a supported descriptor-bound verification method exists that preserves fail-closed security checks and object identity binding; please identify its guarantees and limitations regarding pathname/ancestor changes and later operations. Whether relevant behavior is specific to this macOS/APFS version. Please identify the applicable public documentation or supported verification sequence. We do not want to modify permissions, synthesize ACLs on target objects, treat invalid-attribute defaults as real evidence, or accept ambiguous omission/ENOENT as success. Existing ownership, mode and confinement checks must remain separate mandatory checks. If no public API can make this distinction reliably, please state that limitation.
15
0
582
3d
Export semantics and non-hydrating materialization proof for File Provider-tagged project directories
On macOS 26.7.1 with Xcode 26.6 on Apple silicon, several directories in a development tree carry the private extended-attribute names com.apple.fileprovider.dir#N and com.apple.fileprovider.fpfs#P. On this host, the supported xattr_flags_from_name decoder returns XATTR_FLAG_NEVER_PRESERVE for the first exact name and XATTR_FLAG_NO_EXPORT for the second exact name. Apple's public API defines those flag meanings; the literal name encoding and the attributes' private values are not treated as a public semantic contract. We want a self-contained APFS compilation-input tree using descriptor-based COPYFILE_DATA for regular files, with independent inventory and hash verification and no private-xattr copying. For this compilation-only export, does Apple support deliberate non-preservation when xattr_flags_from_name returns XATTR_FLAG_NEVER_PRESERVE, and when it returns XATTR_FLAG_NO_EXPORT for a governed SHARE operation? Separately, what public, non-hydrating API can establish that every required file is already fully materialized and that export will not trigger provider downloads? Does enumeratorForMaterializedItems establish that state for a closed descendant tree, or must each item be checked by another supported API? Can reading or hashing an item itself cause materialization? We are asking about documented APIs, supported export behavior, and security postconditions. We are not asking to decode or preserve private attribute values. No production paths, source code, credentials, datasets, or personal information are included.
4
0
394
3d
Missing entitlement for API HomeKit error
During a test run of my HomeKit application in Xcode, after some time the app did run smoothly, I've started for one characteristic to get a pretty weird error in the readValueWithCompletionHandler: callback block: Error Domain=HMErrorDomain Code=80 "Missing entitlement for API." UserInfo={NSLocalizedFailureReason=Handler does not support background access, NSLocalizedDescription=Missing entitlement for API.} The application was launched just a couple of hours ago and the profile is still OK (though it will expire very inconveniently soon): 1044 ocs /tmp> security cms -D -i /Users/ocs/Library/Developer/Xcode/DerivedData/HomeObserverNA-hkazqlfbeuucvybpdzdgosyhhxnx/Build/Products/Debug-maccatalyst/HomeObserverNA.app/Contents/embedded.provisionprofile -o /tmp/ppp.plist 1045 ocs /tmp> plutil -extract ExpirationDate raw -o - /tmp/ppp.plist 2026-10-15T14:04:02Z 1046 ocs /tmp> Note please that immediately after launch (and for some time after that) the value was read in through the same code without any problem. Strangely enough, when I've switched the device through the Home application, I've got the update planned through enableNotification:completionHandler: all right. and the error stopped occurring, readValueWithCompletionHandler: from that moment on again works as presumed. How can I fix the problem, what's wrong in my app? Thanks!
25
0
1k
3d
Can a watchOS alarm show a custom wake screen instead of the system Open/Stop alert?
I’m developing a watchOS gentle-wake alarm using WKExtendedRuntimeSession and repeating haptics. When the app determines it is time to wake the user, I want the watch to present the app’s custom wake screen immediately. That screen includes a Stop control. The goal is for the custom screen to be the alarm experience, rather than requiring the user to tap Open on the system’s Open/Stop alert or having that system alert replace the custom screen. In hardware tests of my watchOS app (version 0.1, build 10) on November 9, 2026, I observed the system’s Open/Stop alert during the alarm. After selecting Open, the custom UI appeared, but the system alert returned after the app subsequently became inactive while the alarm session was still running. Test environment Apple Watch Series 11, watchOS 27.2 (24S118) Xcode 27.2 (27B52), watchOS 27.2 SDK Watch unlocked, Always On enabled, no attached debugger The app schedules the session with start(at:), calls notifyUser(hapticType:repeatHandler:) once, and presents a SwiftUI fullScreenCover with the wake interface and Stop button. Stop invalidates the session. In the 15-second Wake Duration test, logs showed reduced luminance after 15 seconds and inactivity about one second later. I observed the Open/Stop alert return twice after selecting Open. In the 70-second test, reduced luminance occurred 70 seconds after activation, followed by inactivity. Neither test logged a duplicate notifyUser call, process restart, or disappearance of the custom view before session termination. The logs establish lifecycle timing, but do not directly record system-alert presentation. Questions Is there a supported watchOS API or alarm architecture that can present a third-party app’s custom wake screen immediately when its alarm starts, without first showing or subsequently replacing it with the system Open/Stop alert? If so, what lifecycle, presentation, and background-haptic requirements apply, including when the app is inactive or the watch is in Always On mode? If this isn’t supported, is the system alert mandatory for WKExtendedRuntimeSession alarms, and what is the recommended alternative? Would AlarmKit with an iPhone companion change what can be presented on the watch? The custom screen would provide a clear way to stop the alarm. I’m not asking to remove the user’s ability to stop it or to keep the display at full brightness indefinitely. I also prepared a focused Watch-only sample isolating the runtime session, repeating haptics, custom presentation, and lifecycle logging. It builds successfully but has not been tested on hardware. The observations above are from the app, not the sample.
1
0
117
3d
Logitech MX Brio 4K webcam detected but no video on macOS 27 Golden Gate (Mac Studio M4)
Since upgrading to macOS 27 Golden Gate, my Mac Studio (M4) recognises my Logitech MX Brio 4K webcam, but no video feed is displayed. The camera appears to be detected by the system, but the video signal does not show up in: FaceTime Photo Booth Logitech Options+ I've spent quite a bit of time troubleshooting the issue, including following diagnostic steps suggested by Siri and Copilot, but everything points to a potential macOS-related problem rather than a hardware or configuration issue. Has anyone else experienced this with the MX Brio or other webcams on macOS 27 Golden Gate? I reported the issue to Apple through the Feedback app when Beta 1 was released, but so far I haven't received a response or found a workaround. Any insights or suggestions would be greatly appreciated. Thanks!
3
2
492
3d
Subscriptions suddenly stopped working in all my apps – StoreKit returns 0 products
Since November 5, in-app subscriptions have suddenly stopped working in all three of my apps on the App Store. Everything worked perfectly before, and no changes were made to the apps. The subscription purchase buttons no longer display prices, only a dash ("–"). Existing apps can still be downloaded normally. I reproduced the problem in Xcode on my own device. StoreKit reports: STOREKIT: Received 0 products STOREKIT: Invalid IDs = ( "TEE_year", "TEE_month", "TEE_week" ) All subscription products are still configured in App Store Connect, and the agreements appear to be active. Interestingly, the problem started around the time I accepted updated Apple agreements and changed my address in my developer account. I don't know whether this is related. Several customers have already independently reported the same problem, so this is not limited to my own device or Apple ID. I strongly suspect an App Store Connect or StoreKit backend issue rather than an app-specific programming error. I've contacted Apple Developer Support (case ID is 30000008123797) but haven't received a solution yet. Has anyone else experienced subscriptions suddenly becoming unavailable across multiple apps? Could this be related to updated agreements or account information?
1
0
138
3d
Supported backend recovery after RESCIND_CONSENT
We are integrating age assurance into two iOS apps with authenticated backend services. We need to handle one specific transition: a parent revokes app consent, then subsequently grants consent again. Our implementation can verify App Store Server Notifications V2 and associate a RESCIND_CONSENT event with its appTransactionId, app and environment. Our backend can then recognize that withdrawal. We do not treat a newly signed AppTransaction, an absent withdrawal record, or acceptance of our Terms as renewed parental permission. We also keep PermissionKit significant-update responses separate from permission to use the app itself. We reviewed the Age Assurance Q&A, Requesting people share their age range with your app, AppTransaction.appTransactionID, and Testing age assurance in sandbox. The documentation explains withdrawal notifications and app-launch prevention. We have not established the supported backend recovery signal after a parent subsequently approves the app again. What supported API, signed field or server notification establishes that later approval for the same appTransactionId? If there is no server-verifiable signal, what supported architecture should a developer use to restore backend access without mistaking a replayed transaction or a significant-update response for renewed app consent? Please identify the supported OS/API versions and a sandbox procedure to exercise withdrawal followed by reapproval, including whether the appTransactionId remains the same. Our current verification uses synthetic withdrawal events and isolated backend tests; we have not yet verified this transition using a genuine parent/child Sandbox Apple Account setup. We are asking about supported API behavior, not reporting an observed Apple service failure or requesting legal advice. References: https://developer.apple.com/support/age-assurance/ https://developer.apple.com/documentation/declaredagerange/requesting-people-share-their-age-range-with-your-app https://developer.apple.com/documentation/storekit/apptransaction/apptransactionid https://developer.apple.com/documentation/storekit/testing-age-assurance-in-sandbox
0
0
38
3d
Subject: Critical APFS Data Loss Bug & Error 1110 Loop during official Finder Update on iPhone 14 (A15)
Hello, I am requesting an engineering escalation regarding a critical bug in Apple's APFS update pipeline that trapped an iPhone 14 (A15, 128 GB) in recovery mode during an official Finder update from iOS 16.6 to iOS 18 (27.2.1, 24B156) on macOS 14.5. The device hardware is 100% healthy (Apple MRI diagnostics all green), the passcode is known, and 101,175 MB (341,967 files) of user data remain intact on the flash storage. However, the device cannot boot or complete an update due to a corruption caused by Apple's own restore tools. --- ### What Happened (Verified in Logs): 1. **Initial Full Storage State:** The device had ~105 GB utilized and was updated via Finder using "Update" (not Restore). 2. **Destructive fsck Behavior:** In pass 3, the restore ramdisk ran `/sbin/fsck_apfs -dy /dev/disk2`. On the nearly full container, fsck erroneously flagged 8,182 live omap mappings as "orphans" and deallocated them, causing extent-ref b-tree node `0x10bb3` to be zeroed out (TRIMmed by the flash controller). 3. **Split Failure:** In pass 4, the iOS 18 System volume installed and sealed, but `split_data_volume` failed in 4 seconds when `apfs_migrator` encountered block `0x10bb3` (`obj_read` checksum failure returning EILSEQ / error 92). 4. **False Error 1110 Loop:** Every subsequent attempt now halts immediately at `space_checks` with Error 1110. --- ### Reverse Engineering Proof: Disassembly of `restored_update` (arm64e, VA 0x10001afcc / 0x10001b0e8) confirms a major error-handling bug: When `splitter_dump` encounters the unreadable block `0x10bb3`, it fails with `EILSEQ` (92). Instead of handling this error, `restored_update` executes: `mov x19, #-1; mov x0, x19; ret` The caller receives `-1 bytes of free space`, logs: "Data volume requires splitting. Splitter will leave -1 bytes of free space after completion. Current free space on device: 6620069888 bytes. Insufficient space on device to run splitter" and aborts with **CHECKPOINT FAILURE:(FAILURE:1110)**. The device is NOT out of space (it has 6.3 GB free); it is blocked solely because `restored_update` misinterprets an EILSEQ filesystem error as negative free space. --- ### Current State & Request: - The encryption keys and SEP/gigalocker are intact (`gigalocker: ONLINE`). - In the restore ramdisk, `/dev/disk2s2` mounts cleanly as read-write on `/mnt2`. - Zero APFS snapshots remain on the volume, meaning the extent-ref tree is theoretically fully reconstructible from the valid fsroot inode tree. I am requesting assistance from CoreOS / APFS engineering: 1. Is there an engineering update ramdisk or build that can bypass the `splitter_dump` EILSEQ check, or rebuild the extent-ref tree, so the update can finalize? 2. Alternatively, can an engineering liaison facilitate a non-destructive extraction given that the volume mounts read-write and the user passcode is known? I can immediately provide full terminal transcripts, Finder updater logs (`iPhoneUpdater-*.log`), and disassembly details. Thank you, Samuel Journo
Replies
1
Boosts
0
Views
106
Activity
3d
macOS APFS: com.apple.macl and UF_TRACKED appear after creating a hard link — safe file replacement and rollback?
I'm investigating an unexpected metadata change during a controlled file deployment on macOS. Environment and observed state Two regular configuration files are used by a local service. Before replacement, the first file had: SHA-256: verified. File flags: 0. Extended attributes: none. Hard-link count: 1. Owner/group: 501/20. Permissions: 0644. ACL: empty. A backup procedure created a hard link to preserve the original inode before replacing the active pathname with an independently created file. Immediately after creating and verifying the hard link, the original file was observed with: The same SHA-256 and inode. Flags: 64 (UF_TRACKED). Extended attribute: com.apple.macl. Hard-link count: 2. No file content was replaced. The procedure stopped because the metadata no longer matched the original baseline. Additional observations Other backup methods also encountered unexpected metadata changes during destination creation. Tests using renamex_np with RENAME_SWAP successfully exchanged and restored artificial files with flags 0 and empty extended attributes. A test with artificial files already containing com.apple.provenance also succeeded. We could not reproduce the specific UF_TRACKED + com.apple.macl + two-hard-link state in an isolated fixture using ordinary documented operations. The operational original and its second hard link currently share the same inode. No attempt has been made to remove the protected attribute or change its flags. Questions for Apple filesystem/security specialists Under what documented circumstances can creating a hard link or related Finder/TCC document-tracking behavior cause UF_TRACKED and com.apple.macl to appear on an existing file? Are these metadata changes expected for a file accessed through a user-authorized Documents location? What supported mechanism can preserve the current original inode and provide a verifiable rollback when replacing its active pathname? Is renamex_np(..., RENAME_SWAP) appropriate for this situation, and what special considerations apply to the existing second hard link and protected extended attributes? What verification criteria would you recommend before permitting a production replacement? I am looking for a documented, reversible procedure that preserves macOS security protections. I do not want to disable SIP, forcibly remove com.apple.macl, or bypass TCC. I can provide sanitized metadata comparisons and a minimal reproduction if needed.
Replies
1
Boosts
0
Views
153
Activity
3d
watchOS — Continuous Core Motion monitoring in the background for independent fall detection
I'm developing an independent fall-detection application for Apple Watch using Core Motion (CMMotionManager) at 20 Hz. The goal is to identify potential falls using accelerometer, gyroscope and orientation data, then notify nominated family contacts. The application is deliberately independent of Apple's built-in Fall Detection and Emergency SOS. Test environment Physical Apple Watch running watchOS 27.2 Xcode 27.2 Core Motion device-motion callbacks on a dedicated serial OperationQueue Motion processing on the MainActor Tests performed without the Xcode debugger attached Observed results With the Watch display awake: 2,300 processed samples Longest sensor timestamp gap: 0.05 seconds Longest callback arrival gap: 0.66 seconds Callback interruptions over one second: 0 With the Watch dimmed/backgrounded: 3,229 processed samples Longest sensor timestamp gap: 0.30 seconds Longest callback arrival gap: 29.11 seconds Callback interruptions over one second: 6 Maximum sample delivery lag: 29.065 seconds The motion timestamps appear nearly continuous, but callback delivery becomes substantially delayed after the app enters the background. The monitoring flag remains true, and no explicit call to stop motion updates occurs when the app becomes inactive. Questions Is there an Apple-supported background execution mechanism or entitlement allowing a third-party watchOS app to continuously process accelerometer and gyroscope data for independent fall detection, without requiring an active workout session? Would CMBatchedSensorManager provide any useful background delivery capability for this application, or would its callbacks remain subject to normal watchOS suspension? Is there a recommended architecture for detecting a potential fall and initiating a timely family notification while the Watch app is backgrounded, without relying on Apple's built-in Fall Detection or Emergency SOS? We understand that workout sessions and extended runtime sessions have specific intended purposes. We want to implement this correctly rather than use an unrelated background mode to prevent suspension. Any guidance from Apple engineers or developers experienced with watchOS background Core Motion processing would be greatly appreciated.
Replies
2
Boosts
0
Views
109
Activity
3d
NEURLFilterManager: inconsistent per-domain blocking (some sites never block, one flaps) - confirmed PIR database is correct
Hello, Some context: DropBet is an app that helps people with gambling addiction stay off gambling sites and apps, using NEURLFilterManager/PIR to block a large list of known gambling domains system-wide. For a lot of our users this filter is a core part of their recovery > reliability really matters here. Since fixing an unrelated HPKE encryption bug (separate thread, now closed), the filter works end-to-end for the first time, but blocking is inconsistent per domain in a way I can't explain from my side: winamax.fr and the Winamax app: blocked reliably, every single time > clean "connection failed" style block, confirmed to load fine with protection off. unibet.fr and betclic.fr: never blocked, consistently > confirmed even after a full device reboot (rules out stale caching), and confirmed identical across both Safari and Chrome on iOS tested side-by-side (so not browser-specific). olybet.fr: flaps > the page reloads every 2-3 seconds with protection on, also identical across both browsers. Confirmed this only happens with the filter enabled (tested toggling protection off/on against the same page). unibet.fr auto-redirects into the native Unibet app via a Universal Link before the page loads, unlike betclic.fr which stays in the browser > different code path, possibly relevant. To rule out any issue on our end, I wrote a standalone test that queries our deployed PIR database shards directly - bypassing OHTTP, the app, and the device entirely - for all of the domains above plus their www. variants. All of them correctly return the blocked value, no exceptions, including unibet.fr and betclic.fr which never block on the actual device. So the database, the PIR protocol implementation, and the server are confirmed correct for every domain I've tested. This points at something in how NEURLFilterManager/ciphermld applies a correctly-received PIR verdict on-device - possibly related to query batching, an evaluation-key edge case, or Universal Link handling bypassing the filter before a web request is even made. Is there anything you can share about how the client applies results once decrypted, or known issues around any of this?
Replies
7
Boosts
0
Views
347
Activity
3d
StoreKit introductoryOfferEligibility: safe retry after JWS expiration
How should a server safely retire or renew an unused JWS for Product.PurchaseOption.introductoryOfferEligibility(compactJWS:) after cancellation or interruption? Our application allows a first-purchase discount once per application account across payment platforms. We bind the signed eligibility request to a verified Apple app transaction, product, and purchase attempt, persist the exact JWS, and reuse it for the same attempt. Once a paid purchase is verified, we consume the application's eligibility. We do not automatically issue another nonce after cancellation, a signature error, or an empty transaction history. Apple's JWS documentation describes a one-time nonce and expiration calculated from iat, and says not to include exp: https://developer.apple.com/documentation/storekit/generating-jws-to-sign-app-store-requests I could not find the lifetime or a supported retirement/renewal procedure for the introductory-offer-eligibility audience. Keeping an unusable authorization forever would prevent the customer from trying another checkout; replacing it without retiring the original might leave two redeemable authorizations. What we observed Environment: Xcode 27.2 (27B52), macOS 26.6.2, physical iPhone 16 with iOS 27.0, Apple Sandbox. Verify the Apple-signed AppTransaction and issue one eligibility JWS. Start the purchase using that JWS, then cancel the payment sheet (userCancelled). Terminate and relaunch the app without resetting purchase history or replacing the authorization. Retry the same product and Apple account using the byte-for-byte identical JWS. Complete the Sandbox purchase and verify the Apple-signed transaction on an isolated server. The successful verification happened about 164 seconds after issuance. This is one successful cancellation/retry observation, not a reproduced expiration failure or proof of a general validity/nonce-consumption rule. It also did not verify our intended introductory price. The purchase call uses the persisted value: let result = try await product.purchase(options: [ .introductoryOfferEligibility(compactJWS: existingJWS) ])Supported lifecycle questions What is the validity period derived from iat, including clock-skew allowances and any Sandbox/production differences? Which API or documented error can establish that a previously issued authorization is definitively unusable, rather than merely absent from transaction history? When is the nonce consumed, and what happens after userCancelled, interruption, pending approval, expiration, or an uncertain result? Is invalidOfferSignature specific enough to distinguish expiration from consumption, account mismatch, or a bad signature? Is it supported to keep the same nonce and all bindings, update only iat, and re-sign? If so, is one-time use enforced across every version and for what retention period? If renewal requires a new nonce, how can the prior authorization be invalidated first? Is there another recommended recovery flow that prevents duplicate redemption without indefinitely blocking checkout? DTS directed us to ask this lifecycle question on the forums. A sanitized minimal Xcode project was already supplied privately to DTS; it demonstrates the observed cancel/relaunch/same-JWS retry, not an expiration failure. We would appreciate a supported procedure or documentation reference.
Replies
1
Boosts
0
Views
84
Activity
3d
Supported publication of HID Report Reference descriptor 0x2908 on iOS
Supported publication of HID Report Reference descriptor 0x2908 on iOS We request clarification of the supported Core Bluetooth API contract for one specific call: publishing the Bluetooth Low Energy HID Report Reference descriptor (0x2908) using CBMutableDescriptor on iOS. Our iPhone application uses CBPeripheralManager to publish a Human Interface Device over GATT Profile (HOGP) service for an iPad. Its Report characteristics use two-byte Report Reference values containing the report ID and report type. The relevant call is: let reportReference = CBMutableDescriptor( type: CBUUID(string: "00002908-0000-1000-8000-00805F9B34FB"), value: Data([0x01, 0x01]) )The initializer documentation lists only CBUUIDCharacteristicUserDescriptionString and CBUUIDCharacteristicFormatString as supported types. The iPhoneOS 27.2 SDK CBDescriptor.h also limits supported mutable descriptors to those types. This appears to exclude Report Reference. Is constructing and publishing 0x2908 in this way officially supported on iOS? If yes, please identify the supported OS versions, value format, restrictions, and an authoritative document or sample. Does spelling the assigned UUID in its full Bluetooth-base 128-bit form change the support contract? If it is unsupported, please confirm that runtime acceptance should not be relied on, and whether a documentation correction or API enhancement request is appropriate. Existing physical-device records from the full application include remote descriptor reads and notification subscriptions through an independent Central application. The owner also reports successful input, automatic reconnection and a 60-minute session after initiating a connection with nRF Connect. These are observations, not evidence of a supported API contract or a verified bonding sequence. They are not results from the attached reduced sample. The attached ReportReferenceProbe.swift isolates construction and an add-service request. It does not advertise or send input and is not a complete HOGP implementation. It has been compiled to an object file against the iPhoneOS SDK but has not been linked, installed or run on a device. No runtime error or success is claimed for it. A didAdd error would not, by itself, identify the descriptor as the rejected attribute because other required HID attributes are omitted. A successful callback would not prove official support or remote visibility. Please answer the API-support question independently of our observed interoperability. We are not asking for private APIs or an App Review approval prediction. Attachments: ReportReferenceProbe.swift, README.en.md, ENVIRONMENT.en.md. References: https://developer.apple.com/documentation/corebluetooth/cbmutabledescriptor https://developer.apple.com/documentation/corebluetooth/cbmutabledescriptor/init(type:value:)
Replies
1
Boosts
0
Views
47
Activity
3d
Healthkit forces 30 days of data or all data
I feel like this should be a bug report but at the very least it is a bad design decision. Confirmed by this documentation Authorizing access to health data Apple is now only allowing the backfill of either 30 days or all data. This is ridiculous as this amounts to all or nothing. We used to sync 90 days worth of data as that was enough to establish trends from the start, 30 days wasn't enough. Now our only option is to backfill years worth of data that is going to bloat our database unacceptably. Could somebody please explain to me the logic behind this? We should absolutely have the ability to choose the backfill window that meets our requirements. My app has been doing the initial backfill for over an hour now and I am storing 100Ks of rows of data I don't want.
Replies
1
Boosts
0
Views
115
Activity
3d
APNs delivery when the device has both cellular and Wi-Fi: which connection gets a pending push?
We're investigating alert pushes (priority 10, mutable-content, short expiration) that occasionally arrive 2-4 minutes late, usually around a cellular -> Wi-Fi handover. The provider gets HTTP 200 immediately. What we've observed with the APNs logging profile: apsd logs mention "dual channel is enabled" and "Connected on N interfaces", and per-interface states for WWAN and NonCellular. When we silently break the device's push connection (no RST), the device notices via a keep-alive timeout, reconnects (falling back to 443 when 5223 is blocked), and pending pushes arrive within ~0.3s of the new connection. In the field, a push sent later can arrive first: push 1 is held ~2-3 minutes while push 2, sent ~60s after it, arrives over Wi-Fi in ~2s. Questions: Can a device hold APNs connections over cellular and Wi-Fi at the same time, and if so, how does APNs choose which one to deliver a push on? If a push was sent on one connection and isn't acknowledged, does APNs keep retrying on that same connection until it times out, or does it move the push to another live connection for the same device? What is the retry/backoff behaviour for an unacknowledged push (intervals, any jitter, the timeout before it's re-queued), and does that schedule reset when the device opens a new connection? On the device side, how does apsd back off between reconnect attempts after consecutive failures, and can anything (for example network changes) cut that wait short? Anything a provider can do to reduce this (for example apns-expiration choices), or is this expected best-effort behaviour? Separate from the questions: I've been genuinely impressed by how resilient the push connection is. Even when I silently killed the connection, the device noticed, fell back to another port, and APNs delivered the pending pushes within a fraction of a second of reconnecting. It's an amazing piece of engineering and I wish I got to see behind the curtain.
Replies
1
Boosts
0
Views
62
Activity
3d
Can an iOS CarPlay app reliably identify the active head unit to enable features on approved units only?
We’re developing, an iOS navigation app with CarPlay support, for a managed vehicle fleet. We want to enable certain in-app features only when the application is running on an approved physical CarPlay head unit. The allowlist needs to distinguish individual units, including several units of the same make and model. The same iPhone may be used in both approved and unapproved vehicles. This application already uses CPTemplateApplicationSceneDelegate to detect when its CarPlay scene connects or disconnects. The scene’s persistentIdentifier is scoped to the UIKit scene session. We’re looking for a stable identity that we can reliably associate with the head unit hosting the current CarPlay session. Is there a supported iOS API or Apple-approved entitlement that lets a third-party navigation app identify the currently active physical CarPlay head unit? Ideally, the identifier would persist across reconnects and be available over both wired and wireless CarPlay. If this requires manufacturer cooperation, is an iAP2 protocol exposed through ExternalAccessory and EASession the recommended approach? Can the app reliably determine that the EAAccessory it is communicating with is the same head unit hosting the current CarPlay session, or would the manufacturer need to provide that binding in firmware? Can an existing third-party navigation app use this integration with an OEM partner, or is it reserved for apps published by the vehicle manufacturer? Which entitlement or Apple program would apply? The use case is to gate specific features inside this application while keeping the standard CarPlay experience available. We can request the required entitlements and work with the hardware vendor if needed. Any guidance on the supported integration path or the appropriate Apple team to contact would be appreciated.
Replies
1
Boosts
0
Views
67
Activity
3d
How does the driverkit serve as a bridge between hardware and the system?
I want to use DriverKit to develop a USBDriver, which serves as a bridge between USB devices and the system. All messages between USB devices and the system will be forwarded through the USBDriver. Can anyone give me some tips or suggestions? What API should I use? I couldn't find anything like this in the documentation or sample code. class MyUSBDriver: public IOUserClient { public: virtual bool init() override; virtual kern_return_t Start(IOService * provider) override; virtual kern_return_t Stop(IOService * provider) override; virtual void free() override; virtual kern_return_t GetRegistryEntryID(uint64_t * registryEntryID) override; virtual kern_return_t NewUserClient(uint32_t type, IOUserClient** userClient) override; virtual kern_return_t ExternalMethod(uint64_t selector, IOUserClientMethodArguments* arguments, const IOUserClientMethodDispatch* dispatch, OSObject* target, void* reference) override; }; I am now able to retrieve the device descriptor in the Start method IOUSBHostDevice *device = OSDynamicCast(IOUSBHostDevice, provider); if (device) { const IOUSBDeviceDescriptor *deviceDescriptor = device->CopyDeviceDescriptor(); if (deviceDescriptor) { uint16_t idVendor = deviceDescriptor->idVendor; uint16_t idProduct = deviceDescriptor->idProduct; uint8_t iSerialNumber = deviceDescriptor->iSerialNumber; IOUSBHostFreeDescriptor(deviceDescriptor); } }
Replies
1
Boosts
0
Views
921
Activity
3d
StoreKit Sandbox returns 0 products after TN3186 checks — catalog association issue?
We are testing two auto-renewable subscriptions for a new iOS app. In Apple Sandbox, StoreKit 2 Product.products(for:) always returns an empty array. Legacy SKProductsRequest independently reports both identifiers as invalid. Environment: Physical iPhone, iOS 26.5 Xcode development build with automatic signing Storefront.current = USA (143441) canMakePayments = true No StoreKit Configuration file in the Run scheme Direct native StoreKit 2 diagnostics, without a third-party purchase SDK TN3186 checks completed: Explicit Bundle ID matches the App Store Connect app, installed app, and provisioning profile In-App Purchase is enabled for the App ID Developer membership, Paid Apps Agreement, banking, and tax are active One subscription group with monthly and yearly subscriptions is visible Pricing, localizations, and availability are configured Neither subscription is Rejected or Developer Action Needed The scheme is using real Sandbox data, not local StoreKit testing Results: StoreKit 2 batch query: rawCount = 0 SKProductsRequest: valid = []; both identifiers are invalid StoreKit 2 individual monthly query: 0 StoreKit 2 individual yearly query: 0 No exception; failure occurs during product discovery Related reports: https://developer.apple.com/forums/thread/839313 — TN3186 verified and USA storefront valid, but still 0 products; no replies https://developer.apple.com/forums/thread/841722 — Apple Commerce mentioned Rejected or Developer Action Needed states; ours have neither https://developer.apple.com/forums/thread/820656 — Apple DTS confirmed first subscriptions do not require review before Sandbox testing Apple Developer Support referred us to TN3186, and we verified every applicable item. The individual subscription detail route in App Store Connect also intermittently remains on a loading indicator although the group and both records are visible. Could an App Store Commerce or StoreKit engineer check whether the app-to-IAP catalog association is populated correctly on Apple's side, or advise an official escalation path to have the Sandbox catalog reprocessed? Exact account, app, product, device, email, and support-case identifiers are omitted from this public post and can be supplied privately through Apple Support or Feedback Assistant.
Replies
1
Boosts
0
Views
522
Activity
3d
Support requested: Notification Service Extension Filtering entitlement requests blocking app updates
Hello, We’re seeking assistance with two pending Notification Service Extension Filtering Entitlement Requests, both submitted on October 27, 2026: HX7DQ5G2R4 3T2KH34RB3 The requests cover our production app and its TestFlight beta. Our production app previously had this entitlement, but after transferring it to a new Apple Developer account, we needed to request it again. Our app provides end-to-end encrypted messaging. Its notification service extension decrypts incoming content and determines whether a visible notification is appropriate. The entitlement is needed to suppress notifications for events that don’t require a user-facing alert. The full technical justification is included in our submissions. While these requests are pending, we’re unable to release updates and bug fixes to important clients who rely on the app. Could Apple staff help us check the status of these requests or direct us to the appropriate support channel? Please let us know if any additional information is needed to move the review forward. Thank you.
Replies
0
Boosts
0
Views
84
Activity
3d
macOS 27/APFS: Supported ACL Absence Verification When acl_get_fd_np Returns ENOENT
Subject: Supported fail-closed ACL absence verification on macOS 27.0.1 / APFS Environment: macOS 27.0.1, build 26A434; APFS; installed macOS 27.0 SDK. We need a supported, documented way to determine whether an existing filesystem object has no effective ACL entries, while rejecting genuine retrieval failures and unsupported or unavailable ACL evidence. We are seeking clarification of the public interface contract, not alleging an Apple defect. For existing directory and regular-file fixtures, pathname metadata and descriptor metadata identify the same object. Errno is cleared immediately before each native call and captured immediately afterward. ACL retrieval uses ACL_TYPE_EXTENDED: acl_get_file(path, ACL_TYPE_EXTENDED) acl_get_fd_np(fd, ACL_TYPE_EXTENDED) On fresh objects, both return NULL with ENOENT. Explicit one-entry fixture ACLs are retrieved successfully. Explicit zero-entry fixture ACLs can also yield NULL/ENOENT, while attribute queries return a serialized zero-entry ACL. The attribute queries use getattrlist() and descriptor-bound fgetattrlist(), requesting ATTR_CMN_RETURNED_ATTRS | ATTR_CMN_EXTENDED_SECURITY, with FSOPT_NOFOLLOW | FSOPT_REPORT_FULLSIZE and WITHOUT FSOPT_PACK_INVAL_ATTRS. Buffer lengths, variable-reference bounds and returned-attribute validity are checked. For the existing directories of interest, both calls succeed but omit the ATTR_CMN_EXTENDED_SECURITY returned bit. Explicit populated and zero-entry fixture records do set the bit. APFS reports valid VOL_CAP_INT_EXTENDED_SECURITY support; we do not assume that volume capability proves per-object ACL availability. On macOS 27.0.1, build 26A434, using APFS, which supported interface and documented conditions allow software to distinguish an absent ACL from unavailable or unsupported ACL evidence when descriptor-bound attribute queries succeed but omit ATTR_CMN_EXTENDED_SECURITY and native ACL getters return ENOENT for an existing object? Please clarify: Whether ENOENT has a supported ACL-absence interpretation, and under exactly which checked conditions. Whether an omitted extended-security attribute can establish ACL absence, rather than unavailable or unsupported evidence. How explicit zero-entry ACLs differ from absent ACL records through supported interfaces. How KAUTH_FILESEC_NOACL should be interpreted through supported APIs. How genuine retrieval failures, including permission, I/O, allocation and unsupported-operation errors, must remain distinguishable. Whether a supported descriptor-bound verification method exists that preserves fail-closed security checks and object identity binding; please identify its guarantees and limitations regarding pathname/ancestor changes and later operations. Whether relevant behavior is specific to this macOS/APFS version. Please identify the applicable public documentation or supported verification sequence. We do not want to modify permissions, synthesize ACLs on target objects, treat invalid-attribute defaults as real evidence, or accept ambiguous omission/ENOENT as success. Existing ownership, mode and confinement checks must remain separate mandatory checks. If no public API can make this distinction reliably, please state that limitation.
Replies
15
Boosts
0
Views
582
Activity
3d
Export semantics and non-hydrating materialization proof for File Provider-tagged project directories
On macOS 26.7.1 with Xcode 26.6 on Apple silicon, several directories in a development tree carry the private extended-attribute names com.apple.fileprovider.dir#N and com.apple.fileprovider.fpfs#P. On this host, the supported xattr_flags_from_name decoder returns XATTR_FLAG_NEVER_PRESERVE for the first exact name and XATTR_FLAG_NO_EXPORT for the second exact name. Apple's public API defines those flag meanings; the literal name encoding and the attributes' private values are not treated as a public semantic contract. We want a self-contained APFS compilation-input tree using descriptor-based COPYFILE_DATA for regular files, with independent inventory and hash verification and no private-xattr copying. For this compilation-only export, does Apple support deliberate non-preservation when xattr_flags_from_name returns XATTR_FLAG_NEVER_PRESERVE, and when it returns XATTR_FLAG_NO_EXPORT for a governed SHARE operation? Separately, what public, non-hydrating API can establish that every required file is already fully materialized and that export will not trigger provider downloads? Does enumeratorForMaterializedItems establish that state for a closed descendant tree, or must each item be checked by another supported API? Can reading or hashing an item itself cause materialization? We are asking about documented APIs, supported export behavior, and security postconditions. We are not asking to decode or preserve private attribute values. No production paths, source code, credentials, datasets, or personal information are included.
Replies
4
Boosts
0
Views
394
Activity
3d
Missing entitlement for API HomeKit error
During a test run of my HomeKit application in Xcode, after some time the app did run smoothly, I've started for one characteristic to get a pretty weird error in the readValueWithCompletionHandler: callback block: Error Domain=HMErrorDomain Code=80 "Missing entitlement for API." UserInfo={NSLocalizedFailureReason=Handler does not support background access, NSLocalizedDescription=Missing entitlement for API.} The application was launched just a couple of hours ago and the profile is still OK (though it will expire very inconveniently soon): 1044 ocs /tmp> security cms -D -i /Users/ocs/Library/Developer/Xcode/DerivedData/HomeObserverNA-hkazqlfbeuucvybpdzdgosyhhxnx/Build/Products/Debug-maccatalyst/HomeObserverNA.app/Contents/embedded.provisionprofile -o /tmp/ppp.plist 1045 ocs /tmp> plutil -extract ExpirationDate raw -o - /tmp/ppp.plist 2026-10-15T14:04:02Z 1046 ocs /tmp> Note please that immediately after launch (and for some time after that) the value was read in through the same code without any problem. Strangely enough, when I've switched the device through the Home application, I've got the update planned through enableNotification:completionHandler: all right. and the error stopped occurring, readValueWithCompletionHandler: from that moment on again works as presumed. How can I fix the problem, what's wrong in my app? Thanks!
Replies
25
Boosts
0
Views
1k
Activity
3d
Can a watchOS alarm show a custom wake screen instead of the system Open/Stop alert?
I’m developing a watchOS gentle-wake alarm using WKExtendedRuntimeSession and repeating haptics. When the app determines it is time to wake the user, I want the watch to present the app’s custom wake screen immediately. That screen includes a Stop control. The goal is for the custom screen to be the alarm experience, rather than requiring the user to tap Open on the system’s Open/Stop alert or having that system alert replace the custom screen. In hardware tests of my watchOS app (version 0.1, build 10) on November 9, 2026, I observed the system’s Open/Stop alert during the alarm. After selecting Open, the custom UI appeared, but the system alert returned after the app subsequently became inactive while the alarm session was still running. Test environment Apple Watch Series 11, watchOS 27.2 (24S118) Xcode 27.2 (27B52), watchOS 27.2 SDK Watch unlocked, Always On enabled, no attached debugger The app schedules the session with start(at:), calls notifyUser(hapticType:repeatHandler:) once, and presents a SwiftUI fullScreenCover with the wake interface and Stop button. Stop invalidates the session. In the 15-second Wake Duration test, logs showed reduced luminance after 15 seconds and inactivity about one second later. I observed the Open/Stop alert return twice after selecting Open. In the 70-second test, reduced luminance occurred 70 seconds after activation, followed by inactivity. Neither test logged a duplicate notifyUser call, process restart, or disappearance of the custom view before session termination. The logs establish lifecycle timing, but do not directly record system-alert presentation. Questions Is there a supported watchOS API or alarm architecture that can present a third-party app’s custom wake screen immediately when its alarm starts, without first showing or subsequently replacing it with the system Open/Stop alert? If so, what lifecycle, presentation, and background-haptic requirements apply, including when the app is inactive or the watch is in Always On mode? If this isn’t supported, is the system alert mandatory for WKExtendedRuntimeSession alarms, and what is the recommended alternative? Would AlarmKit with an iPhone companion change what can be presented on the watch? The custom screen would provide a clear way to stop the alarm. I’m not asking to remove the user’s ability to stop it or to keep the display at full brightness indefinitely. I also prepared a focused Watch-only sample isolating the runtime session, repeating haptics, custom presentation, and lifecycle logging. It builds successfully but has not been tested on hardware. The observations above are from the app, not the sample.
Replies
1
Boosts
0
Views
117
Activity
3d
Logitech MX Brio 4K webcam detected but no video on macOS 27 Golden Gate (Mac Studio M4)
Since upgrading to macOS 27 Golden Gate, my Mac Studio (M4) recognises my Logitech MX Brio 4K webcam, but no video feed is displayed. The camera appears to be detected by the system, but the video signal does not show up in: FaceTime Photo Booth Logitech Options+ I've spent quite a bit of time troubleshooting the issue, including following diagnostic steps suggested by Siri and Copilot, but everything points to a potential macOS-related problem rather than a hardware or configuration issue. Has anyone else experienced this with the MX Brio or other webcams on macOS 27 Golden Gate? I reported the issue to Apple through the Feedback app when Beta 1 was released, but so far I haven't received a response or found a workaround. Any insights or suggestions would be greatly appreciated. Thanks!
Replies
3
Boosts
2
Views
492
Activity
3d
Subscriptions suddenly stopped working in all my apps – StoreKit returns 0 products
Since November 5, in-app subscriptions have suddenly stopped working in all three of my apps on the App Store. Everything worked perfectly before, and no changes were made to the apps. The subscription purchase buttons no longer display prices, only a dash ("–"). Existing apps can still be downloaded normally. I reproduced the problem in Xcode on my own device. StoreKit reports: STOREKIT: Received 0 products STOREKIT: Invalid IDs = ( "TEE_year", "TEE_month", "TEE_week" ) All subscription products are still configured in App Store Connect, and the agreements appear to be active. Interestingly, the problem started around the time I accepted updated Apple agreements and changed my address in my developer account. I don't know whether this is related. Several customers have already independently reported the same problem, so this is not limited to my own device or Apple ID. I strongly suspect an App Store Connect or StoreKit backend issue rather than an app-specific programming error. I've contacted Apple Developer Support (case ID is 30000008123797) but haven't received a solution yet. Has anyone else experienced subscriptions suddenly becoming unavailable across multiple apps? Could this be related to updated agreements or account information?
Replies
1
Boosts
0
Views
138
Activity
3d
Supported backend recovery after RESCIND_CONSENT
We are integrating age assurance into two iOS apps with authenticated backend services. We need to handle one specific transition: a parent revokes app consent, then subsequently grants consent again. Our implementation can verify App Store Server Notifications V2 and associate a RESCIND_CONSENT event with its appTransactionId, app and environment. Our backend can then recognize that withdrawal. We do not treat a newly signed AppTransaction, an absent withdrawal record, or acceptance of our Terms as renewed parental permission. We also keep PermissionKit significant-update responses separate from permission to use the app itself. We reviewed the Age Assurance Q&A, Requesting people share their age range with your app, AppTransaction.appTransactionID, and Testing age assurance in sandbox. The documentation explains withdrawal notifications and app-launch prevention. We have not established the supported backend recovery signal after a parent subsequently approves the app again. What supported API, signed field or server notification establishes that later approval for the same appTransactionId? If there is no server-verifiable signal, what supported architecture should a developer use to restore backend access without mistaking a replayed transaction or a significant-update response for renewed app consent? Please identify the supported OS/API versions and a sandbox procedure to exercise withdrawal followed by reapproval, including whether the appTransactionId remains the same. Our current verification uses synthetic withdrawal events and isolated backend tests; we have not yet verified this transition using a genuine parent/child Sandbox Apple Account setup. We are asking about supported API behavior, not reporting an observed Apple service failure or requesting legal advice. References: https://developer.apple.com/support/age-assurance/ https://developer.apple.com/documentation/declaredagerange/requesting-people-share-their-age-range-with-your-app https://developer.apple.com/documentation/storekit/apptransaction/apptransactionid https://developer.apple.com/documentation/storekit/testing-age-assurance-in-sandbox
Replies
0
Boosts
0
Views
38
Activity
3d