Posts under App & System Services topic

Post

Replies

Boosts

Views

Activity

HELP!! OPENING TOMORROW!!
HI! We have been in review for over a month with no communication and we open tomorrow! We initially were rejected saying apple pay did not work. However, in the test app apple pay worked fine. We really need this app to open our doors tomorrow!! Please advise! Thank you
0
0
52
1w
Kernel tag check fault after wake on Mac17 hardware, Google Chrome Helper, macOS 26.5–27.0.1 — related to r.172793638?
We're seeing a recurring kernel panic across six Mac17-family Macs (Mac17,2 / Mac17,4 / Mac17,8; T8142 and T6050) in a managed fleet. 34 panic logs collected 30 Sept – 9 Oct, all with the same signature: panic(cpu N caller ...): Kernel tag check fault (expected tagged address: 0x...028), esr 0x96000011 Faulting address is always at offset 0x28 of the object Same crash PC per build: kernel text exec base + 0x48da38 on 27.0/27.0.1, + 0x46a784 on 26.7, + 0x466ee0 on 26.5 Panicked task is "Google Chrome Helper" in all 34 cases, thread Chrome_ChildIOThread (Chrome's IPC/network I/O thread) Always 3–60 s after wake from sleep, usually a dark wake with the lid closed (overnight or after a 3–18 min sleep) No third-party kexts loaded; "Post-boot loaded kexts" lists only Apple drivers Affected builds: 26.5 (25F71), 26.7 (25G229), 27.0 (26A428), 27.0.1 (26A434). Not a regression from one update: a machine still on 26.5 panics identically. Only Mac17-family hardware is affected. Older Apple silicon Macs with the same software stack are fine. Present on every affected machine: Chrome PWAs (Gmail/Chat/Meet) running in the background, keeping Chrome's network service alive across sleep. On one machine Microsoft Edge is the primary browser and never panics; only Chrome Helper does. Microsoft Defender for Endpoint with its network filter (content filter) extension, MDM-managed. This looks related to thread 821372, where DTS described a kernel networking panic on M5-family hardware with a Network Extension present (r.172793638 / FB22401652), fixed in 26.5b2. We appear to be seeing a tag-check-fault variant on 26.5 release and later. Questions: Is this a known issue, and is it the same root cause as r.172793638? Is there a build where it's fixed? Any recommended mitigation beyond preventing sleep and quitting Chrome? Feedback Assistant: FB25128015 with panic logs and sysdiagnose. Happy to collect more data or test a build. Backtrace from a 27.0.1 panic (kernel text exec base 0xfffffe003aa54000), panic PC first: lr: 0xfffffe003aee1a38 lr: 0xfffffe003aeec580 lr: 0xfffffe003b12cf34 lr: 0xfffffe003b12dc50 lr: 0xfffffe003b07b1f8 lr: 0xfffffe003b07c758 lr: 0xfffffe003b237ff4 lr: 0xfffffe003ac787f0 lr: 0xfffffe003aa576ac lr: 0x000000018747a57c (userspace)
4
0
392
1w
iOS 27: duplicate BLE identities with extended advertising on iPhone 15 Pro; legacy advertising unaffected
On our iPhone 15 Pro running iOS 27.2 (24B119), a single physical BLE peripheral consistently appears as two separate scan results with different UUIDs. The issue reproduces consistently when the peripheral uses connectable BLE extended advertising with a 1M primary PHY and 2M secondary PHY. Switching the same peripheral to legacy advertising eliminates the duplicate scan results. The duplication is visible in both our application and nRF Connect, and we did not observe it on iOS 26. The duplicate results are visible in both our application and nRF Connect, so this is not specific to our application code or BLE library. The peripherals use a Silicon Labs BLE chipset and connectable BLE extended advertising with a 1M primary PHY and 2M secondary PHY. The interesting detail is in the captured bluetoothd logs: the same Bluetooth address, advertised local name, and manufacturer data appear under two UUIDs, but one identity is labeled Random and the other Public. Both are marked connectable. For example, one peripheral appears as: Local name: WD-883200239 Bluetooth address: 7C:C6:B6:58:F4:76 Random: F015AD07-F340-40DB-CEB5-5D602386B408 Public: 6D0F1C74-14B9-06B3-F64C-29E33CB8A065 On November 6, the logs report the Random identity at 08:07:07.496, followed by the Public identity at 08:07:08.505, with matching address bytes, local name, and manufacturer data. A second physical peripheral shows the same pattern. To clarify, these are different UUIDs for the same physical peripheral, not simply repeated discovery callbacks for one UUID. This creates ambiguity when selecting a peripheral for connection. The Public/Random distinction is visible in system diagnostics but is not exposed through supported Core Bluetooth APIs. Both identities are marked connectable, so that flag does not help select the usable identity. We have not yet established that one address type consistently succeeds while the other fails. I have filed FB25543615 with the sysdiagnose and Bluetooth HCI PacketLogger captures. I’m posting separately from the extended-advertising discovery issue identified as r.188123531, which Apple clarified affects iPhone 17 and newer. This reproduction is on an iPhone 15 Pro and concerns duplicate identities, rather than missing discovery. I’m not assuming the two issues share a cause. Has anyone else observed this after moving from iOS 26 to iOS 27? In particular: What could cause the same address to be reported as both Public and Random, producing separate Core Bluetooth UUIDs? Is there a supported way for an application to distinguish the usable identity before attempting a connection? What additional controller traces or over-the-air evidence would help determine where the address-type inconsistency originates?
0
0
73
1w
iPhone 17 / iOS 27.2: BLE extended advertising discovery fails approximately 90–95% of the time
We are investigating a severe BLE extended-advertising discovery issue on an iPhone 17 running iOS 27.2 (24B119). The phone fails to discover our peripherals approximately 90–95% of the time, based on our testing estimate. On rare occasions discovery succeeds, and the peripheral can then be connected. We have filed FB25463740, with diagnostic captures and a comparison of successful and failing behavior. Earlier iOS behavior Extended-advertising discovery and connection worked without issues in our previous iOS 26 testing. Failures became apparent with iOS 27, with behavior varying by iPhone model. We do not have a verified iOS 26 baseline for this particular iPhone 17, so we are treating an OS regression as a possibility rather than a confirmed cause. Test configuration Affected phone: iPhone 17, iOS 27.2 (24B119). Working comparison: iPhone 16, also running iOS 27.2 (24B119). Advertising: extended advertising with a 1M primary PHY, 2M secondary PHY, and 31-byte advertising data. Scanning: nRF Connect in the foreground, without a service UUID filter. Both phones were near the same powered-on peripherals, with advertising configuration unchanged during the comparison. Observed behavior The iPhone 16 discovers the extended-advertising peripherals. The iPhone 17 usually does not, even while discovering other nearby BLE devices. Switching the peripherals to legacy advertising provides reliable discovery on the tested iPhone 17. When extended-advertising discovery does succeed, connection works. The issue reproduces in nRF Connect as well as our application. What the captures show During failing foreground scans, the iPhone 17 receives thousands of legacy advertising reports, but neither target peripheral appears in its HCI packet log. A later capture contains rare successful extended-advertising receptions from both peripherals. These reports contain the same 31-byte payloads received by the working iPhone 16 and identify the secondary PHY as 2M. That capture also records a successful connection using 2M in both directions. Successful and failing scans occur on the same iPhone 17 with identical checked scan-start command sequences. The commands complete successfully. This does not establish that all internal controller state is identical. Wi-Fi disconnection preceded one successful period, but repeating that action did not reproduce success. We have not established Wi-Fi coexistence or primary-to-auxiliary timing as the cause. Questions Has anyone observed similar extended-advertising discovery failures on iPhone 17 or other models running iOS 27? If so, which phone models, iOS builds, peripheral chipsets, and advertising PHYs are involved? Does legacy advertising remain reliable? Are there any known issues or supported workarounds for this behavior? For Apple engineering, FB25463740 includes captures covering both successful and failing periods that may help distinguish reception, auxiliary-channel scheduling, and reporting/filtering problems.
6
0
312
1w
Not receiving payments, bank account + tax info is setup and correct
I am pulling my hair out. I have a appstore connect profile, I can see the amount that I am owed, but I do not receive payments. I have tried to contact apple about this, I have received mails with a case number, but no response or update ever. First ticket was created in September. My bank account is active, I have signed and accepted all required tax agreements etc. Is there anyone that can help me? Also, I don;t see the appropriate topic and subtopic for this.
0
0
44
1w
NSE Filtering Entitlement lost after app transfer, now blocked from shipping updates to a live app (Request ID: 3T2KH34RB3)
Hi all, Our iOS app is an end-to-end encrypted collaboration app with live customers. It was transferred to our new developer team on October 14. Before the transfer, the app had the Notification Service Extension Filtering entitlement. The entitlement did not carry over to the receiving team, and we didn't realize that until after the transfer was complete. Our pushes are end-to-end encrypted, so we can't ship a build with important updates to our customers without it. What we've done so far: Submitted the entitlement request (Request ID: 3T2KH34RB3) Opened an Apple Developer Support case on October 26 (Case #103009182658) asking for the request to be expedited Followed up by email several times and through the support form, with no response so far Our questions: Is there a process for restoring a previously approved entitlement to the receiving team after an app transfer, rather than going through a new review? Can someone confirm our request is in the review queue and share an estimated timeline? Is there anything else we can provide to help move this forward?
0
0
49
1w
StoreKit Testing on iOS 27.2 Simulator returns the refunded renewal when repurchasing a subscription
I'm testing auto-renewable subscriptions with a local .storekit configuration in Xcode 27.2 (27B52). With the same app and configuration on iPhone 17 simulators, I get different results on iOS 26.2 (23C54) and iOS 27.2 (24B8117). Set SKTestSession.timeRate to .oneRenewalEveryThirtySeconds, then purchase an auto-renewable subscription in the app with StoreKit 2. Wait for the original period to expire and the first automatic renewal to appear. Refund that renewal using SKTestSession.refundTransaction(identifier:) and wait for the app to receive the revocation. While the app is still running, purchase the same product again and inspect the verified transaction returned directly by Product.purchase(). Both runtimes return .success with a verified transaction. On iOS 26.2, the repurchase returns a new transaction ID with revocationDate == nil, and Transaction.currentEntitlements contains it. On iOS 27.2, the result has the same ID, purchaseDate, and non-nil revocationDate as the refunded renewal. The current entitlement check yields no verified unrevoked transaction. This reproduced for both a monthly and a three-month subscription. The monthly case also reproduced when calling Product.purchase() without an appAccountToken option. Is this a known issue in StoreKit Testing on iOS 27.2 Simulator? Is there a supported way to test the repurchase path while preserving the refunded transaction in the test history?
0
0
69
1w
RLIMIT_AS across posix_spawn and exec on Apple silicon: documented guarantees?
What supported behaviour, if any, may applications rely on for inherited RLIMIT_AS when launching a process on macOS on Apple silicon using posix_spawn and subsequent exec transitions? An older published XNU header defines RLIMIT_AS: XNU resource.h (immutable revision) I am looking for the documented support and virtual-address-space accounting scope, including exclusions. For a finite limit already set in the launching process, does any documented guarantee cover the new process from its first executable or dynamic-loader mapping and across later exec transitions, or does the limit take effect at a later stage? If the limit cannot be applied, does launch abort before any target user code executes, what failure is reported, and can mappings occur before that failure? An explicit statement that this guarantee is not provided would also be helpful. My question concerns virtual address space, rather than resident memory or a language runtime's heap. A successful setter or getrlimit readback by itself does not answer when the limit takes effect. If an answer relies on published XNU code, what public release/build record would be needed to relate an immutable source revision to a released macOS build on Apple silicon, and what limits apply to that correspondence? I am asking about the supported public interface and publicly available documentation/source, without requesting private implementation details. A link to an existing answer or the documented boundary would be appreciated.
5
0
251
1w
Supported read/write handoff of a sandbox-container PNG to Preview using NSWorkspace
Hello, I am preparing an existing macOS screenshot utility for distribution through the Mac App Store. The app stores captured PNG files under its temporary directory: FileManager.default.temporaryDirectory .appendingPathComponent("ShelfDragPoC/Captures", isDirectory: true) A context-menu "Edit" action passes the original PNG URL to Preview using NSWorkspace. The app does not create an editing copy. Relevant code: import AppKit @MainActor func openInPreview(_ url: URL) { guard let previewURL = NSWorkspace.shared.urlForApplication( withBundleIdentifier: "com.apple.Preview" ) else { return } let configuration = NSWorkspace.OpenConfiguration() configuration.activates = true NSWorkspace.shared.open( [url], withApplicationAt: previewURL, configuration: configuration ) { _, _ in } } The app monitors the original PNG URL for file changes and refreshes its thumbnail when changes are detected. Observed behavior: In the existing non-sandboxed app, rotating an image in Preview updates the original PNG and the thumbnail without requiring Command-S. In the sandboxed validation app, Preview opens the image, but editing results in a separate copy. When closing the edited document, Preview displays a message indicating that the original document will not be changed. The original PNG and the app's thumbnail are not updated. The Preview launch code and file watcher are unchanged between the non-sandboxed and sandboxed versions. The sandboxed app has these entitlements: com.apple.security.app-sandbox com.apple.security.files.user-selected.read-write com.apple.security.files.bookmarks.app-scope The app-scoped bookmark is used for a separate Desktop export feature. The PNG opened in Preview remains in the app's sandbox container. My question: Is there a supported public API that allows a sandboxed Mac App Store app to open its own container-resident PNG in Preview with the permissions required for in-place editing and normal automatic saving? Ideally, the user would only need to select "Edit" once, without an additional file-selection dialog or an explicit Save command. We want to preserve the original PNG URL, keep App Sandbox enabled, and avoid automatically exporting temporary images to the Desktop. If this workflow is not supported, what is Apple's recommended approach? Thank you.
13
0
525
1w
Choosing a TLS server identity by client address with NWListener
I run an HTTPS server on NWListener (iOS and macOS) that serves several identities from one listener on port 443, picked per handshake in sec_protocol_options_set_challenge_block, as suggested in this thread. That works well for every handshake that carries a server name. The trouble is handshakes without one. Clients on the LAN connect by IP address, so they send no SNI (RFC 6066 keeps IP literals out of it), and they trust a self-signed certificate through a configuration profile. Internet clients and scanners that reach the public address through the router's port forward also often arrive without SNI. The two groups should get different certificates, and the only thing that tells them apart is the client's address. The listener knows it in newConnectionHandler, but the challenge block never sees it. What I tried: sec_protocol_metadata_t has accessors for the server name, ALPN, version, cipher suite and so on, but I can't find one for the connection's endpoints. Setting a challenge block on the accepted connection's own TLS options before start(): listener.newConnectionHandler = { connection in let remote = connection.endpoint if let tls = connection.parameters.defaultProtocolStack.applicationProtocols .compactMap({ $0 as? NWProtocolTLS.Options }).first { sec_protocol_options_set_challenge_block(tls.securityProtocolOptions, { _, complete in complete(identity(for: remote)) }, queue) } connection.start(queue: queue) }This block never runs. The listener's own block answers every handshake (tested on macOS 27.2). My questions: Is there a supported way to choose the server identity per connection based on its endpoints, short of terminating TLS myself? Is the challenge block supported under TLS 1.3 by now? I also see it run twice for every handshake; is that expected? When a server-side handshake fails, connection.metadata(definition: NWProtocolTLS.definition) returns nil. Is there any way to learn which server name a failed handshake asked for, so it can be logged? I filed FB25541009 with a small sample project that shows all three.
2
0
90
1w
URL Filter (Oblivious HTTP) configuration In Review for almost a week with no feedback
Hello, I submitted a Network Extension URL Filter (Oblivious HTTP) configuration in CloudKit Console almost a week ago. It still says In Review / Waiting for Approval and I haven't heard anything back since the submission notice. I wanted to check whether anything is missing on my end. Just in case, the configuration ID is 60802ed4-abfa-4b20-a64e-0d35230f478a. The app is an open-source ad and tracker blocker from the developers of an existing content blocker with a large user base. On iPhone and iPad its system-wide blocking runs entirely through the URL filter. Until the configuration is approved the iOS app can't block anything at all, and our testers are left with a Mac-only product in the meantime. Because lookups go through Apple's relay to our own PIR server, we never learn which sites anyone visits. All four endpoints have been live since the day I submitted and the TXT records are in place. Every database we build also includes the www.apple.com/url-filter-test validation entry. Is there anything else I need to provide, or a rough timeline I should expect? Thank you in advance!
1
0
86
1w
BLE IOS27. When the device is connected to headphones, the Bluetooth controller does not tend to perform normal scheduling on BLE
We have an internet app that uses BLE COC to synchronize the call audio of Android devices to the iPhone side microphone. All of this functions normally, but if two conditions are met: upgrading to IOS27; Connect iPhone to headphones. So the up and down latency of our BLE COC data will be significant and increase proportionally with time. Through the analysis of the air interface logs, it can be seen that the number of retries for COC data on the air interface has significantly increased, and the interval between the other two packets is very large (far greater than the 30 millisecond conn interval). I would like to ask if Apple has adjusted the scheduling strategy of the Bluetooth controller on iOS 27, and how can we adapt to this situation? The attachment is a screenshot of the air interface log. The packet circled in the picture is sent from iPhone to Android, with an interval of 300+ms. It can be inferred that the iPhone protocol stack and Bluetooth controller have already squeezed a large amount of data, and our business bitrate is not high, only about 10K per second
4
0
151
1w
WatchOS 27 throttles BLE discoveries
Hi! We have an app that highly depends on CoreBluetooth including scanning for peripherals with an advertised serviceUUID. Our app sets the CBCentralManagerScanOptionAllowDuplicatesKey flag to true while scanning. Receiving continuous discovery events about nearby devices is key to measure the RSSI before connecting. Updating some of our test devices to watchOS 27 we noticed that our app is broken. To analyze further we created a simple app to compare behavior between watchOS 26 and 27, and the difference is clear. On the 27 device it behaves like the flag is ignored and we only receive a couple of callbacks to centralManager(_:didDiscover:advertisementData:rssi:) then it stops. We could not find any documentation declaring this as a new restriction or something regarding that has changed. Is this a bug, or is there a way to get the old behavior on the new OS? The example app used for testing is available here: https://github.com/levente-gulyas-skidata/WatchBLEExperiments (Change the serviceUUID for testing if needed) Thank you, Levi
3
4
337
1w
Title: StoreKit Sandbox: supportsMultiSeatPurchase is true, but pricingTerms contains no seatBased terms
We’re testing an annual multiseat subscription on a physical iPad. StoreKit returns the expected product and reports supportsMultiSeatPurchase == true, but its pricingTerms contains one term and no seatBased terms. Our app therefore cannot calculate a two-seat quote and stops before attempting a purchase. Environment iPad Air 11-inch (M3) iPadOS 27.3 beta (24C5037i) Xcode 27.3 beta (27C5020n) Development-signed app, version 1.0, diagnostic build 44 Physical-device testing with a US Sandbox purchaser App Store Connect configuration Annual auto-renewable subscription Multiseat purchases allowed Invitations provided by Apple Annual upfront availability enabled for the United States at USD 6.99 Subscription status: Prepare for Submission Sandbox purchases and renewals enabled Steps to reproduce Request the subscription using Product.products(for:). Confirm that the expected annual product is returned. Check supportsMultiSeatPurchase, which returns true. Inspect pricingTerms for supported upfront seatBased terms. Attempt to prepare a quote for two total seats. Actual result Total pricing terms: 1 Seat-based pricing terms: 0 Supported group pricing terms: 0 No purchase is attempted. Production sponsorship sales remain disabled. Expected result A supported upfront seat-based pricing term with Apple-provided pricing tiers that can be used to calculate a two-seat quote. Questions Is additional configuration or account eligibility required for Sandbox to return seat-based pricing terms? Must the subscription progress beyond Prepare for Submission before multiseat pricing can be tested? Can supportsMultiSeatPurchase legitimately return true while no seat-based pricing terms are available? If so, what conditions cause this? Is this a known limitation in this beta, and is there a supported workaround or recommended testing configuration? The issue was reproduced again on November 10, 2026, at approximately 9:57 PM Mountain Time. A sysdiagnose captured at 10:03:11 PM Mountain Time was attached privately to FB25451377. DTS directed us to post here under Case-ID: 23369152. We can provide a focused reproduction project if needed.
0
0
86
1w
synchronize a file's state with that on disk
Hello Dev, The App, which I am working on, uses fcopyfile() to copy file from external storage (USB, thunderbolt) to internal disk. Looks like this call provides the best performance. fcopyfile(from, to, nullptr, COPYFILE_DATA); I need to be sure the data is copied after the call. Are there any necessity to synchronize a file's state with that on disk the data? (e.g. call fsync()) Thank you in advance! Pavel
2
0
502
1w
Apple Pay ( auto update )
What is this? You want me to enable automatic updates just so I can use Apple Pay on macOS? Why? So whenever you decide to push an update, you can extract personal data without anyone noticing? Hahahah. Looks like Apple has become just like Windows nothing but bugs and background processes draining resources for no reason. Windows usesd to be like that before 8 years, and now you guys couldn't bear to be left behind either. Great just great. Love how you're using AI without putting an ounce of thought inot it. Updated to 27.2.1, Sifi is supposedly stopped and EVERYTHING is turned off, and yet there it is in Activity Monitor processes running and pegging system resoues at 100%. Just unbeliebale....
0
0
28
1w
iPhone 17 on iOS 27 cannot connect to a Bluetooth 4.0 BLE peripheral (works on older iPhones with iOS 27)
We have a BLE pulse oximeter (medical device, Bluetooth 4.0 module) that can no longer be connected from iPhone 17 running iOS 27.0.1 and 27.2. CBCentralManager.connect() never results in didConnect or didFailToConnect; the connection stays pending indefinitely. The same accessory works on: iPhone 17 with iOS 26.6.1 iPhone 15 with iOS 27.0.1 iPhone 14 Pro Max with iOS 26.5.2 The issue also reproduces with nRF Connect and LightBlue, so it does not appear to be specific to our app. Other BLE devices connect normally on the same iPhone 17. PacketLogger traces from iPhone 17 (failing) and iPhone 15 (working) are attached to FB25459075. It is possible that the accessory firmware does not fully follow the Bluetooth specification. However, many units are already in use by patients and may not be firmware-updatable. Questions: Is this a known issue with iPhone 17 on iOS 27? Could Apple consider an interoperability fix, since the same accessory works on iPhone 17 with iOS 26.6.1 and on older iPhone models with iOS 27? Is there any workaround we can apply in our app?
1
1
178
1w
Declared Age Range in sandbox: no sheet at launch, and the set per scenario
We are testing the Declared Age Range API with sandbox testers on an iPhone 17e with iOS 26.6.2 (Xcode 26.6, iOS 26.5 SDK). The app is not yet released; everything here is pre-release testing. We have filed three focused reports: FB25530441 (requestAgeRange returned .declinedSharing with no sheet), FB25530501 (the age that Age Assurance first shows at a sign-in against what the API reads), and FB25530513 (a selected scenario not reflected in requiredRegulatoryFeatures). Four questions remain that are not defects: When a sandbox tester has an Age Assurance scenario selected, should requestAgeRange present the sheet at launch, or answer from the scenario without showing one? Is there a way to see the sheet at launch in sandbox, as a first-time user would, so we can test the share and decline paths end to end? The article "Requesting people's age range information in your app" says the set's values "tell you which actions you need to take for compliance", and the sandbox page lists each scenario's age range, but we found neither saying which members each scenario produces. Please confirm: for each Age Assurance scenario, and for a tester with no scenario selected, what should requiredRegulatoryFeatures contain? Does the tester's App Store territory or creation date matter in sandbox? On 1 and 2. Our app calls requestAgeRange at launch when requiredRegulatoryFeatures contains .declaredAgeRangeRequired. On four days between October 31 and November 7, 2026, at every launch where we know it did make the request, Apple's age range sheet did not appear. Some requests we made by hand from a debug console returned the scenario's range with no sheet: on November 7, one on each of two testers on '13 - 15' returned a shared range of 13 to 15. One such request on October 31 did present the sheet; it is the only sheet on record across the four days (at a few launches the sheet was not written down separately). On 3. What we read on one tester, in this order, each scenario read before and after a relaunch unless noted: No scenario selected (signed in for the first time; Age Assurance showed no option selected), read after a relaunch only: none of the three members. '13 - 15, significant change approved', then '16 - 17, significant change declined', then 'Under 13, significant change approved': .declaredAgeRangeRequired and .significantAppChangeRequiresParentalConsent. '18+, age confirmed, significant change not applicable': .declaredAgeRangeRequired only. '18+, age confirmed, significant change applicable': .declaredAgeRangeRequired and .significantAppChangeRequiresAdultNotification. '18+, age not confirmed, significant change not applicable': .declaredAgeRangeRequired only. For these rows we read contains for the three members the iOS 26.5 SDK defines, so a member outside those three would not show. On November 5 we printed the whole set on 15 reads of sandbox testers, and no other member appeared.
0
0
73
1w
CloudKit CKShare architecture for family and teacher access with private data separation
Hi everyone, I'm an independent iOS developer currently working on a family sharing feature for an app designed to support children with additional communication and care needs. I'm using CloudKit and CKShare, and I'd really appreciate some architectural guidance before moving into live sharing. The idea is to allow a parent to manage their child's profile and invite family members or teachers to access specific information. For example: Family members could share communication boards, routines and visual supports. Teachers could access school-related information and make authorised changes. Teachers may also need to record daily observations such as toileting, seizures, eating, drinking and sensory events. Parents would control which categories of information teachers can access. Private family wellbeing records and caregiver notes must remain inaccessible unless explicitly shared. I've already successfully tested CloudKit Development connectivity on a physical iPhone, including account status, user identity and private database zone discovery. Before implementing the actual sharing functionality, I'd like to understand the best approach to managing permissions and keeping sensitive information separate. My main questions are: Would separate custom record zones and CKShare relationships be the recommended approach for isolating school-shared data from family-private data? Since CKShare permissions apply at the share level, what's the recommended way to let teachers edit selected information without accessing other sensitive records? For parent-controlled access to individual categories such as toileting or seizure observations, would separate shares or zones per category be advisable? When a parent revokes a teacher's access, what guarantees does CloudKit provide regarding future access, particularly for previously downloaded data? Is there a recommended approach for synchronising school-created observations back into a parent's private history without exposing unrelated family records? My aim is to keep the experience simple for parents and teachers while ensuring that privacy is enforced by the underlying CloudKit architecture rather than relying solely on UI restrictions. I'd really appreciate any advice, recommendations or examples from developers or Apple engineers who have worked with similar sharing requirements. Many thanks!
0
0
76
1w
HELP!! OPENING TOMORROW!!
HI! We have been in review for over a month with no communication and we open tomorrow! We initially were rejected saying apple pay did not work. However, in the test app apple pay worked fine. We really need this app to open our doors tomorrow!! Please advise! Thank you
Replies
0
Boosts
0
Views
52
Activity
1w
Kernel tag check fault after wake on Mac17 hardware, Google Chrome Helper, macOS 26.5–27.0.1 — related to r.172793638?
We're seeing a recurring kernel panic across six Mac17-family Macs (Mac17,2 / Mac17,4 / Mac17,8; T8142 and T6050) in a managed fleet. 34 panic logs collected 30 Sept – 9 Oct, all with the same signature: panic(cpu N caller ...): Kernel tag check fault (expected tagged address: 0x...028), esr 0x96000011 Faulting address is always at offset 0x28 of the object Same crash PC per build: kernel text exec base + 0x48da38 on 27.0/27.0.1, + 0x46a784 on 26.7, + 0x466ee0 on 26.5 Panicked task is "Google Chrome Helper" in all 34 cases, thread Chrome_ChildIOThread (Chrome's IPC/network I/O thread) Always 3–60 s after wake from sleep, usually a dark wake with the lid closed (overnight or after a 3–18 min sleep) No third-party kexts loaded; "Post-boot loaded kexts" lists only Apple drivers Affected builds: 26.5 (25F71), 26.7 (25G229), 27.0 (26A428), 27.0.1 (26A434). Not a regression from one update: a machine still on 26.5 panics identically. Only Mac17-family hardware is affected. Older Apple silicon Macs with the same software stack are fine. Present on every affected machine: Chrome PWAs (Gmail/Chat/Meet) running in the background, keeping Chrome's network service alive across sleep. On one machine Microsoft Edge is the primary browser and never panics; only Chrome Helper does. Microsoft Defender for Endpoint with its network filter (content filter) extension, MDM-managed. This looks related to thread 821372, where DTS described a kernel networking panic on M5-family hardware with a Network Extension present (r.172793638 / FB22401652), fixed in 26.5b2. We appear to be seeing a tag-check-fault variant on 26.5 release and later. Questions: Is this a known issue, and is it the same root cause as r.172793638? Is there a build where it's fixed? Any recommended mitigation beyond preventing sleep and quitting Chrome? Feedback Assistant: FB25128015 with panic logs and sysdiagnose. Happy to collect more data or test a build. Backtrace from a 27.0.1 panic (kernel text exec base 0xfffffe003aa54000), panic PC first: lr: 0xfffffe003aee1a38 lr: 0xfffffe003aeec580 lr: 0xfffffe003b12cf34 lr: 0xfffffe003b12dc50 lr: 0xfffffe003b07b1f8 lr: 0xfffffe003b07c758 lr: 0xfffffe003b237ff4 lr: 0xfffffe003ac787f0 lr: 0xfffffe003aa576ac lr: 0x000000018747a57c (userspace)
Replies
4
Boosts
0
Views
392
Activity
1w
iOS 27: duplicate BLE identities with extended advertising on iPhone 15 Pro; legacy advertising unaffected
On our iPhone 15 Pro running iOS 27.2 (24B119), a single physical BLE peripheral consistently appears as two separate scan results with different UUIDs. The issue reproduces consistently when the peripheral uses connectable BLE extended advertising with a 1M primary PHY and 2M secondary PHY. Switching the same peripheral to legacy advertising eliminates the duplicate scan results. The duplication is visible in both our application and nRF Connect, and we did not observe it on iOS 26. The duplicate results are visible in both our application and nRF Connect, so this is not specific to our application code or BLE library. The peripherals use a Silicon Labs BLE chipset and connectable BLE extended advertising with a 1M primary PHY and 2M secondary PHY. The interesting detail is in the captured bluetoothd logs: the same Bluetooth address, advertised local name, and manufacturer data appear under two UUIDs, but one identity is labeled Random and the other Public. Both are marked connectable. For example, one peripheral appears as: Local name: WD-883200239 Bluetooth address: 7C:C6:B6:58:F4:76 Random: F015AD07-F340-40DB-CEB5-5D602386B408 Public: 6D0F1C74-14B9-06B3-F64C-29E33CB8A065 On November 6, the logs report the Random identity at 08:07:07.496, followed by the Public identity at 08:07:08.505, with matching address bytes, local name, and manufacturer data. A second physical peripheral shows the same pattern. To clarify, these are different UUIDs for the same physical peripheral, not simply repeated discovery callbacks for one UUID. This creates ambiguity when selecting a peripheral for connection. The Public/Random distinction is visible in system diagnostics but is not exposed through supported Core Bluetooth APIs. Both identities are marked connectable, so that flag does not help select the usable identity. We have not yet established that one address type consistently succeeds while the other fails. I have filed FB25543615 with the sysdiagnose and Bluetooth HCI PacketLogger captures. I’m posting separately from the extended-advertising discovery issue identified as r.188123531, which Apple clarified affects iPhone 17 and newer. This reproduction is on an iPhone 15 Pro and concerns duplicate identities, rather than missing discovery. I’m not assuming the two issues share a cause. Has anyone else observed this after moving from iOS 26 to iOS 27? In particular: What could cause the same address to be reported as both Public and Random, producing separate Core Bluetooth UUIDs? Is there a supported way for an application to distinguish the usable identity before attempting a connection? What additional controller traces or over-the-air evidence would help determine where the address-type inconsistency originates?
Replies
0
Boosts
0
Views
73
Activity
1w
iPhone 17 / iOS 27.2: BLE extended advertising discovery fails approximately 90–95% of the time
We are investigating a severe BLE extended-advertising discovery issue on an iPhone 17 running iOS 27.2 (24B119). The phone fails to discover our peripherals approximately 90–95% of the time, based on our testing estimate. On rare occasions discovery succeeds, and the peripheral can then be connected. We have filed FB25463740, with diagnostic captures and a comparison of successful and failing behavior. Earlier iOS behavior Extended-advertising discovery and connection worked without issues in our previous iOS 26 testing. Failures became apparent with iOS 27, with behavior varying by iPhone model. We do not have a verified iOS 26 baseline for this particular iPhone 17, so we are treating an OS regression as a possibility rather than a confirmed cause. Test configuration Affected phone: iPhone 17, iOS 27.2 (24B119). Working comparison: iPhone 16, also running iOS 27.2 (24B119). Advertising: extended advertising with a 1M primary PHY, 2M secondary PHY, and 31-byte advertising data. Scanning: nRF Connect in the foreground, without a service UUID filter. Both phones were near the same powered-on peripherals, with advertising configuration unchanged during the comparison. Observed behavior The iPhone 16 discovers the extended-advertising peripherals. The iPhone 17 usually does not, even while discovering other nearby BLE devices. Switching the peripherals to legacy advertising provides reliable discovery on the tested iPhone 17. When extended-advertising discovery does succeed, connection works. The issue reproduces in nRF Connect as well as our application. What the captures show During failing foreground scans, the iPhone 17 receives thousands of legacy advertising reports, but neither target peripheral appears in its HCI packet log. A later capture contains rare successful extended-advertising receptions from both peripherals. These reports contain the same 31-byte payloads received by the working iPhone 16 and identify the secondary PHY as 2M. That capture also records a successful connection using 2M in both directions. Successful and failing scans occur on the same iPhone 17 with identical checked scan-start command sequences. The commands complete successfully. This does not establish that all internal controller state is identical. Wi-Fi disconnection preceded one successful period, but repeating that action did not reproduce success. We have not established Wi-Fi coexistence or primary-to-auxiliary timing as the cause. Questions Has anyone observed similar extended-advertising discovery failures on iPhone 17 or other models running iOS 27? If so, which phone models, iOS builds, peripheral chipsets, and advertising PHYs are involved? Does legacy advertising remain reliable? Are there any known issues or supported workarounds for this behavior? For Apple engineering, FB25463740 includes captures covering both successful and failing periods that may help distinguish reception, auxiliary-channel scheduling, and reporting/filtering problems.
Replies
6
Boosts
0
Views
312
Activity
1w
Not receiving payments, bank account + tax info is setup and correct
I am pulling my hair out. I have a appstore connect profile, I can see the amount that I am owed, but I do not receive payments. I have tried to contact apple about this, I have received mails with a case number, but no response or update ever. First ticket was created in September. My bank account is active, I have signed and accepted all required tax agreements etc. Is there anyone that can help me? Also, I don;t see the appropriate topic and subtopic for this.
Replies
0
Boosts
0
Views
44
Activity
1w
NSE Filtering Entitlement lost after app transfer, now blocked from shipping updates to a live app (Request ID: 3T2KH34RB3)
Hi all, Our iOS app is an end-to-end encrypted collaboration app with live customers. It was transferred to our new developer team on October 14. Before the transfer, the app had the Notification Service Extension Filtering entitlement. The entitlement did not carry over to the receiving team, and we didn't realize that until after the transfer was complete. Our pushes are end-to-end encrypted, so we can't ship a build with important updates to our customers without it. What we've done so far: Submitted the entitlement request (Request ID: 3T2KH34RB3) Opened an Apple Developer Support case on October 26 (Case #103009182658) asking for the request to be expedited Followed up by email several times and through the support form, with no response so far Our questions: Is there a process for restoring a previously approved entitlement to the receiving team after an app transfer, rather than going through a new review? Can someone confirm our request is in the review queue and share an estimated timeline? Is there anything else we can provide to help move this forward?
Replies
0
Boosts
0
Views
49
Activity
1w
StoreKit Testing on iOS 27.2 Simulator returns the refunded renewal when repurchasing a subscription
I'm testing auto-renewable subscriptions with a local .storekit configuration in Xcode 27.2 (27B52). With the same app and configuration on iPhone 17 simulators, I get different results on iOS 26.2 (23C54) and iOS 27.2 (24B8117). Set SKTestSession.timeRate to .oneRenewalEveryThirtySeconds, then purchase an auto-renewable subscription in the app with StoreKit 2. Wait for the original period to expire and the first automatic renewal to appear. Refund that renewal using SKTestSession.refundTransaction(identifier:) and wait for the app to receive the revocation. While the app is still running, purchase the same product again and inspect the verified transaction returned directly by Product.purchase(). Both runtimes return .success with a verified transaction. On iOS 26.2, the repurchase returns a new transaction ID with revocationDate == nil, and Transaction.currentEntitlements contains it. On iOS 27.2, the result has the same ID, purchaseDate, and non-nil revocationDate as the refunded renewal. The current entitlement check yields no verified unrevoked transaction. This reproduced for both a monthly and a three-month subscription. The monthly case also reproduced when calling Product.purchase() without an appAccountToken option. Is this a known issue in StoreKit Testing on iOS 27.2 Simulator? Is there a supported way to test the repurchase path while preserving the refunded transaction in the test history?
Replies
0
Boosts
0
Views
69
Activity
1w
RLIMIT_AS across posix_spawn and exec on Apple silicon: documented guarantees?
What supported behaviour, if any, may applications rely on for inherited RLIMIT_AS when launching a process on macOS on Apple silicon using posix_spawn and subsequent exec transitions? An older published XNU header defines RLIMIT_AS: XNU resource.h (immutable revision) I am looking for the documented support and virtual-address-space accounting scope, including exclusions. For a finite limit already set in the launching process, does any documented guarantee cover the new process from its first executable or dynamic-loader mapping and across later exec transitions, or does the limit take effect at a later stage? If the limit cannot be applied, does launch abort before any target user code executes, what failure is reported, and can mappings occur before that failure? An explicit statement that this guarantee is not provided would also be helpful. My question concerns virtual address space, rather than resident memory or a language runtime's heap. A successful setter or getrlimit readback by itself does not answer when the limit takes effect. If an answer relies on published XNU code, what public release/build record would be needed to relate an immutable source revision to a released macOS build on Apple silicon, and what limits apply to that correspondence? I am asking about the supported public interface and publicly available documentation/source, without requesting private implementation details. A link to an existing answer or the documented boundary would be appreciated.
Replies
5
Boosts
0
Views
251
Activity
1w
Supported read/write handoff of a sandbox-container PNG to Preview using NSWorkspace
Hello, I am preparing an existing macOS screenshot utility for distribution through the Mac App Store. The app stores captured PNG files under its temporary directory: FileManager.default.temporaryDirectory .appendingPathComponent("ShelfDragPoC/Captures", isDirectory: true) A context-menu "Edit" action passes the original PNG URL to Preview using NSWorkspace. The app does not create an editing copy. Relevant code: import AppKit @MainActor func openInPreview(_ url: URL) { guard let previewURL = NSWorkspace.shared.urlForApplication( withBundleIdentifier: "com.apple.Preview" ) else { return } let configuration = NSWorkspace.OpenConfiguration() configuration.activates = true NSWorkspace.shared.open( [url], withApplicationAt: previewURL, configuration: configuration ) { _, _ in } } The app monitors the original PNG URL for file changes and refreshes its thumbnail when changes are detected. Observed behavior: In the existing non-sandboxed app, rotating an image in Preview updates the original PNG and the thumbnail without requiring Command-S. In the sandboxed validation app, Preview opens the image, but editing results in a separate copy. When closing the edited document, Preview displays a message indicating that the original document will not be changed. The original PNG and the app's thumbnail are not updated. The Preview launch code and file watcher are unchanged between the non-sandboxed and sandboxed versions. The sandboxed app has these entitlements: com.apple.security.app-sandbox com.apple.security.files.user-selected.read-write com.apple.security.files.bookmarks.app-scope The app-scoped bookmark is used for a separate Desktop export feature. The PNG opened in Preview remains in the app's sandbox container. My question: Is there a supported public API that allows a sandboxed Mac App Store app to open its own container-resident PNG in Preview with the permissions required for in-place editing and normal automatic saving? Ideally, the user would only need to select "Edit" once, without an additional file-selection dialog or an explicit Save command. We want to preserve the original PNG URL, keep App Sandbox enabled, and avoid automatically exporting temporary images to the Desktop. If this workflow is not supported, what is Apple's recommended approach? Thank you.
Replies
13
Boosts
0
Views
525
Activity
1w
Choosing a TLS server identity by client address with NWListener
I run an HTTPS server on NWListener (iOS and macOS) that serves several identities from one listener on port 443, picked per handshake in sec_protocol_options_set_challenge_block, as suggested in this thread. That works well for every handshake that carries a server name. The trouble is handshakes without one. Clients on the LAN connect by IP address, so they send no SNI (RFC 6066 keeps IP literals out of it), and they trust a self-signed certificate through a configuration profile. Internet clients and scanners that reach the public address through the router's port forward also often arrive without SNI. The two groups should get different certificates, and the only thing that tells them apart is the client's address. The listener knows it in newConnectionHandler, but the challenge block never sees it. What I tried: sec_protocol_metadata_t has accessors for the server name, ALPN, version, cipher suite and so on, but I can't find one for the connection's endpoints. Setting a challenge block on the accepted connection's own TLS options before start(): listener.newConnectionHandler = { connection in let remote = connection.endpoint if let tls = connection.parameters.defaultProtocolStack.applicationProtocols .compactMap({ $0 as? NWProtocolTLS.Options }).first { sec_protocol_options_set_challenge_block(tls.securityProtocolOptions, { _, complete in complete(identity(for: remote)) }, queue) } connection.start(queue: queue) }This block never runs. The listener's own block answers every handshake (tested on macOS 27.2). My questions: Is there a supported way to choose the server identity per connection based on its endpoints, short of terminating TLS myself? Is the challenge block supported under TLS 1.3 by now? I also see it run twice for every handshake; is that expected? When a server-side handshake fails, connection.metadata(definition: NWProtocolTLS.definition) returns nil. Is there any way to learn which server name a failed handshake asked for, so it can be logged? I filed FB25541009 with a small sample project that shows all three.
Replies
2
Boosts
0
Views
90
Activity
1w
URL Filter (Oblivious HTTP) configuration In Review for almost a week with no feedback
Hello, I submitted a Network Extension URL Filter (Oblivious HTTP) configuration in CloudKit Console almost a week ago. It still says In Review / Waiting for Approval and I haven't heard anything back since the submission notice. I wanted to check whether anything is missing on my end. Just in case, the configuration ID is 60802ed4-abfa-4b20-a64e-0d35230f478a. The app is an open-source ad and tracker blocker from the developers of an existing content blocker with a large user base. On iPhone and iPad its system-wide blocking runs entirely through the URL filter. Until the configuration is approved the iOS app can't block anything at all, and our testers are left with a Mac-only product in the meantime. Because lookups go through Apple's relay to our own PIR server, we never learn which sites anyone visits. All four endpoints have been live since the day I submitted and the TXT records are in place. Every database we build also includes the www.apple.com/url-filter-test validation entry. Is there anything else I need to provide, or a rough timeline I should expect? Thank you in advance!
Replies
1
Boosts
0
Views
86
Activity
1w
BLE IOS27. When the device is connected to headphones, the Bluetooth controller does not tend to perform normal scheduling on BLE
We have an internet app that uses BLE COC to synchronize the call audio of Android devices to the iPhone side microphone. All of this functions normally, but if two conditions are met: upgrading to IOS27; Connect iPhone to headphones. So the up and down latency of our BLE COC data will be significant and increase proportionally with time. Through the analysis of the air interface logs, it can be seen that the number of retries for COC data on the air interface has significantly increased, and the interval between the other two packets is very large (far greater than the 30 millisecond conn interval). I would like to ask if Apple has adjusted the scheduling strategy of the Bluetooth controller on iOS 27, and how can we adapt to this situation? The attachment is a screenshot of the air interface log. The packet circled in the picture is sent from iPhone to Android, with an interval of 300+ms. It can be inferred that the iPhone protocol stack and Bluetooth controller have already squeezed a large amount of data, and our business bitrate is not high, only about 10K per second
Replies
4
Boosts
0
Views
151
Activity
1w
WatchOS 27 throttles BLE discoveries
Hi! We have an app that highly depends on CoreBluetooth including scanning for peripherals with an advertised serviceUUID. Our app sets the CBCentralManagerScanOptionAllowDuplicatesKey flag to true while scanning. Receiving continuous discovery events about nearby devices is key to measure the RSSI before connecting. Updating some of our test devices to watchOS 27 we noticed that our app is broken. To analyze further we created a simple app to compare behavior between watchOS 26 and 27, and the difference is clear. On the 27 device it behaves like the flag is ignored and we only receive a couple of callbacks to centralManager(_:didDiscover:advertisementData:rssi:) then it stops. We could not find any documentation declaring this as a new restriction or something regarding that has changed. Is this a bug, or is there a way to get the old behavior on the new OS? The example app used for testing is available here: https://github.com/levente-gulyas-skidata/WatchBLEExperiments (Change the serviceUUID for testing if needed) Thank you, Levi
Replies
3
Boosts
4
Views
337
Activity
1w
Title: StoreKit Sandbox: supportsMultiSeatPurchase is true, but pricingTerms contains no seatBased terms
We’re testing an annual multiseat subscription on a physical iPad. StoreKit returns the expected product and reports supportsMultiSeatPurchase == true, but its pricingTerms contains one term and no seatBased terms. Our app therefore cannot calculate a two-seat quote and stops before attempting a purchase. Environment iPad Air 11-inch (M3) iPadOS 27.3 beta (24C5037i) Xcode 27.3 beta (27C5020n) Development-signed app, version 1.0, diagnostic build 44 Physical-device testing with a US Sandbox purchaser App Store Connect configuration Annual auto-renewable subscription Multiseat purchases allowed Invitations provided by Apple Annual upfront availability enabled for the United States at USD 6.99 Subscription status: Prepare for Submission Sandbox purchases and renewals enabled Steps to reproduce Request the subscription using Product.products(for:). Confirm that the expected annual product is returned. Check supportsMultiSeatPurchase, which returns true. Inspect pricingTerms for supported upfront seatBased terms. Attempt to prepare a quote for two total seats. Actual result Total pricing terms: 1 Seat-based pricing terms: 0 Supported group pricing terms: 0 No purchase is attempted. Production sponsorship sales remain disabled. Expected result A supported upfront seat-based pricing term with Apple-provided pricing tiers that can be used to calculate a two-seat quote. Questions Is additional configuration or account eligibility required for Sandbox to return seat-based pricing terms? Must the subscription progress beyond Prepare for Submission before multiseat pricing can be tested? Can supportsMultiSeatPurchase legitimately return true while no seat-based pricing terms are available? If so, what conditions cause this? Is this a known limitation in this beta, and is there a supported workaround or recommended testing configuration? The issue was reproduced again on November 10, 2026, at approximately 9:57 PM Mountain Time. A sysdiagnose captured at 10:03:11 PM Mountain Time was attached privately to FB25451377. DTS directed us to post here under Case-ID: 23369152. We can provide a focused reproduction project if needed.
Replies
0
Boosts
0
Views
86
Activity
1w
synchronize a file's state with that on disk
Hello Dev, The App, which I am working on, uses fcopyfile() to copy file from external storage (USB, thunderbolt) to internal disk. Looks like this call provides the best performance. fcopyfile(from, to, nullptr, COPYFILE_DATA); I need to be sure the data is copied after the call. Are there any necessity to synchronize a file's state with that on disk the data? (e.g. call fsync()) Thank you in advance! Pavel
Replies
2
Boosts
0
Views
502
Activity
1w
Apple Pay ( auto update )
What is this? You want me to enable automatic updates just so I can use Apple Pay on macOS? Why? So whenever you decide to push an update, you can extract personal data without anyone noticing? Hahahah. Looks like Apple has become just like Windows nothing but bugs and background processes draining resources for no reason. Windows usesd to be like that before 8 years, and now you guys couldn't bear to be left behind either. Great just great. Love how you're using AI without putting an ounce of thought inot it. Updated to 27.2.1, Sifi is supposedly stopped and EVERYTHING is turned off, and yet there it is in Activity Monitor processes running and pegging system resoues at 100%. Just unbeliebale....
Replies
0
Boosts
0
Views
28
Activity
1w
iPhone 17 on iOS 27 cannot connect to a Bluetooth 4.0 BLE peripheral (works on older iPhones with iOS 27)
We have a BLE pulse oximeter (medical device, Bluetooth 4.0 module) that can no longer be connected from iPhone 17 running iOS 27.0.1 and 27.2. CBCentralManager.connect() never results in didConnect or didFailToConnect; the connection stays pending indefinitely. The same accessory works on: iPhone 17 with iOS 26.6.1 iPhone 15 with iOS 27.0.1 iPhone 14 Pro Max with iOS 26.5.2 The issue also reproduces with nRF Connect and LightBlue, so it does not appear to be specific to our app. Other BLE devices connect normally on the same iPhone 17. PacketLogger traces from iPhone 17 (failing) and iPhone 15 (working) are attached to FB25459075. It is possible that the accessory firmware does not fully follow the Bluetooth specification. However, many units are already in use by patients and may not be firmware-updatable. Questions: Is this a known issue with iPhone 17 on iOS 27? Could Apple consider an interoperability fix, since the same accessory works on iPhone 17 with iOS 26.6.1 and on older iPhone models with iOS 27? Is there any workaround we can apply in our app?
Replies
1
Boosts
1
Views
178
Activity
1w
Declared Age Range in sandbox: no sheet at launch, and the set per scenario
We are testing the Declared Age Range API with sandbox testers on an iPhone 17e with iOS 26.6.2 (Xcode 26.6, iOS 26.5 SDK). The app is not yet released; everything here is pre-release testing. We have filed three focused reports: FB25530441 (requestAgeRange returned .declinedSharing with no sheet), FB25530501 (the age that Age Assurance first shows at a sign-in against what the API reads), and FB25530513 (a selected scenario not reflected in requiredRegulatoryFeatures). Four questions remain that are not defects: When a sandbox tester has an Age Assurance scenario selected, should requestAgeRange present the sheet at launch, or answer from the scenario without showing one? Is there a way to see the sheet at launch in sandbox, as a first-time user would, so we can test the share and decline paths end to end? The article "Requesting people's age range information in your app" says the set's values "tell you which actions you need to take for compliance", and the sandbox page lists each scenario's age range, but we found neither saying which members each scenario produces. Please confirm: for each Age Assurance scenario, and for a tester with no scenario selected, what should requiredRegulatoryFeatures contain? Does the tester's App Store territory or creation date matter in sandbox? On 1 and 2. Our app calls requestAgeRange at launch when requiredRegulatoryFeatures contains .declaredAgeRangeRequired. On four days between October 31 and November 7, 2026, at every launch where we know it did make the request, Apple's age range sheet did not appear. Some requests we made by hand from a debug console returned the scenario's range with no sheet: on November 7, one on each of two testers on '13 - 15' returned a shared range of 13 to 15. One such request on October 31 did present the sheet; it is the only sheet on record across the four days (at a few launches the sheet was not written down separately). On 3. What we read on one tester, in this order, each scenario read before and after a relaunch unless noted: No scenario selected (signed in for the first time; Age Assurance showed no option selected), read after a relaunch only: none of the three members. '13 - 15, significant change approved', then '16 - 17, significant change declined', then 'Under 13, significant change approved': .declaredAgeRangeRequired and .significantAppChangeRequiresParentalConsent. '18+, age confirmed, significant change not applicable': .declaredAgeRangeRequired only. '18+, age confirmed, significant change applicable': .declaredAgeRangeRequired and .significantAppChangeRequiresAdultNotification. '18+, age not confirmed, significant change not applicable': .declaredAgeRangeRequired only. For these rows we read contains for the three members the iOS 26.5 SDK defines, so a member outside those three would not show. On November 5 we printed the whole set on 15 reads of sandbox testers, and no other member appeared.
Replies
0
Boosts
0
Views
73
Activity
1w
CloudKit CKShare architecture for family and teacher access with private data separation
Hi everyone, I'm an independent iOS developer currently working on a family sharing feature for an app designed to support children with additional communication and care needs. I'm using CloudKit and CKShare, and I'd really appreciate some architectural guidance before moving into live sharing. The idea is to allow a parent to manage their child's profile and invite family members or teachers to access specific information. For example: Family members could share communication boards, routines and visual supports. Teachers could access school-related information and make authorised changes. Teachers may also need to record daily observations such as toileting, seizures, eating, drinking and sensory events. Parents would control which categories of information teachers can access. Private family wellbeing records and caregiver notes must remain inaccessible unless explicitly shared. I've already successfully tested CloudKit Development connectivity on a physical iPhone, including account status, user identity and private database zone discovery. Before implementing the actual sharing functionality, I'd like to understand the best approach to managing permissions and keeping sensitive information separate. My main questions are: Would separate custom record zones and CKShare relationships be the recommended approach for isolating school-shared data from family-private data? Since CKShare permissions apply at the share level, what's the recommended way to let teachers edit selected information without accessing other sensitive records? For parent-controlled access to individual categories such as toileting or seizure observations, would separate shares or zones per category be advisable? When a parent revokes a teacher's access, what guarantees does CloudKit provide regarding future access, particularly for previously downloaded data? Is there a recommended approach for synchronising school-created observations back into a parent's private history without exposing unrelated family records? My aim is to keep the experience simple for parents and teachers while ensuring that privacy is enforced by the underlying CloudKit architecture rather than relying solely on UI restrictions. I'd really appreciate any advice, recommendations or examples from developers or Apple engineers who have worked with similar sharing requirements. Many thanks!
Replies
0
Boosts
0
Views
76
Activity
1w