Posts under App & System Services topic

Post

Replies

Boosts

Views

Activity

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
511
1d
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
81
1d
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
575
1d
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
386
1d
Processor Trace
Hello. I'm trying to use this feature with DriverKit and currently it seems like a dead end: https://developer.apple.com/documentation/xcode/analyzing-cpu-usage-with-processor-trace I'm on Mac Mini m4, macOS 27.2, Xcode 27.2, SIP disabled, Processor Trace in Settings->Developer Tools ticked. Just to make sure - there is no way to profile cpu inside DriverKit process? Any hints appreciated :)
1
0
73
1d
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
1d
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
102
1d
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
479
1d
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
128
1d
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
26
1d
StoreKit returns USD prices instead of EUR in TestFlight, blocking app release (iOS 27.0.1)
We are experiencing the same issue with two independent native iOS apps on an iPhone running iOS 27.0.1, using TestFlight in France. Our annual subscription displays US$34.90 instead of €39.90, and our non-consumable purchase displays US$5.99 instead of €6.99. Both apps displayed the correct EUR prices during local Xcode testing. In TestFlight, Apple's native purchase sheets still show the correct EUR prices, and both purchases work successfully. We have contacted Apple Developer Support (case 103017935062). As this issue is delaying the time-sensitive release of our educational app, could Apple confirm whether a workaround is available or whether a fix is planned? https://developer.apple.com/forums/thread/845478 Thank you.
3
0
83
1d
macOS Transparent Proxy fails to start before login on Wi-Fi: "No network available"
I'm investigating an issue when deploying my VPN agent via Jamf during initial setup on clean macOS machines. The Network Extension process starts immediately after installation, but its Transparent Proxy provider starts only after a user logs in. I tried to reboot, and still observed the transparent proxy start fails. 10:00:52 === system boot 10:00:57.535 NESMTransparentProxySession[Primary Tunnel:Prisma Access Agent:68CAC11B-...]: Received a start command from PASrv[303] 10:00:57.538 NESMTransparentProxySession[...]: No network available <<<<<<<<< 10:00:57.541 NESMTransparentProxySession[...]: status changed to disconnected, last stop reason No network available <<<<<<<<< 10:01:21.541 NESMTransparentProxySession[...]: handleChangeEventForRankedInterfaces - stopped 0 status disconnected includeAllNetworks 0 10:01:26.373 NESMTransparentProxySession[...]: handleChangeEventForRankedInterfaces - stopped 0 status disconnected includeAllNetworks 0 10:06:01.293 NESMTransparentProxySession[...]: Received a start command from user_context[1547] 10:06:01.615 NESMTransparentProxySession[...]: status changed to connectedOur product requires pre-login functionality. Is this behavior expected, and how can we enable the Transparent Proxy provider before user login? I suspect a race between network availability and the attempt to start the Transparent Proxy. The issue does not occur with Ethernet, possibly because connectivity becomes available earlier than with Wi-Fi. Should we call startVPNTunnel again once connectivity becomes available? If so, what is the recommended way to detect this network transition?
5
0
149
1d
Can a Mac App Store (sandboxed) app create and delete VLAN interfaces with SCVLANInterfaceCreate?
We make a Mac App Store app that runs virtual machines with the Virtualization framework. It has the com.apple.vm.networking entitlement and already bridges VMs to physical interfaces through VZBridgedNetworkDeviceAttachment. We'd like users to manage 802.1Q VLAN interfaces from inside the app, so they can create a VLAN on an Ethernet port and bridge a VM to it. The SystemConfiguration API for this is: var auth: AuthorizationRef? var item = AuthorizationItem(name: "system.services.systemconfiguration.network", valueLength: 0, value: nil, flags: 0) var rights = AuthorizationRights(count: 1, items: &item) AuthorizationCreate(&rights, nil, [.interactionAllowed, .extendRights, .preAuthorize], &auth) let prefs = SCPreferencesCreateWithAuthorization(nil, "MyApp" as CFString, nil, auth!)! SCPreferencesLock(prefs, true) // fails in the sandbox let vlan = SCVLANInterfaceCreate(prefs, physicalInterface, 100 as CFNumber) SCPreferencesCommitChanges(prefs) SCPreferencesApplyChanges(prefs) SCPreferencesUnlock(prefs) What we see on macOS 27: Without the sandbox, SCPreferencesLock on preferences created with SCPreferencesCreateWithAuthorization succeeds. With com.apple.security.app-sandbox, the same call fails with kSCStatusAccessError ("Permission denied"). Read-only calls work in the sandbox: SCVLANInterfaceCopyAll, ACVLANInterfaceCopyAvailablePhysicalInterfaces and SCNetworkInterfaceCopyAll all return the expected results. Our questions: Can a sandboxed Mac App Store app create or delete VLAN interfaces in any supported way, through SystemConfiguration or another API? If not, is there an entitlement we could request for this, similar to com.apple.vm.networking? Or is a privileged helper (SMAppService.daemon) the only way? As we understand it, the Mac App Store doesn't allow a privileged helper. Are VLAN interfaces (vlanN) meant to appear in VZBridgedNetworkInterface.networkInterfaces(update: it appears i create vlan interface using mac settings network settings) so a VM can be bridged to one? Does vmnet's bridged mode support them? If a VM is bridged to the physical Ethernet port and tags its own frames inside the guest, do the 802.1Q tags pass through the bridge unchanged? If creating VLANs isn't possible from the sandbox, our fallback is to list the existing VLANs and send users to System Settings › Network › Manage Virtual Interfaces. We'd like to confirm that before building it. Thanks!
5
0
132
1d
Can macOS sandbox-exec confine writes to a directory that doesn’t exist yet?
I’m evaluating an offline command-line tool launched from Terminal on macOS. The parent process creates an enclosing directory, then launches the tool through /usr/bin/sandbox-exec -p with an inline profile. The tool must create its own output directory, which is absent at launch. Can a macOS sandbox profile reliably enforce all of the following for that invocation? Allow reads of the tool’s interpreter, dependencies and input files. Deny network access and creation of child processes by the sandboxed tool. Allow the tool to create /path/to/work/proof/producer001 and write beneath it, while denying writes outside that directory, including writes through symlinks or other path aliases. The proposed profile denies file-write* globally and allows it only under a subpath rule for the output directory. Does that exception cover creation of the directory itself when only its parent exists? Does deny process-fork cover all child-process creation paths, including posix_spawn? Is there a supported way to inspect or validate the effective policy for an exact command and working directory before invoking it? If sandbox-exec is unsuitable for this use, is there a supported macOS mechanism for applying these restrictions to a command-line tool launched from Terminal? A documentation reference would be helpful.
1
0
99
1d
Supported way for a watchOS clock app to stay frontmost after the screen dims?
I'm building a standalone watchOS app (SwiftUI, watch-only) whose main screen is its own full-screen clock. Users who choose this clock want it to remain the screen they see on wrist raise, instead of returning to the system watch face after the inactivity timeout. I'd like to know whether watchOS supports this for an App Store app, and which API to use. What I've looked at (watchOS 27.2 SDK, Xcode 27.2): Always On + Return to Clock. The app supports the Always On state. This works up to the Return to Clock interval the user chooses (at most one hour, per "Taking advantage of frontmost app state"). After that, the system face returns. WKApplication.isFrontmostTimeoutExtended. The documentation says it has had no effect since watchOS 7. In a test, reading it back gave false, and the app went to the background after about 2 minutes. WKExtendedRuntimeSession. The documentation asks developers to pick a session type based on the app's actual purpose (self care, mindfulness, physical therapy, smart alarm). None of these fits a clock, so I'm not using one to gain runtime. App Intents supportedModes / LongRunningIntent. These bring the app to the foreground when an intent runs, or run long background work. I couldn't find a way to use them to return automatically after the timeout. openSystemURL with the app's own URL scheme from a background callback. This didn't reopen the app. Other clock apps on the App Store offer a "keep active" style option, so I'm wondering whether a supported mechanism exists that I've missed. Questions: Is there a supported API or capability that lets a user-selected clock app stay frontmost, or come back automatically, after the inactivity timeout? Normal exits must still work: the Digital Crown, other apps, notifications, locking and Sleep Focus. If this isn't supported, is the limit intentional? Is per-app Return to Clock plus Always On the intended maximum? I can share a minimal sample (FrontmostClockProbe) that uses only public APIs and logs scene phase and luminance state. Thanks!
2
0
67
1d
Supported quarantine preservation when copying files from an App Sandbox process
What supported public API and verification contract should a sandboxed macOS file manager use to preserve a copied file's quarantine/provenance metadata? We observe different results in App Sandbox versus Finder and an otherwise-matched non-sandbox diagnostic. We want to keep App Sandbox and all security protections enabled, not remove quarantine or invent undocumented flag masks. Environment: macOS 26.6.2 (25G83), Apple Silicon, local APFS. Optimized Foundation-only diagnostic, Apple Development signing, Hardened Runtime, launched directly as an executable. The sandbox variant has app-sandbox, user-selected read/write and app-scope bookmark entitlements. This is not a notarized distribution-build comparison. Reproduction: Use an existing regular JPEG with naturally present com.apple.quarantine metadata identifying Chrome, raw flags 0283 and a nonempty event field. Keep the original read-only. Record SHA-256, length, full raw extended attributes and fresh NSURL quarantinePropertiesKey observations. Keep access to a user-granted local test directory active. Copy to a new, absent destination in a fresh directory using each of these three arms: fclonefileat with CLONE_ACL | CLONE_NOFOLLOW_ANY | CLONE_RESOLVE_BENEATH (28). copyfile with COPYFILE_CLONE | COPYFILE_ACL; record COPYFILE_STATE_WAS_CLONED. FileManager.copyItem(at:to:). Observe source and destination without setting, removing or repairing metadata. Each arm waits at least 1.1 seconds before copying; the source quarantine timestamp is much older than call time. Repeat with fresh destinations. Also copy the same source through actual Finder Copy/Paste twice. Compare two signed variants made from the same compiled payload, with identical executable name, bundle ID, Development identity and Hardened Runtime. The only signed entitlement difference is app-sandbox=true versus its omission. The sandbox variant resolves the existing exact folder grant; the non-sandbox diagnostic uses that same fixed test directory directly. Results: Sandbox diagnostic: all six calls succeed and data hashes/lengths match. All six outputs change raw flags 0283 to 0082, agent Chrome to the diagnostic app, event field nonempty to empty, and timestamp. Public output lacks the source event identifier and adds LSQuarantineTypeSandboxed. Matched non-sandbox diagnostic: all six copies preserve the full observed raw quarantine record and public quarantine dictionary. copyfile reports WAS_CLONED=true in both contexts. Finder: both copies preserve the full observed raw quarantine record and public dictionary. Source bytes and declared preserved metadata remain unchanged. Other compared raw attributes, mode, flags, birth/modification times, owner/group and ACL match in these cases. We also reproduced timestamp-only differences with files naturally quarantined by the diagnostic itself. The foreign-agent control above shows that the difference is not limited to timestamp. The chosen source exposes no public origin/data URL, so their preservation is untested. We have not traced the responsible internal component, tested Gatekeeper effects, or established whether the transformation is security-equivalent. We do not claim the three APIs use independent implementations or that all possible public API combinations have been tested. Could you clarify: Is this transformation expected for copying from an App Sandbox process, or should we file it as a bug? What documented preservation behavior should a sandboxed file manager rely on? Is there a supported API or operation that preserves the source's quarantine/provenance metadata in this context without disabling App Sandbox or weakening security protections? If exact raw equality is intentionally not guaranteed, which supported public properties or behaviors should verification check? Is a quarantine-properties dictionary round-trip supported, and what information does it preserve or omit? We have not attempted a metadata repair. Separately, a pathname-based repair after cloning would require its own destination-identity/race safety review because the clone call does not return a creation-bound destination descriptor. We are asking for supported API semantics, not private implementation details or a security bypass. We can prepare a minimal sanitized standalone reproducer if needed. No user files, sandbox grants, private logs or diagnostic binaries are attached to this initial question.
5
0
626
1d
LiveCommunicationKit: In‑call banner missing in foreground, only appears after app goes background (iPhone14 Pro)
Environment: Device: iPhone 14 Pro iOS version: 26 SDK: LiveCommunicationKit App status: Foreground / Active state Problem reproduction: Intermittent, happens on some devices, not 100% reproducible on all test devices. Expected behavior: Incoming call banner should present when app is active (foreground). Actual behavior: No system incoming‑call banner while app is foreground. Banner appears only after pressing home‑button / switching app to background. Additional notes: Our app uses LiveCommunicationKit because VoIP PushKit is not permitted for China mainland App Store distribution. Call reporting completes without error; no error returned from LiveCommunicationKit API. private func _lckReportIncomingCall(call: Call?, uuid: UUID, handle: String, hasVideo: Bool, displayName: String) { guard let manager = conversationManager else { Log.error("[ProviderDelegate-LCK] ConversationManager is nil, falling back") _fallbackReportIncomingCall(call: call, uuid: uuid, handle: handle, hasVideo: hasVideo, displayName: displayName) return } let callInfo = callInfos[uuid] let callId = callInfo?.callId ?? "" let remoteHandle = Handle(type: .generic, value: handle, displayName: displayName) let update = Conversation.Update(localMember: nil, members: [remoteHandle], activeRemoteMembers: [remoteHandle]) // 冷启动时 iOS PKPushRegistry 要求在 2 秒内上报来电,否则杀进程。 // Task { @MainActor } 是异步的,调试时主线程 RunLoop 来不及调度就超时了。 // 这里用 DispatchSemaphore 在后台线程同步等待 LCK 上报完成。 let semaphore = DispatchSemaphore(value: 0) var lckError: Error? DispatchQueue.main.async { Task { @MainActor in do { try await manager.reportNewIncomingConversation(uuid: uuid, update: update) Log.info("[ProviderDelegate-LCK] Reported incoming conversation: callId=\(callId), uuid=\(uuid)") if TelecomManager.shared.endCallkit { CoreContext.shared.doOnCoreQueue(synchronous: true) { core in let linphoneCall = core.getCallByCallid(callId: callId) if linphoneCall?.state == .PushIncomingReceived { try? linphoneCall?.terminate() } } } } catch { Log.error("[ProviderDelegate-LCK] Failed to report incoming conversation: \(error)") lckError = error } semaphore.signal() } } let waitResult = semaphore.wait(timeout: .now() + 5) if waitResult == .timedOut { Log.error("[ProviderDelegate-LCK] Timed out waiting for LCK report, falling back") _fallbackReportIncomingCall(call: call, uuid: uuid, handle: handle, hasVideo: hasVideo, displayName: displayName) } else if let error = lckError { Log.error("[ProviderDelegate-LCK] LCK report failed: \(error), declining SIP call") // 来电被拒(勿扰/黑名单等),decline 掉 SIP 侧 CoreContext.shared.doOnCoreQueue(synchronous: true) { _ in try? call?.decline(reason: .Busy) } } }
3
0
793
1d
Tap To Pay Account Not Linked Issue
I am currently having issues getting tap to pay to work locally for development. I have: the tap to pay development entitlement a verified test device a test sandbox user tap to pay / NFC / app apptest capabilities the correct provisioning profile We are currently working a payment service provider NMI to support tap to pay. Part of that process has been getting entitlements, and we now have the developer entitlement for tap to pay. We are having an issue with an "account not linked" error. We have been told by NMI this is an issue on Apple's side since we have the correct provisioning profile, capabilities, and entitlements set up for our company. This issue is when using a sandbox account. When I use a developer account I get an "invalid apple account" issue. Any combination of user / provisioning profile / and capabilities that I have tried have not produced better results. Versions: IOS version is 26.6 and xcode is also 26.6. I have followed these steps: https://developer.apple.com/forums/thread/775784 here is my feedback assistant ID which contains my sys logs and a video. FB24822720
1
1
386
1d
Apple iCloud Log TimeZone Verification
Hello, I'm using some of the data from apple icloud logs and hoping someone can help from the Apple community. When an app is autimatically updated there is a column called 'Activity Date' in the 'App-Book Re-download and Update History.csv' log file. Can you confirm the timezone? Here is an example date: 2025-02-02T02:13:40. Thank you!
2
0
109
1d
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
511
Activity
1d
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
81
Activity
1d
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
575
Activity
1d
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
386
Activity
1d
Processor Trace
Hello. I'm trying to use this feature with DriverKit and currently it seems like a dead end: https://developer.apple.com/documentation/xcode/analyzing-cpu-usage-with-processor-trace I'm on Mac Mini m4, macOS 27.2, Xcode 27.2, SIP disabled, Processor Trace in Settings->Developer Tools ticked. Just to make sure - there is no way to profile cpu inside DriverKit process? Any hints appreciated :)
Replies
1
Boosts
0
Views
73
Activity
1d
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
1d
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
102
Activity
1d
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
479
Activity
1d
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
128
Activity
1d
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
26
Activity
1d
StoreKit returns USD prices instead of EUR in TestFlight, blocking app release (iOS 27.0.1)
We are experiencing the same issue with two independent native iOS apps on an iPhone running iOS 27.0.1, using TestFlight in France. Our annual subscription displays US$34.90 instead of €39.90, and our non-consumable purchase displays US$5.99 instead of €6.99. Both apps displayed the correct EUR prices during local Xcode testing. In TestFlight, Apple's native purchase sheets still show the correct EUR prices, and both purchases work successfully. We have contacted Apple Developer Support (case 103017935062). As this issue is delaying the time-sensitive release of our educational app, could Apple confirm whether a workaround is available or whether a fix is planned? https://developer.apple.com/forums/thread/845478 Thank you.
Replies
3
Boosts
0
Views
83
Activity
1d
macOS Transparent Proxy fails to start before login on Wi-Fi: "No network available"
I'm investigating an issue when deploying my VPN agent via Jamf during initial setup on clean macOS machines. The Network Extension process starts immediately after installation, but its Transparent Proxy provider starts only after a user logs in. I tried to reboot, and still observed the transparent proxy start fails. 10:00:52 === system boot 10:00:57.535 NESMTransparentProxySession[Primary Tunnel:Prisma Access Agent:68CAC11B-...]: Received a start command from PASrv[303] 10:00:57.538 NESMTransparentProxySession[...]: No network available <<<<<<<<< 10:00:57.541 NESMTransparentProxySession[...]: status changed to disconnected, last stop reason No network available <<<<<<<<< 10:01:21.541 NESMTransparentProxySession[...]: handleChangeEventForRankedInterfaces - stopped 0 status disconnected includeAllNetworks 0 10:01:26.373 NESMTransparentProxySession[...]: handleChangeEventForRankedInterfaces - stopped 0 status disconnected includeAllNetworks 0 10:06:01.293 NESMTransparentProxySession[...]: Received a start command from user_context[1547] 10:06:01.615 NESMTransparentProxySession[...]: status changed to connectedOur product requires pre-login functionality. Is this behavior expected, and how can we enable the Transparent Proxy provider before user login? I suspect a race between network availability and the attempt to start the Transparent Proxy. The issue does not occur with Ethernet, possibly because connectivity becomes available earlier than with Wi-Fi. Should we call startVPNTunnel again once connectivity becomes available? If so, what is the recommended way to detect this network transition?
Replies
5
Boosts
0
Views
149
Activity
1d
Can a Mac App Store (sandboxed) app create and delete VLAN interfaces with SCVLANInterfaceCreate?
We make a Mac App Store app that runs virtual machines with the Virtualization framework. It has the com.apple.vm.networking entitlement and already bridges VMs to physical interfaces through VZBridgedNetworkDeviceAttachment. We'd like users to manage 802.1Q VLAN interfaces from inside the app, so they can create a VLAN on an Ethernet port and bridge a VM to it. The SystemConfiguration API for this is: var auth: AuthorizationRef? var item = AuthorizationItem(name: "system.services.systemconfiguration.network", valueLength: 0, value: nil, flags: 0) var rights = AuthorizationRights(count: 1, items: &item) AuthorizationCreate(&rights, nil, [.interactionAllowed, .extendRights, .preAuthorize], &auth) let prefs = SCPreferencesCreateWithAuthorization(nil, "MyApp" as CFString, nil, auth!)! SCPreferencesLock(prefs, true) // fails in the sandbox let vlan = SCVLANInterfaceCreate(prefs, physicalInterface, 100 as CFNumber) SCPreferencesCommitChanges(prefs) SCPreferencesApplyChanges(prefs) SCPreferencesUnlock(prefs) What we see on macOS 27: Without the sandbox, SCPreferencesLock on preferences created with SCPreferencesCreateWithAuthorization succeeds. With com.apple.security.app-sandbox, the same call fails with kSCStatusAccessError ("Permission denied"). Read-only calls work in the sandbox: SCVLANInterfaceCopyAll, ACVLANInterfaceCopyAvailablePhysicalInterfaces and SCNetworkInterfaceCopyAll all return the expected results. Our questions: Can a sandboxed Mac App Store app create or delete VLAN interfaces in any supported way, through SystemConfiguration or another API? If not, is there an entitlement we could request for this, similar to com.apple.vm.networking? Or is a privileged helper (SMAppService.daemon) the only way? As we understand it, the Mac App Store doesn't allow a privileged helper. Are VLAN interfaces (vlanN) meant to appear in VZBridgedNetworkInterface.networkInterfaces(update: it appears i create vlan interface using mac settings network settings) so a VM can be bridged to one? Does vmnet's bridged mode support them? If a VM is bridged to the physical Ethernet port and tags its own frames inside the guest, do the 802.1Q tags pass through the bridge unchanged? If creating VLANs isn't possible from the sandbox, our fallback is to list the existing VLANs and send users to System Settings › Network › Manage Virtual Interfaces. We'd like to confirm that before building it. Thanks!
Replies
5
Boosts
0
Views
132
Activity
1d
Can macOS sandbox-exec confine writes to a directory that doesn’t exist yet?
I’m evaluating an offline command-line tool launched from Terminal on macOS. The parent process creates an enclosing directory, then launches the tool through /usr/bin/sandbox-exec -p with an inline profile. The tool must create its own output directory, which is absent at launch. Can a macOS sandbox profile reliably enforce all of the following for that invocation? Allow reads of the tool’s interpreter, dependencies and input files. Deny network access and creation of child processes by the sandboxed tool. Allow the tool to create /path/to/work/proof/producer001 and write beneath it, while denying writes outside that directory, including writes through symlinks or other path aliases. The proposed profile denies file-write* globally and allows it only under a subpath rule for the output directory. Does that exception cover creation of the directory itself when only its parent exists? Does deny process-fork cover all child-process creation paths, including posix_spawn? Is there a supported way to inspect or validate the effective policy for an exact command and working directory before invoking it? If sandbox-exec is unsuitable for this use, is there a supported macOS mechanism for applying these restrictions to a command-line tool launched from Terminal? A documentation reference would be helpful.
Replies
1
Boosts
0
Views
99
Activity
1d
Supported way for a watchOS clock app to stay frontmost after the screen dims?
I'm building a standalone watchOS app (SwiftUI, watch-only) whose main screen is its own full-screen clock. Users who choose this clock want it to remain the screen they see on wrist raise, instead of returning to the system watch face after the inactivity timeout. I'd like to know whether watchOS supports this for an App Store app, and which API to use. What I've looked at (watchOS 27.2 SDK, Xcode 27.2): Always On + Return to Clock. The app supports the Always On state. This works up to the Return to Clock interval the user chooses (at most one hour, per "Taking advantage of frontmost app state"). After that, the system face returns. WKApplication.isFrontmostTimeoutExtended. The documentation says it has had no effect since watchOS 7. In a test, reading it back gave false, and the app went to the background after about 2 minutes. WKExtendedRuntimeSession. The documentation asks developers to pick a session type based on the app's actual purpose (self care, mindfulness, physical therapy, smart alarm). None of these fits a clock, so I'm not using one to gain runtime. App Intents supportedModes / LongRunningIntent. These bring the app to the foreground when an intent runs, or run long background work. I couldn't find a way to use them to return automatically after the timeout. openSystemURL with the app's own URL scheme from a background callback. This didn't reopen the app. Other clock apps on the App Store offer a "keep active" style option, so I'm wondering whether a supported mechanism exists that I've missed. Questions: Is there a supported API or capability that lets a user-selected clock app stay frontmost, or come back automatically, after the inactivity timeout? Normal exits must still work: the Digital Crown, other apps, notifications, locking and Sleep Focus. If this isn't supported, is the limit intentional? Is per-app Return to Clock plus Always On the intended maximum? I can share a minimal sample (FrontmostClockProbe) that uses only public APIs and logs scene phase and luminance state. Thanks!
Replies
2
Boosts
0
Views
67
Activity
1d
Supported quarantine preservation when copying files from an App Sandbox process
What supported public API and verification contract should a sandboxed macOS file manager use to preserve a copied file's quarantine/provenance metadata? We observe different results in App Sandbox versus Finder and an otherwise-matched non-sandbox diagnostic. We want to keep App Sandbox and all security protections enabled, not remove quarantine or invent undocumented flag masks. Environment: macOS 26.6.2 (25G83), Apple Silicon, local APFS. Optimized Foundation-only diagnostic, Apple Development signing, Hardened Runtime, launched directly as an executable. The sandbox variant has app-sandbox, user-selected read/write and app-scope bookmark entitlements. This is not a notarized distribution-build comparison. Reproduction: Use an existing regular JPEG with naturally present com.apple.quarantine metadata identifying Chrome, raw flags 0283 and a nonempty event field. Keep the original read-only. Record SHA-256, length, full raw extended attributes and fresh NSURL quarantinePropertiesKey observations. Keep access to a user-granted local test directory active. Copy to a new, absent destination in a fresh directory using each of these three arms: fclonefileat with CLONE_ACL | CLONE_NOFOLLOW_ANY | CLONE_RESOLVE_BENEATH (28). copyfile with COPYFILE_CLONE | COPYFILE_ACL; record COPYFILE_STATE_WAS_CLONED. FileManager.copyItem(at:to:). Observe source and destination without setting, removing or repairing metadata. Each arm waits at least 1.1 seconds before copying; the source quarantine timestamp is much older than call time. Repeat with fresh destinations. Also copy the same source through actual Finder Copy/Paste twice. Compare two signed variants made from the same compiled payload, with identical executable name, bundle ID, Development identity and Hardened Runtime. The only signed entitlement difference is app-sandbox=true versus its omission. The sandbox variant resolves the existing exact folder grant; the non-sandbox diagnostic uses that same fixed test directory directly. Results: Sandbox diagnostic: all six calls succeed and data hashes/lengths match. All six outputs change raw flags 0283 to 0082, agent Chrome to the diagnostic app, event field nonempty to empty, and timestamp. Public output lacks the source event identifier and adds LSQuarantineTypeSandboxed. Matched non-sandbox diagnostic: all six copies preserve the full observed raw quarantine record and public quarantine dictionary. copyfile reports WAS_CLONED=true in both contexts. Finder: both copies preserve the full observed raw quarantine record and public dictionary. Source bytes and declared preserved metadata remain unchanged. Other compared raw attributes, mode, flags, birth/modification times, owner/group and ACL match in these cases. We also reproduced timestamp-only differences with files naturally quarantined by the diagnostic itself. The foreign-agent control above shows that the difference is not limited to timestamp. The chosen source exposes no public origin/data URL, so their preservation is untested. We have not traced the responsible internal component, tested Gatekeeper effects, or established whether the transformation is security-equivalent. We do not claim the three APIs use independent implementations or that all possible public API combinations have been tested. Could you clarify: Is this transformation expected for copying from an App Sandbox process, or should we file it as a bug? What documented preservation behavior should a sandboxed file manager rely on? Is there a supported API or operation that preserves the source's quarantine/provenance metadata in this context without disabling App Sandbox or weakening security protections? If exact raw equality is intentionally not guaranteed, which supported public properties or behaviors should verification check? Is a quarantine-properties dictionary round-trip supported, and what information does it preserve or omit? We have not attempted a metadata repair. Separately, a pathname-based repair after cloning would require its own destination-identity/race safety review because the clone call does not return a creation-bound destination descriptor. We are asking for supported API semantics, not private implementation details or a security bypass. We can prepare a minimal sanitized standalone reproducer if needed. No user files, sandbox grants, private logs or diagnostic binaries are attached to this initial question.
Replies
5
Boosts
0
Views
626
Activity
1d
LiveCommunicationKit: In‑call banner missing in foreground, only appears after app goes background (iPhone14 Pro)
Environment: Device: iPhone 14 Pro iOS version: 26 SDK: LiveCommunicationKit App status: Foreground / Active state Problem reproduction: Intermittent, happens on some devices, not 100% reproducible on all test devices. Expected behavior: Incoming call banner should present when app is active (foreground). Actual behavior: No system incoming‑call banner while app is foreground. Banner appears only after pressing home‑button / switching app to background. Additional notes: Our app uses LiveCommunicationKit because VoIP PushKit is not permitted for China mainland App Store distribution. Call reporting completes without error; no error returned from LiveCommunicationKit API. private func _lckReportIncomingCall(call: Call?, uuid: UUID, handle: String, hasVideo: Bool, displayName: String) { guard let manager = conversationManager else { Log.error("[ProviderDelegate-LCK] ConversationManager is nil, falling back") _fallbackReportIncomingCall(call: call, uuid: uuid, handle: handle, hasVideo: hasVideo, displayName: displayName) return } let callInfo = callInfos[uuid] let callId = callInfo?.callId ?? "" let remoteHandle = Handle(type: .generic, value: handle, displayName: displayName) let update = Conversation.Update(localMember: nil, members: [remoteHandle], activeRemoteMembers: [remoteHandle]) // 冷启动时 iOS PKPushRegistry 要求在 2 秒内上报来电,否则杀进程。 // Task { @MainActor } 是异步的,调试时主线程 RunLoop 来不及调度就超时了。 // 这里用 DispatchSemaphore 在后台线程同步等待 LCK 上报完成。 let semaphore = DispatchSemaphore(value: 0) var lckError: Error? DispatchQueue.main.async { Task { @MainActor in do { try await manager.reportNewIncomingConversation(uuid: uuid, update: update) Log.info("[ProviderDelegate-LCK] Reported incoming conversation: callId=\(callId), uuid=\(uuid)") if TelecomManager.shared.endCallkit { CoreContext.shared.doOnCoreQueue(synchronous: true) { core in let linphoneCall = core.getCallByCallid(callId: callId) if linphoneCall?.state == .PushIncomingReceived { try? linphoneCall?.terminate() } } } } catch { Log.error("[ProviderDelegate-LCK] Failed to report incoming conversation: \(error)") lckError = error } semaphore.signal() } } let waitResult = semaphore.wait(timeout: .now() + 5) if waitResult == .timedOut { Log.error("[ProviderDelegate-LCK] Timed out waiting for LCK report, falling back") _fallbackReportIncomingCall(call: call, uuid: uuid, handle: handle, hasVideo: hasVideo, displayName: displayName) } else if let error = lckError { Log.error("[ProviderDelegate-LCK] LCK report failed: \(error), declining SIP call") // 来电被拒(勿扰/黑名单等),decline 掉 SIP 侧 CoreContext.shared.doOnCoreQueue(synchronous: true) { _ in try? call?.decline(reason: .Busy) } } }
Replies
3
Boosts
0
Views
793
Activity
1d
Tap To Pay Account Not Linked Issue
I am currently having issues getting tap to pay to work locally for development. I have: the tap to pay development entitlement a verified test device a test sandbox user tap to pay / NFC / app apptest capabilities the correct provisioning profile We are currently working a payment service provider NMI to support tap to pay. Part of that process has been getting entitlements, and we now have the developer entitlement for tap to pay. We are having an issue with an "account not linked" error. We have been told by NMI this is an issue on Apple's side since we have the correct provisioning profile, capabilities, and entitlements set up for our company. This issue is when using a sandbox account. When I use a developer account I get an "invalid apple account" issue. Any combination of user / provisioning profile / and capabilities that I have tried have not produced better results. Versions: IOS version is 26.6 and xcode is also 26.6. I have followed these steps: https://developer.apple.com/forums/thread/775784 here is my feedback assistant ID which contains my sys logs and a video. FB24822720
Replies
1
Boosts
1
Views
386
Activity
1d
Apple iCloud Log TimeZone Verification
Hello, I'm using some of the data from apple icloud logs and hoping someone can help from the Apple community. When an app is autimatically updated there is a column called 'Activity Date' in the 'App-Book Re-download and Update History.csv' log file. Can you confirm the timezone? Here is an example date: 2025-02-02T02:13:40. Thank you!
Replies
2
Boosts
0
Views
109
Activity
1d