Posts under App & System Services topic

Post

Replies

Boosts

Views

Activity

Screen Recording permission popup not shown & app not added to app list in Screen Recording settings
Requesting the Screen Recording permission seems broken on macOS 27.3 beta 2. I'd love to know whether this change is intentional or whether we can expect a fix before the stable macOS 27.3 release. Feedback report: FB25646769 Behavior until macOS 27.2 When an app calls CGRequestScreenCaptureAccess(), macOS shows the following popup: Additionally, the app is added to the app list in the “Screen & System Audio Recording” panel in the System Settings. It is toggled off by default and the user can easily toggle it on. Behavior on macOS 27.3 beta 2 When an app calls CGRequestScreenCaptureAccess(), no popup appears and the app is not added to the app list in the “Screen & System Audio Recording” panel in the System Settings. The user cannot easily grant the permission. What the user has to do to grant the permission on macOS 27.3 beta 2 It is not intuitive for the user to figure out how to grant the Screen Recording permission. Without any guidance, the user needs to: Click the little plus icon below the app list in the "Screen & System Audio Recording” panel in the System Settings Because the System Settings panel shows two app lists, the user needs to click the plus icon below the correct app list ("Screen & System Audio Recording", not "System Audio Recording Only") Find the app in the file picker and add it This is cumbersome and unintuitive. There's no explanation of what to do. The average user will be confused and will struggle to complete these tasks. Reproduction steps Install an app that requests the Screen Recording permission (e.g., Cap) Get to the onboarding step that requests the Screen Recording permission Observe that the permission request popup is not shown and that the app is not added to the System Settings panel
3
1
143
2d
Guidelines 3.1.1 and 3.1.3(c): enterprise-only access on iOS
Hello, I’m looking for guidance on how App Review Guidelines 3.1.1 and 3.1.3(c) apply to an enterprise learning platform with the following access model: Organizations purchase access for their employees through a business-to-business agreement. Employees sign in to the iOS app using accounts provided by their organization. They do not purchase access or pay within the app. Individual users may access the platform separately through the web or Android, but the iOS app is intended only for employees covered by an organization’s agreement. Would this model generally qualify for the enterprise services exception under Guideline 3.1.3(c)? If so, what information or configuration would help App Review verify that iOS access is limited to eligible organization-funded users? I understand that each app is reviewed on its specific implementation. I’d appreciate any guidance or relevant experience from developers who have dealt with a similar setup. Thank you!
0
0
31
2d
Accessory Access: IOUSBHostInterface can’t be opened after AAUSBAccessory.open() (QEMU-based VM app)
Hi, I’m building a macOS hypervisor app based on QEMU + Hypervisor.framework (a fork of the open-source UTM project). Following Quinn’s advice in DTS case 23599042, I’m trying to implement USB passthrough on macOS 27 with Accessory Access instead of com.apple.vm.device-access. Since the app doesn’t use the Virtualization framework, I take the IOUSBHostDevice from AAUSBAccessory.open(serviceQueue:) and forward the transfers to QEMU through usbredir. What works “Claim USB Accessory” capability (com.apple.developer.accessory-access.usb), plus com.apple.security.app-sandbox and com.apple.security.device.usb registerListener(:matchingCriteria:); the user assigns the device from the “Virtual Machine Accessories” menu bar item; usbAccessoryDidConnect fires open(serviceQueue:) returns an IOUSBHostDevice; control transfers with enqueueDeviceRequest work; configureWithValue(:matchInterfaces:) succeeds What fails Opening any interface. IOUSBHostInterface(__ioService:options:queue:interestHandler:) on the device’s child IOUSBHostInterface services always fails: Error: Unable to open io_service_t object and create user client. with reason: IOServiceOpen failed. Error: Failed to create IOUSBHostInterface. with reason: Failed [super init] IOUSBHostErrorDomain 0xe00002c9 I tried with the interfaces as delivered, after configureWithValue(1, matchInterfaces: false) and after configureWithValue(1, matchInterfaces: true). No sandbox violations are logged. Device: USB 3 mass storage stick. macOS 27.0.1, Xcode 27.2. Questions Is interface and pipe access (IOUSBHostInterface / IOUSBHostPipe) supposed to work for an AAUSBAccessory opened by an app that doesn’t use the Virtualization framework? If so, what’s the right way to get those objects? If not, is the default control endpoint the intended scope? In that case I’ll file a feedback report, since bulk and interrupt endpoints are needed for USB passthrough in non-Virtualization hypervisors. Thanks!
2
0
53
2d
Refund requests in the testing environment are never approved, only DECLINE resolves (consumables, non-renewing subscription) – FB25652374
We are testing refunds for consumables and a non-renewing subscription, installed from TestFlight (tester's own Apple Account, storefront VNM, iPhone 15, iOS 27.0.1), with App Store Server Notifications V2 on the sandbox URL. "Testing refund requests" says: "select any refund reason on the refund request sheet, and submit the sheet. The App Store automatically approves the refund request in the testing environment." What we see: DECLINE resolves every time, about 8 minutes after the CONSUMPTION_REQUEST: REFUND_DECLINED arrives whether our server answers refundPreference: DECLINE or the tester types DECLINE under Issue > Other. Nothing else resolves, for up to 43 hours so far (11 requests): no REFUND notification, no revocationDate in Get Transaction Info, empty Get Refund History. This covers: a listed reason with our server answering without refundPreference, answering GRANT_FULL (Send Consumption Information V2, inside the 5-minute window, 202), or not answering; GRANT_PRORATED and GRANT_FULL typed under Issue > Other. Every CONSUMPTION_REQUEST has consumptionRequestReason UNINTENDED_PURCHASE, even when the tester chose Issue > Other. Questions: Should a refund request in the testing environment be approved when the server answers without a preference, answers GRANT_FULL, or does not answer? Is the GRANT_PRORATED keyword still supported? Does refund testing require a Sandbox Apple Account instead of a TestFlight install? Full details, transaction IDs and decoded notification history are in FB25652374. Thread 743381 looks similar.
0
0
26
2d
DriverKit USB Transport entitlement for an iPadOS photo printer driver still "Submitted"
We're building an iPadOS photo booth app that prints to dye-sublimation photo printers over USB-C through a DriverKit USB driver. On 19 November 2026 we requested (request ID 32DURFLH96) com.apple.developer.driverkit, com.apple.developer.driverkit.transport.usb for vendor IDs 0x1452 (5202) and 0x1343 (4931) in a single configuration for our driver, and com.apple.developer.driverkit.userclient-access for our app. The request still shows "Submitted" and we never received a confirmation email. We've also opened Apple Developer Support case 103019360398. Is there anything else we should provide, or a better way to follow up?
0
0
24
2d
Shortcut action that returns a file stopped working on iPhones with iOS 27.2
I have a shortcut action ("Get file") that returns a file. It worked well until iOS 27.1 (with a slight glitch on iOS 18 RC: https://developer.apple.com/forums/thread/763630 ), but with iOS 27.2, I get the following error: "There was a problem running the shortcut "Get file"". The structure is simple: intentResponse.file = INFile(fileURL: fileURL, filename: fileName, typeIdentifier: nil) completion(intentResponse) returnUsing the debugger, I can tell that INFile() has returned, intentResponse.file has been set, and the issue happens in completion(). Weirdly, the other option (read the data from the file) does work (but it is limited in size): if let urlData = try? Data(contentsOf: fileURL) { intentResponse.file = INFile(data: urlData, filename: fileName, typeIdentifier: nil) completion(intentResponse) return }What could explain the difference between INFile(fileURL: fileURL and INFile(data: ? How can I work around this issue? To make things worse, it works in the simulator, it works on iPads, it works with iOS 27.1 and before. It seems to only affect physical iPhones running iOS 27.2.
0
0
40
2d
Can an iOS Custom Keyboard Legally Launch Its Containing App for a User-Initiated Speech Recording?
I’m developing an iOS application with a custom keyboard extension and a companion app. Our intended user experience: The user is typing in an app such as WhatsApp using our custom keyboard. They tap the Speech button. Our companion app opens automatically. The companion app establishes a microphone session. iOS returns the user to the original host app. The user continues dictating through the keyboard. What we have already implemented: A Swift-based custom keyboard and companion app. App Groups and Darwin notifications for communication between the two targets. Microphone recording through the companion app. Apple Speech Recognition with on-device recognition. A warm background audio session. Subsequent recordings and text insertion work on a physical iPhone once the warm session is established. Our current blocker: The keyboard extension cannot successfully open its companion app when the warm session is inactive. We previously tried NSExtensionContext.open(), but it did not work. We want to avoid private APIs, responder-chain workarounds, and anything that could violate App Store Review Guidelines. My questions: Does Apple provide any officially supported public API that allows a custom keyboard extension to launch its containing app in response to an explicit user tap? Can App Intents or ForegroundContinuableIntent legitimately achieve this from a keyboard extension? Does App Review Guideline 4.4.1 prohibit this particular user-initiated handoff? If direct launching is prohibited, what Apple-supported architecture or interaction pattern would you recommend for this use case? Is there a supported way for the companion app to return the user to the original host app after establishing the microphone session? We are looking for guidance based on actual iOS platform restrictions and supported APIs, preferably from developers who have shipped custom keyboard applications. Thank you.
1
0
45
2d
Which memory entitlements can an independent iOS developer use?
I'm researching the memory limits and capabilities available to ordinary third-party iOS applications. My project, Kairavox, is a native iOS application whose initial CPU design uses a software AArch64 interpreter. Its long-term goal is to run a genuine, unmodified iPadOS installation as a guest. Before making further architectural decisions, I want to understand what memory capabilities are actually available to independent developers. Our initial guest research target is an iPad 9th generation running iPadOS 27.2.1. The host iPhone model has not yet been fixed. I've found Apple's documentation for: Increased Memory Limit, with the key com.apple.developer.kernel.increased-memory-limit. Extended Virtual Addressing, with the key com.apple.developer.kernel.extended-virtual-addressing. Increased Debugging Memory Limit, which Apple describes as providing additional memory during development and internal testing. I'd appreciate clarification on the following for current iOS versions: Which iPhone models and iOS versions support each of these capabilities? Is there a public compatibility list? Can an independent developer request the Increased Memory Limit entitlement? If so, what is the current request and provisioning-profile process? Does Extended Virtual Addressing increase only address-space capacity, or can it also raise an app's physical-memory limit? What is the exact entitlement key for Increased Debugging Memory Limit, and what are its limits for development, ad hoc, and internal TestFlight builds? Are any of these capabilities available with free Personal Team signing? Does paid Apple Developer Program membership change eligibility, or is separate authorization required? If granted, may an app use additional available memory as backing for software-emulated guest RAM? Are there documented limits or workload restrictions? I understand that an entitlement would not reserve physical RAM or prevent memory pressure and termination. Apple's current iOS supported-capabilities table lists Extended Virtual Addressing and Increased Debugging Memory Limit, but I could not find Increased Memory Limit there. Is that table complete for this capability, or does availability depend on the device, account, or another process? I'm not assuming these entitlements are available to every developer. Documentation or specific eligibility guidance would be very helpful. Thank you.
1
0
49
2d
Is JIT execution possible for ordinary third-party iOS apps?
I'm researching whether a normally signed third-party iOS application can use Just-In-Time (JIT) compilation on a stock, unjailbroken iPhone. My project, Kairavox, aims to run a genuine, unmodified iPadOS installation as a guest inside a native iOS application. JIT compilation is central to our intended execution architecture: we want to translate and execute guest AArch64 instructions through dynamically generated native code. We intend to test through personal development signing and sideloading using AltStore or SideStore. App Store distribution is not a requirement. I've found Apple's documentation for: Allow Execution of Just-In-Time (JIT) Compiled Code Entitlement Porting Just-In-Time Compilers to Apple Silicon Alternative Browser Engines in the European Union However, the first two appear to concern the macOS Hardened Runtime context. Apple's alternative browser engine provisions also describe a specifically authorized exception, which does not describe our application. I'd appreciate clarification on what is supported for an ordinary third-party iOS app: Is there a documented iOS API or entitlement that allows a normally signed third-party app to allocate writable memory, generate machine code, and execute that code at runtime? Does iOS support MAP_JIT for ordinary third-party applications, or is it restricted to other Apple platforms or specially authorized applications? Is com.apple.security.cs.allow-jit exclusively a macOS Hardened Runtime entitlement, or does it have any application on iOS? Can an app using free Personal Team development signing execute JIT-generated code? Does paid Apple Developer Program membership change this? Do development, ad hoc, or other signing arrangements differ in their JIT permissions? Is there a documented process for an independent developer to request the necessary capability? Does installing an app through AltStore or SideStore change its OS-granted executable-memory permissions, or does it retain the permissions associated with its signed build? Are there any documented restrictions on using JIT-generated native code for CPU emulation or virtualization workloads? I understand that Apple's EU alternative-browser-engine authorization is a narrow exception for eligible browser applications. I'm not assuming it applies to Kairavox. The main question is whether an independent developer can build and test a JIT-based application on a stock iPhone using an officially supported signing and permission model. Thank you.
1
0
51
2d
verifyReceipt returns empty then historical transactions with different receipt metadata during an IAP flow
We are investigating two different production app receipts collected before and after an in-app purchase flow for the same signed-in user of our iOS app. Both receipts were validated against https://buy.itunes.apple.com/verifyReceipt. Both responses returned status = 0 and environment = Production, and both have the same bundle_id and app_item_id. However, their transaction histories and app receipt metadata differ substantially. Observed differences Receipt A (before the purchase flow): receipt.in_app is empty. latest_receipt_info, latest_receipt, and pending_renewal_info are absent. application_version is 31436; original_application_version is 25069. Receipt B (after the purchase flow, validated approximately 78 seconds later): receipt.in_app contains one historical auto-renewable subscription transaction. latest_receipt_info contains two historical subscription transactions; the later one includes promotional_offer_id and offer_code_ref_name. application_version is 31323; original_application_version is 18440. receipt_creation_date is approximately three months earlier than Receipt A's creation date, despite B being collected later in the flow. receipt.original_purchase_date differs by approximately two years. download_id and version_external_identifier also differ. The transactions shown in B predate this purchase flow. These responses alone do not establish that a new purchase completed successfully. What we know and what remains unconfirmed The same application user is involved before and after the flow. We have not yet independently confirmed continuity of the underlying Media & Purchases Apple Account. The supplied server logs do not contain the exact StoreKit callbacks or any receipt refresh/restore calls. We do not currently have a focused standalone reproduction project or confirmed device OS/tool versions for this occurrence. We understand that transaction contents can change as receipts are updated. What we need help understanding is the combination of an empty transaction history changing to historical subscriptions, an older receipt creation date, and different original app purchase metadata during one user's purchase flow. Questions Under what circumstances can this combination of changes occur? Could a cached receipt, receipt refresh/restoration, or a change in App Store account context explain it? Which StoreKit callbacks, receipt acquisition/refresh events, and other diagnostics should we capture to distinguish these possibilities without collecting Apple Account credentials? What is the recommended way to obtain and validate the applicable subscription history when the initial app receipt contains no in-app transactions? If Apple needs the original receipt payloads to investigate this occurrence, which private support or Feedback Assistant channel should we use? Raw receipt data, transaction identifiers, account tokens, download identifiers, and user-specific timestamps have been omitted from this public post. We can provide the original request/response files through an appropriate private Apple support channel. Any guidance from the StoreKit team would be appreciated.
0
0
154
2d
CarPlay Simulator (from Additional tools) stuck on "Connecting to phone" since March 4th
We're experiencing an issue where the CarPlay Simulator (from Apple Developer Additional Tools) stopped connecting to our iPhones as of March 4th, 2025. The simulator gets stuck indefinitely on "Connecting to phone" and never completes the pairing. Environment App: Oracle Field Service iOS app (with CarPlay support) Tool: CarPlay Simulator from Apple Developer Additional Tools (developer.apple.com/download/all/) Issue start date: Wednesday, March 4th, 2025 Tested on: Multiple Mac machines, multiple iPhones Multiple CarPlay Simulator versions tested What's happening The CarPlay Simulator launches but displays "Connecting to phone" indefinitely. It was working correctly prior to March 4th with no changes on our end. What still works CarPlay functions correctly when the same iPhone is connected to a real car, confirming the issue is specific to the simulator. Troubleshooting steps already attempted Reset permissions and re-added the simulator Forgot the simulator and re-paired it Changed the USB cable Tested on multiple Mac machines Tested on multiple iPhones Tried multiple versions of the CarPlay Simulator Confirmed no VPN is in use Confirmed with IT, no OS updates or enterprise restrictions were applied Questions Has anyone else experienced this since March 4th? Was there a change in CarPlay Simulator behavior or a requirement on the Apple side (certificate, entitlement, protocol) around that date? Is there a known workaround or fix?
6
7
2.2k
2d
[iOS 27.2.1 / iPhone 17 Pro] BLE Central app sporadically fails to detect region and interact with Peripheral
Hello everyone, I am developing a BLE-based room entry/exit authentication app and we are currently experiencing an intermittent issue where the app fails to respond to the reader. I am looking for any similar reports or potential workarounds. [Environment] Devices affected: iPhone 17 Pro (majority of user reports), iPhone Air (reproduced once internally) OS Version: iOS 27.2.1 [App Architecture] iOS App: Central Reader (Hardware): Peripheral [Issue Description] On the specific devices mentioned above, the reader and the iOS app sporadically fail to interact with each other. This unresponsiveness occurs at a frequency of approximately 1 out of 5 attempts. [Investigation Details] Our development team was able to reproduce this exact issue once on an iPhone Air. When analyzing the logs and behavior during this reproduction, we confirmed that although the device was physically well within the BLE region (range), the OS completely failed to detect that it was inside the region. [Questions] Is this a known bug regarding CoreBluetooth / CoreLocation region monitoring specific to iOS 27.2.1 or newer devices like the iPhone 17 Pro? If anyone has experienced this intermittent region detection failure on recent OS/device combinations, are there any known workarounds to force the detection or prevent the drops? Any insights or advice would be greatly appreciated. Thank you!
0
0
78
2d
AlarmKit Fixed Schedule Going off at Midnight
I am getting bug reports from users that occasionally the AlarmKit alarms scheduled by my app are going off exactly at midnight. In my app, users can set recurring alarms for sunrise/sunset etc. I implement this as fixed schedule alarms over the next 2-3 days with correct dates pre-computed at schedule time. I have a background task which is scheduled to run at noon every day to update the alarms for the next 2-3 days. Are there any limitations to the fixed schedule which might be causing this unintended behavior of going off at midnight?
7
2
942
2d
AlarmKit leaves an empty zombie Live Activity in Dynamic Island after swipe-dismiss while unlocked
Hi, We are the developers of Morning Call (https://morningcall.info), and we believe we may have identified an AlarmKit / system UI bug on iPhone. We can reproduce the same behavior not only in our app, but also in Apple’s official AlarmKit sample app, which strongly suggests this is a framework or system-level issue rather than an app-specific bug. Demonstration Video of producing zombie Live Activity https://www.youtube.com/watch?v=cZdF3oc8dVI Related Thread https://developer.apple.com/forums/thread/812006 https://developer.apple.com/forums/thread/817305 https://developer.apple.com/forums/thread/807335 Environment iPhone with Dynamic Island Alarm created using AlarmKit Device is unlocked when the alarm begins alerting Steps to reproduce Schedule an AlarmKit alarm. Wait for the alarm to alert while the device is unlocked. The alarm appears in Dynamic Island. Instead of tapping the intended stop or dismiss button, swipe the Dynamic Island presentation away. Expected result The alarm should be fully dismissed. The Live Activity should be removed. No empty UI should remain in Dynamic Island. Actual result The assigned AppIntent runs successfully. Our app code executes as expected. AlarmKit appears to stop the alarm correctly. However, an empty “zombie” Live Activity remains in Dynamic Island indefinitely. The user cannot clear it through normal interaction. Why this is a serious user-facing issue This is not just a cosmetic issue for us. From the user’s perspective, it looks like a Live Activity is permanently stuck in Dynamic Island. More importantly: Force-quitting the app does not remove it Deleting the app does not remove it In practice, many users conclude that our app has left a broken Live Activity running forever We receive repeated user complaints saying that the Live Activity “won’t go away” Because the remaining UI appears to be system-owned, users often do not realize that the only reliable recovery is to restart the phone. Most users do not discover that workaround on their own, so they instead assume the app is severely broken. Cases where the zombie state disappears Rebooting the phone Waiting for the next AlarmKit alert, then pressing the proper stop button on that alert Additional observations Inside our LiveActivityIntent, calling AlarmManager.shared.stop(id:) reports that the alarm has already been stopped by the system. We also tried inspecting Activity<AlarmAttributes<...>>.activities and calling end(..., dismissalPolicy: .immediate), but in this state no matching activity is exposed to the app. This suggests that the alarm itself has already been stopped, but the system-owned Live Activity UI is not being cleaned up correctly after the swipe-dismiss path. Why this does not appear to be an app logic issue The intent is invoked successfully. The alarm stop path is reached. The alarm is already considered stopped by the system. The remaining UI appears to be system-owned. The stuck UI persists even after our own cleanup logic has run. The stuck UI also survives app force-quit and app deletion.
12
13
3.2k
2d
Can’t submit IMDF! Approved for Indoor Maps Program, no upload path in ABR.
Has anyone recently found a working path to claim a venue and upload an IMDF in Apple Business Register? Our Locations page shows 0 locations with no option to add one. (Screenshot attached.) Our business is approved for the Indoor Maps Program, our location is approved/verified in Apple Business Register, and our IMDF file is complete and ready to submit. We just can’t find anywhere to submit it. The 2019 WWDC session “Introducing the Indoor Maps Program” shows a “Claim your location” flow and a per-venue upload dashboard that simply doesn’t exist in our account today. We emailed maps-indoor-support@apple.com on August 25 with no response. A few other threads here describe the same thing, IMDF or venue registration stuck with no visible next step, so this doesn’t look isolated to our account. Any pointers on where this actually happens now would help. This has been open almost three months with a completed file and nowhere to send it. I am trying to develop my app but cannot proceed without this piece.
0
0
45
2d
PermissionKit significant-change consent: is a parent's answer delivered if the app is closed?
Our app is not yet released. We have built, but not switched on, the parental consent step for a significant change: when requiredRegulatoryFeatures contains .significantAppChangeRequiresParentalConsent, the app creates PermissionQuestion(significantAppUpdateTopic: SignificantAppUpdateTopic(description:)), calls AskCenter.shared.ask(_:in:), and holds the changed app until an approval arrives. It listens with for await response in AskCenter.shared.responses(for: SignificantAppUpdateTopic.self) from launch, on every launch while an approval is owed. The ask and listen part runs on iOS 26.2 and later; the set is read on iOS 26.4 and later. We have seen iOS 27's askSignificantChangePermission(for:permissionFlow:in:) with .approveInPerson, which returns the answer to the caller; the questions below are about the Ask to Approve path through ask(_:in:). A parent may answer hours later, after the child has closed the app. "Creating a communication experience" says to obtain the sequence promptly after launch, and points to a background route for communication limits, but says nothing about SignificantAppUpdateTopic. The sample "Implementing age assurance and permissions" listens at its entry point but does not say what happens to an answer given while the app is closed. If the parent answers while the app is closed, is that response delivered on the next launch's responses(for: SignificantAppUpdateTopic.self)? Is a response delivered once, or again on every later launch? Does that differ for an approval and a decline? On the Ask to Approve path, is there a supported way for the app to be woken, or to fetch the current answer, so that it does not depend on a response arriving while it is running? Without an expirationDate, how long does a question stay open for the parent? What does ask do when a question on the same topic is already pending? After a decline, can the child send a new question? "Testing Age Assurance in Sandbox" says that for a selected scenario PermissionKit returns the associated response status. Does that response arrive through responses(for:) after ask, and can the closed-app case in question 1 be exercised in sandbox? We have not yet run this on a device. Environment: iPhone 17e, iOS 27.2.1. Xcode 26.6 (17F113) with the iOS 26.5 SDK.
0
0
40
2d
Declared Age Range: does a sandbox tester's Age Assurance setting reach other installs after sign-out?
The problem. We are trying to confirm, before release, what our app's age check will read on an App Store install. On a development-signed install, a sandbox tester's Age Assurance setting was still returned after the tester signed out. We want to know whether a TestFlight or App Store install would read the same state. The app is not yet released; everything here is pre-release testing. Questions On a development-signed install with no sandbox tester signed in, does the API answer from the device's real Apple Account as production would, or from sandbox state? Is a sandbox tester's Age Assurance setting expected to stay in effect after the tester signs out? If so, what clears it? Can that state reach a TestFlight install or an App Store install on the same device? Do TestFlight installs read production or sandbox for this API? How should a developer verify before release what an App Store install will read? Other developers have asked near questions 3 and 4 (threads 851245 and 854172) without an Apple answer. What we read (iPhone 17e, iOS 27.2.1; a small native sample app, development-signed, that reads requiredRegulatoryFeatures and calls requestAgeRange(ageGates: 16, in:)) With the device's own adult account and no sandbox tester signed in: [declaredAgeRangeRequired], sharing with a lower bound of 18, declaration confirmed, no sheet. We signed in a new sandbox tester and set Age Assurance to '13 - 15, significant change approved': the set gained .significantAppChangeRequiresParentalConsent, and the request returned 13 to 15 with .significantAppChangeApprovalRequired in activeParentalControls. After the tester signed out, with no sandbox tester signed in, reads still returned the tester's 13 to 15 on every read for the next 21 minutes, one of them after a restart, and again the next morning, about 16 hours later. No sheet was seen on any of these reads. The next morning we signed the same tester back in (its Age Assurance still showed '13 - 15'; the set read empty) and made one request by hand, which presented a sheet; we chose Share and it returned 16 or older, self-declared. We then set the tester to '18+, age confirmed, significant change not applicable' and signed it out. From then on, with no tester signed in, reads returned a lower bound of 18 again. On TestFlight. A TestFlight build of our app has no console, so we could not read what the API returned there. Once (iOS 26.6.2), three sandbox testers had used the phone earlier in the day, the last set to '13 - 15', and all were signed out. With the phone then signed out of every Apple Account, a TestFlight build opened in about a second. Just after, a development build of the same source read both .declaredAgeRangeRequired and .significantAppChangeRequiresParentalConsent and ended on the screen our app shows when the request returns anything other than a shared range of 16 or older. Environment: iPhone 17e, iOS 27.2.1 and iOS 26.6.2. Xcode 26.6 (17F113) with the iOS 26.5 SDK. Related Feedback: FB25530441, FB25530501, FB25530513.
0
0
41
2d
Declared Age Range: when can the requirement be absent or removed, and what if the read throws?
The problem. Our iOS app decides at launch whether to ask for a person's age range, from whether requiredRegulatoryFeatures contains .declaredAgeRangeRequired. The app is not yet released; everything here is pre-release testing. We want to confirm the cases where that member can be absent or can change, and what to do when the read fails. Questions Thread 815952 (Apple, March 2026) says the set could be empty while isEligibleForAgeFeatures is true. Can that case occur on iOS 27? The article "Requesting people's age range information in your app" says that in some regulated regions people "can't decline sharing". Is Texas one of those regions? Where .declaredAgeRangeRequired is present, can a decline remove it afterwards? Another developer reports Texas users who read the requirement and could still decline (thread 836191, no answer yet). What we saw in sandbox is below. Apple's news post of June 3, 2026 says the Texas requirements apply to new Apple Accounts in Texas from June 4, 2026. Does an account created before that date ever read .declaredAgeRangeRequired (iOS 26.4 or later), for example after moving to Texas or after an OS update? (A related question, about the sheet, is in thread 853955, no answer yet.) The requiredRegulatoryFeatures page says it throws notAvailable when the service is unavailable, and the article's example has a bare catch. When it throws, should the app treat the person as required, not required, or retry? (Another developer reports notAvailable after a device was switched from a parent's account to a child's, thread 854397, no answer yet. That report is theirs, not ours.) What we saw on a decline (question 2). In sandbox (iOS 26.6.2), with a tester on '13 - 15' signed in, a request we made by hand presented the sheet; we declined and it returned declinedSharing. A read after that, tester still on '13 - 15', did not contain .declaredAgeRangeRequired; it was present again once the tester was switched to an 18+ scenario. We had not read the set just before the decline. The device's own account later listed a decline for our app dated that day, so we cannot say which account the sheet belonged to. What we read (question 1). On iOS 26.6.2 we printed the whole set together with isEligibleForAgeFeatures on 15 reads of sandbox testers created in App Store Connect with region United States. isEligibleForAgeFeatures was true on every read where the set was not empty (7) and false on every read where it was empty (8). On iOS 27.2.1, with a small native sample app that reads the set and isEligibleForAgeFeatures and calls requestAgeRange(ageGates: 16, in:), every launch where we printed both had a non-empty set and true (7 launches). On two further launches the set was empty (a tester signed in, its Age Assurance showing '13 - 15') and we did not print isEligibleForAgeFeatures, so we cannot say whether those were the case in question 1. Environment: iPhone 17e, iOS 26.6.2 and iOS 27.2.1. Xcode 26.6 (17F113) with the iOS 26.5 SDK. Reads made from development builds. Related Feedback: FB25530441, FB25530501, FB25530513.
0
0
41
2d
Improve PTT System UI Visibility When Location Indicators Are Active
Observed Limitation When location services are active, the iOS location indicator may overlap with or hide the PTT blue button or system UI in the notch / Dynamic Island area. Requested Changes Ensure PTT controls remain visible and accessible when location indicators are displayed. Improve system UI positioning to prevent conflicts with other system indicators.
1
0
35
2d
Screen Recording permission popup not shown & app not added to app list in Screen Recording settings
Requesting the Screen Recording permission seems broken on macOS 27.3 beta 2. I'd love to know whether this change is intentional or whether we can expect a fix before the stable macOS 27.3 release. Feedback report: FB25646769 Behavior until macOS 27.2 When an app calls CGRequestScreenCaptureAccess(), macOS shows the following popup: Additionally, the app is added to the app list in the “Screen & System Audio Recording” panel in the System Settings. It is toggled off by default and the user can easily toggle it on. Behavior on macOS 27.3 beta 2 When an app calls CGRequestScreenCaptureAccess(), no popup appears and the app is not added to the app list in the “Screen & System Audio Recording” panel in the System Settings. The user cannot easily grant the permission. What the user has to do to grant the permission on macOS 27.3 beta 2 It is not intuitive for the user to figure out how to grant the Screen Recording permission. Without any guidance, the user needs to: Click the little plus icon below the app list in the "Screen & System Audio Recording” panel in the System Settings Because the System Settings panel shows two app lists, the user needs to click the plus icon below the correct app list ("Screen & System Audio Recording", not "System Audio Recording Only") Find the app in the file picker and add it This is cumbersome and unintuitive. There's no explanation of what to do. The average user will be confused and will struggle to complete these tasks. Reproduction steps Install an app that requests the Screen Recording permission (e.g., Cap) Get to the onboarding step that requests the Screen Recording permission Observe that the permission request popup is not shown and that the app is not added to the System Settings panel
Replies
3
Boosts
1
Views
143
Activity
2d
Guidelines 3.1.1 and 3.1.3(c): enterprise-only access on iOS
Hello, I’m looking for guidance on how App Review Guidelines 3.1.1 and 3.1.3(c) apply to an enterprise learning platform with the following access model: Organizations purchase access for their employees through a business-to-business agreement. Employees sign in to the iOS app using accounts provided by their organization. They do not purchase access or pay within the app. Individual users may access the platform separately through the web or Android, but the iOS app is intended only for employees covered by an organization’s agreement. Would this model generally qualify for the enterprise services exception under Guideline 3.1.3(c)? If so, what information or configuration would help App Review verify that iOS access is limited to eligible organization-funded users? I understand that each app is reviewed on its specific implementation. I’d appreciate any guidance or relevant experience from developers who have dealt with a similar setup. Thank you!
Replies
0
Boosts
0
Views
31
Activity
2d
Accessory Access: IOUSBHostInterface can’t be opened after AAUSBAccessory.open() (QEMU-based VM app)
Hi, I’m building a macOS hypervisor app based on QEMU + Hypervisor.framework (a fork of the open-source UTM project). Following Quinn’s advice in DTS case 23599042, I’m trying to implement USB passthrough on macOS 27 with Accessory Access instead of com.apple.vm.device-access. Since the app doesn’t use the Virtualization framework, I take the IOUSBHostDevice from AAUSBAccessory.open(serviceQueue:) and forward the transfers to QEMU through usbredir. What works “Claim USB Accessory” capability (com.apple.developer.accessory-access.usb), plus com.apple.security.app-sandbox and com.apple.security.device.usb registerListener(:matchingCriteria:); the user assigns the device from the “Virtual Machine Accessories” menu bar item; usbAccessoryDidConnect fires open(serviceQueue:) returns an IOUSBHostDevice; control transfers with enqueueDeviceRequest work; configureWithValue(:matchInterfaces:) succeeds What fails Opening any interface. IOUSBHostInterface(__ioService:options:queue:interestHandler:) on the device’s child IOUSBHostInterface services always fails: Error: Unable to open io_service_t object and create user client. with reason: IOServiceOpen failed. Error: Failed to create IOUSBHostInterface. with reason: Failed [super init] IOUSBHostErrorDomain 0xe00002c9 I tried with the interfaces as delivered, after configureWithValue(1, matchInterfaces: false) and after configureWithValue(1, matchInterfaces: true). No sandbox violations are logged. Device: USB 3 mass storage stick. macOS 27.0.1, Xcode 27.2. Questions Is interface and pipe access (IOUSBHostInterface / IOUSBHostPipe) supposed to work for an AAUSBAccessory opened by an app that doesn’t use the Virtualization framework? If so, what’s the right way to get those objects? If not, is the default control endpoint the intended scope? In that case I’ll file a feedback report, since bulk and interrupt endpoints are needed for USB passthrough in non-Virtualization hypervisors. Thanks!
Replies
2
Boosts
0
Views
53
Activity
2d
Refund requests in the testing environment are never approved, only DECLINE resolves (consumables, non-renewing subscription) – FB25652374
We are testing refunds for consumables and a non-renewing subscription, installed from TestFlight (tester's own Apple Account, storefront VNM, iPhone 15, iOS 27.0.1), with App Store Server Notifications V2 on the sandbox URL. "Testing refund requests" says: "select any refund reason on the refund request sheet, and submit the sheet. The App Store automatically approves the refund request in the testing environment." What we see: DECLINE resolves every time, about 8 minutes after the CONSUMPTION_REQUEST: REFUND_DECLINED arrives whether our server answers refundPreference: DECLINE or the tester types DECLINE under Issue > Other. Nothing else resolves, for up to 43 hours so far (11 requests): no REFUND notification, no revocationDate in Get Transaction Info, empty Get Refund History. This covers: a listed reason with our server answering without refundPreference, answering GRANT_FULL (Send Consumption Information V2, inside the 5-minute window, 202), or not answering; GRANT_PRORATED and GRANT_FULL typed under Issue > Other. Every CONSUMPTION_REQUEST has consumptionRequestReason UNINTENDED_PURCHASE, even when the tester chose Issue > Other. Questions: Should a refund request in the testing environment be approved when the server answers without a preference, answers GRANT_FULL, or does not answer? Is the GRANT_PRORATED keyword still supported? Does refund testing require a Sandbox Apple Account instead of a TestFlight install? Full details, transaction IDs and decoded notification history are in FB25652374. Thread 743381 looks similar.
Replies
0
Boosts
0
Views
26
Activity
2d
DriverKit USB Transport entitlement for an iPadOS photo printer driver still "Submitted"
We're building an iPadOS photo booth app that prints to dye-sublimation photo printers over USB-C through a DriverKit USB driver. On 19 November 2026 we requested (request ID 32DURFLH96) com.apple.developer.driverkit, com.apple.developer.driverkit.transport.usb for vendor IDs 0x1452 (5202) and 0x1343 (4931) in a single configuration for our driver, and com.apple.developer.driverkit.userclient-access for our app. The request still shows "Submitted" and we never received a confirmation email. We've also opened Apple Developer Support case 103019360398. Is there anything else we should provide, or a better way to follow up?
Replies
0
Boosts
0
Views
24
Activity
2d
Shortcut action that returns a file stopped working on iPhones with iOS 27.2
I have a shortcut action ("Get file") that returns a file. It worked well until iOS 27.1 (with a slight glitch on iOS 18 RC: https://developer.apple.com/forums/thread/763630 ), but with iOS 27.2, I get the following error: "There was a problem running the shortcut "Get file"". The structure is simple: intentResponse.file = INFile(fileURL: fileURL, filename: fileName, typeIdentifier: nil) completion(intentResponse) returnUsing the debugger, I can tell that INFile() has returned, intentResponse.file has been set, and the issue happens in completion(). Weirdly, the other option (read the data from the file) does work (but it is limited in size): if let urlData = try? Data(contentsOf: fileURL) { intentResponse.file = INFile(data: urlData, filename: fileName, typeIdentifier: nil) completion(intentResponse) return }What could explain the difference between INFile(fileURL: fileURL and INFile(data: ? How can I work around this issue? To make things worse, it works in the simulator, it works on iPads, it works with iOS 27.1 and before. It seems to only affect physical iPhones running iOS 27.2.
Replies
0
Boosts
0
Views
40
Activity
2d
Can an iOS Custom Keyboard Legally Launch Its Containing App for a User-Initiated Speech Recording?
I’m developing an iOS application with a custom keyboard extension and a companion app. Our intended user experience: The user is typing in an app such as WhatsApp using our custom keyboard. They tap the Speech button. Our companion app opens automatically. The companion app establishes a microphone session. iOS returns the user to the original host app. The user continues dictating through the keyboard. What we have already implemented: A Swift-based custom keyboard and companion app. App Groups and Darwin notifications for communication between the two targets. Microphone recording through the companion app. Apple Speech Recognition with on-device recognition. A warm background audio session. Subsequent recordings and text insertion work on a physical iPhone once the warm session is established. Our current blocker: The keyboard extension cannot successfully open its companion app when the warm session is inactive. We previously tried NSExtensionContext.open(), but it did not work. We want to avoid private APIs, responder-chain workarounds, and anything that could violate App Store Review Guidelines. My questions: Does Apple provide any officially supported public API that allows a custom keyboard extension to launch its containing app in response to an explicit user tap? Can App Intents or ForegroundContinuableIntent legitimately achieve this from a keyboard extension? Does App Review Guideline 4.4.1 prohibit this particular user-initiated handoff? If direct launching is prohibited, what Apple-supported architecture or interaction pattern would you recommend for this use case? Is there a supported way for the companion app to return the user to the original host app after establishing the microphone session? We are looking for guidance based on actual iOS platform restrictions and supported APIs, preferably from developers who have shipped custom keyboard applications. Thank you.
Replies
1
Boosts
0
Views
45
Activity
2d
Which memory entitlements can an independent iOS developer use?
I'm researching the memory limits and capabilities available to ordinary third-party iOS applications. My project, Kairavox, is a native iOS application whose initial CPU design uses a software AArch64 interpreter. Its long-term goal is to run a genuine, unmodified iPadOS installation as a guest. Before making further architectural decisions, I want to understand what memory capabilities are actually available to independent developers. Our initial guest research target is an iPad 9th generation running iPadOS 27.2.1. The host iPhone model has not yet been fixed. I've found Apple's documentation for: Increased Memory Limit, with the key com.apple.developer.kernel.increased-memory-limit. Extended Virtual Addressing, with the key com.apple.developer.kernel.extended-virtual-addressing. Increased Debugging Memory Limit, which Apple describes as providing additional memory during development and internal testing. I'd appreciate clarification on the following for current iOS versions: Which iPhone models and iOS versions support each of these capabilities? Is there a public compatibility list? Can an independent developer request the Increased Memory Limit entitlement? If so, what is the current request and provisioning-profile process? Does Extended Virtual Addressing increase only address-space capacity, or can it also raise an app's physical-memory limit? What is the exact entitlement key for Increased Debugging Memory Limit, and what are its limits for development, ad hoc, and internal TestFlight builds? Are any of these capabilities available with free Personal Team signing? Does paid Apple Developer Program membership change eligibility, or is separate authorization required? If granted, may an app use additional available memory as backing for software-emulated guest RAM? Are there documented limits or workload restrictions? I understand that an entitlement would not reserve physical RAM or prevent memory pressure and termination. Apple's current iOS supported-capabilities table lists Extended Virtual Addressing and Increased Debugging Memory Limit, but I could not find Increased Memory Limit there. Is that table complete for this capability, or does availability depend on the device, account, or another process? I'm not assuming these entitlements are available to every developer. Documentation or specific eligibility guidance would be very helpful. Thank you.
Replies
1
Boosts
0
Views
49
Activity
2d
Is JIT execution possible for ordinary third-party iOS apps?
I'm researching whether a normally signed third-party iOS application can use Just-In-Time (JIT) compilation on a stock, unjailbroken iPhone. My project, Kairavox, aims to run a genuine, unmodified iPadOS installation as a guest inside a native iOS application. JIT compilation is central to our intended execution architecture: we want to translate and execute guest AArch64 instructions through dynamically generated native code. We intend to test through personal development signing and sideloading using AltStore or SideStore. App Store distribution is not a requirement. I've found Apple's documentation for: Allow Execution of Just-In-Time (JIT) Compiled Code Entitlement Porting Just-In-Time Compilers to Apple Silicon Alternative Browser Engines in the European Union However, the first two appear to concern the macOS Hardened Runtime context. Apple's alternative browser engine provisions also describe a specifically authorized exception, which does not describe our application. I'd appreciate clarification on what is supported for an ordinary third-party iOS app: Is there a documented iOS API or entitlement that allows a normally signed third-party app to allocate writable memory, generate machine code, and execute that code at runtime? Does iOS support MAP_JIT for ordinary third-party applications, or is it restricted to other Apple platforms or specially authorized applications? Is com.apple.security.cs.allow-jit exclusively a macOS Hardened Runtime entitlement, or does it have any application on iOS? Can an app using free Personal Team development signing execute JIT-generated code? Does paid Apple Developer Program membership change this? Do development, ad hoc, or other signing arrangements differ in their JIT permissions? Is there a documented process for an independent developer to request the necessary capability? Does installing an app through AltStore or SideStore change its OS-granted executable-memory permissions, or does it retain the permissions associated with its signed build? Are there any documented restrictions on using JIT-generated native code for CPU emulation or virtualization workloads? I understand that Apple's EU alternative-browser-engine authorization is a narrow exception for eligible browser applications. I'm not assuming it applies to Kairavox. The main question is whether an independent developer can build and test a JIT-based application on a stock iPhone using an officially supported signing and permission model. Thank you.
Replies
1
Boosts
0
Views
51
Activity
2d
verifyReceipt returns empty then historical transactions with different receipt metadata during an IAP flow
We are investigating two different production app receipts collected before and after an in-app purchase flow for the same signed-in user of our iOS app. Both receipts were validated against https://buy.itunes.apple.com/verifyReceipt. Both responses returned status = 0 and environment = Production, and both have the same bundle_id and app_item_id. However, their transaction histories and app receipt metadata differ substantially. Observed differences Receipt A (before the purchase flow): receipt.in_app is empty. latest_receipt_info, latest_receipt, and pending_renewal_info are absent. application_version is 31436; original_application_version is 25069. Receipt B (after the purchase flow, validated approximately 78 seconds later): receipt.in_app contains one historical auto-renewable subscription transaction. latest_receipt_info contains two historical subscription transactions; the later one includes promotional_offer_id and offer_code_ref_name. application_version is 31323; original_application_version is 18440. receipt_creation_date is approximately three months earlier than Receipt A's creation date, despite B being collected later in the flow. receipt.original_purchase_date differs by approximately two years. download_id and version_external_identifier also differ. The transactions shown in B predate this purchase flow. These responses alone do not establish that a new purchase completed successfully. What we know and what remains unconfirmed The same application user is involved before and after the flow. We have not yet independently confirmed continuity of the underlying Media & Purchases Apple Account. The supplied server logs do not contain the exact StoreKit callbacks or any receipt refresh/restore calls. We do not currently have a focused standalone reproduction project or confirmed device OS/tool versions for this occurrence. We understand that transaction contents can change as receipts are updated. What we need help understanding is the combination of an empty transaction history changing to historical subscriptions, an older receipt creation date, and different original app purchase metadata during one user's purchase flow. Questions Under what circumstances can this combination of changes occur? Could a cached receipt, receipt refresh/restoration, or a change in App Store account context explain it? Which StoreKit callbacks, receipt acquisition/refresh events, and other diagnostics should we capture to distinguish these possibilities without collecting Apple Account credentials? What is the recommended way to obtain and validate the applicable subscription history when the initial app receipt contains no in-app transactions? If Apple needs the original receipt payloads to investigate this occurrence, which private support or Feedback Assistant channel should we use? Raw receipt data, transaction identifiers, account tokens, download identifiers, and user-specific timestamps have been omitted from this public post. We can provide the original request/response files through an appropriate private Apple support channel. Any guidance from the StoreKit team would be appreciated.
Replies
0
Boosts
0
Views
154
Activity
2d
CarPlay Simulator (from Additional tools) stuck on "Connecting to phone" since March 4th
We're experiencing an issue where the CarPlay Simulator (from Apple Developer Additional Tools) stopped connecting to our iPhones as of March 4th, 2025. The simulator gets stuck indefinitely on "Connecting to phone" and never completes the pairing. Environment App: Oracle Field Service iOS app (with CarPlay support) Tool: CarPlay Simulator from Apple Developer Additional Tools (developer.apple.com/download/all/) Issue start date: Wednesday, March 4th, 2025 Tested on: Multiple Mac machines, multiple iPhones Multiple CarPlay Simulator versions tested What's happening The CarPlay Simulator launches but displays "Connecting to phone" indefinitely. It was working correctly prior to March 4th with no changes on our end. What still works CarPlay functions correctly when the same iPhone is connected to a real car, confirming the issue is specific to the simulator. Troubleshooting steps already attempted Reset permissions and re-added the simulator Forgot the simulator and re-paired it Changed the USB cable Tested on multiple Mac machines Tested on multiple iPhones Tried multiple versions of the CarPlay Simulator Confirmed no VPN is in use Confirmed with IT, no OS updates or enterprise restrictions were applied Questions Has anyone else experienced this since March 4th? Was there a change in CarPlay Simulator behavior or a requirement on the Apple side (certificate, entitlement, protocol) around that date? Is there a known workaround or fix?
Replies
6
Boosts
7
Views
2.2k
Activity
2d
[iOS 27.2.1 / iPhone 17 Pro] BLE Central app sporadically fails to detect region and interact with Peripheral
Hello everyone, I am developing a BLE-based room entry/exit authentication app and we are currently experiencing an intermittent issue where the app fails to respond to the reader. I am looking for any similar reports or potential workarounds. [Environment] Devices affected: iPhone 17 Pro (majority of user reports), iPhone Air (reproduced once internally) OS Version: iOS 27.2.1 [App Architecture] iOS App: Central Reader (Hardware): Peripheral [Issue Description] On the specific devices mentioned above, the reader and the iOS app sporadically fail to interact with each other. This unresponsiveness occurs at a frequency of approximately 1 out of 5 attempts. [Investigation Details] Our development team was able to reproduce this exact issue once on an iPhone Air. When analyzing the logs and behavior during this reproduction, we confirmed that although the device was physically well within the BLE region (range), the OS completely failed to detect that it was inside the region. [Questions] Is this a known bug regarding CoreBluetooth / CoreLocation region monitoring specific to iOS 27.2.1 or newer devices like the iPhone 17 Pro? If anyone has experienced this intermittent region detection failure on recent OS/device combinations, are there any known workarounds to force the detection or prevent the drops? Any insights or advice would be greatly appreciated. Thank you!
Replies
0
Boosts
0
Views
78
Activity
2d
AlarmKit Fixed Schedule Going off at Midnight
I am getting bug reports from users that occasionally the AlarmKit alarms scheduled by my app are going off exactly at midnight. In my app, users can set recurring alarms for sunrise/sunset etc. I implement this as fixed schedule alarms over the next 2-3 days with correct dates pre-computed at schedule time. I have a background task which is scheduled to run at noon every day to update the alarms for the next 2-3 days. Are there any limitations to the fixed schedule which might be causing this unintended behavior of going off at midnight?
Replies
7
Boosts
2
Views
942
Activity
2d
AlarmKit leaves an empty zombie Live Activity in Dynamic Island after swipe-dismiss while unlocked
Hi, We are the developers of Morning Call (https://morningcall.info), and we believe we may have identified an AlarmKit / system UI bug on iPhone. We can reproduce the same behavior not only in our app, but also in Apple’s official AlarmKit sample app, which strongly suggests this is a framework or system-level issue rather than an app-specific bug. Demonstration Video of producing zombie Live Activity https://www.youtube.com/watch?v=cZdF3oc8dVI Related Thread https://developer.apple.com/forums/thread/812006 https://developer.apple.com/forums/thread/817305 https://developer.apple.com/forums/thread/807335 Environment iPhone with Dynamic Island Alarm created using AlarmKit Device is unlocked when the alarm begins alerting Steps to reproduce Schedule an AlarmKit alarm. Wait for the alarm to alert while the device is unlocked. The alarm appears in Dynamic Island. Instead of tapping the intended stop or dismiss button, swipe the Dynamic Island presentation away. Expected result The alarm should be fully dismissed. The Live Activity should be removed. No empty UI should remain in Dynamic Island. Actual result The assigned AppIntent runs successfully. Our app code executes as expected. AlarmKit appears to stop the alarm correctly. However, an empty “zombie” Live Activity remains in Dynamic Island indefinitely. The user cannot clear it through normal interaction. Why this is a serious user-facing issue This is not just a cosmetic issue for us. From the user’s perspective, it looks like a Live Activity is permanently stuck in Dynamic Island. More importantly: Force-quitting the app does not remove it Deleting the app does not remove it In practice, many users conclude that our app has left a broken Live Activity running forever We receive repeated user complaints saying that the Live Activity “won’t go away” Because the remaining UI appears to be system-owned, users often do not realize that the only reliable recovery is to restart the phone. Most users do not discover that workaround on their own, so they instead assume the app is severely broken. Cases where the zombie state disappears Rebooting the phone Waiting for the next AlarmKit alert, then pressing the proper stop button on that alert Additional observations Inside our LiveActivityIntent, calling AlarmManager.shared.stop(id:) reports that the alarm has already been stopped by the system. We also tried inspecting Activity<AlarmAttributes<...>>.activities and calling end(..., dismissalPolicy: .immediate), but in this state no matching activity is exposed to the app. This suggests that the alarm itself has already been stopped, but the system-owned Live Activity UI is not being cleaned up correctly after the swipe-dismiss path. Why this does not appear to be an app logic issue The intent is invoked successfully. The alarm stop path is reached. The alarm is already considered stopped by the system. The remaining UI appears to be system-owned. The stuck UI persists even after our own cleanup logic has run. The stuck UI also survives app force-quit and app deletion.
Replies
12
Boosts
13
Views
3.2k
Activity
2d
Can’t submit IMDF! Approved for Indoor Maps Program, no upload path in ABR.
Has anyone recently found a working path to claim a venue and upload an IMDF in Apple Business Register? Our Locations page shows 0 locations with no option to add one. (Screenshot attached.) Our business is approved for the Indoor Maps Program, our location is approved/verified in Apple Business Register, and our IMDF file is complete and ready to submit. We just can’t find anywhere to submit it. The 2019 WWDC session “Introducing the Indoor Maps Program” shows a “Claim your location” flow and a per-venue upload dashboard that simply doesn’t exist in our account today. We emailed maps-indoor-support@apple.com on August 25 with no response. A few other threads here describe the same thing, IMDF or venue registration stuck with no visible next step, so this doesn’t look isolated to our account. Any pointers on where this actually happens now would help. This has been open almost three months with a completed file and nowhere to send it. I am trying to develop my app but cannot proceed without this piece.
Replies
0
Boosts
0
Views
45
Activity
2d
PermissionKit significant-change consent: is a parent's answer delivered if the app is closed?
Our app is not yet released. We have built, but not switched on, the parental consent step for a significant change: when requiredRegulatoryFeatures contains .significantAppChangeRequiresParentalConsent, the app creates PermissionQuestion(significantAppUpdateTopic: SignificantAppUpdateTopic(description:)), calls AskCenter.shared.ask(_:in:), and holds the changed app until an approval arrives. It listens with for await response in AskCenter.shared.responses(for: SignificantAppUpdateTopic.self) from launch, on every launch while an approval is owed. The ask and listen part runs on iOS 26.2 and later; the set is read on iOS 26.4 and later. We have seen iOS 27's askSignificantChangePermission(for:permissionFlow:in:) with .approveInPerson, which returns the answer to the caller; the questions below are about the Ask to Approve path through ask(_:in:). A parent may answer hours later, after the child has closed the app. "Creating a communication experience" says to obtain the sequence promptly after launch, and points to a background route for communication limits, but says nothing about SignificantAppUpdateTopic. The sample "Implementing age assurance and permissions" listens at its entry point but does not say what happens to an answer given while the app is closed. If the parent answers while the app is closed, is that response delivered on the next launch's responses(for: SignificantAppUpdateTopic.self)? Is a response delivered once, or again on every later launch? Does that differ for an approval and a decline? On the Ask to Approve path, is there a supported way for the app to be woken, or to fetch the current answer, so that it does not depend on a response arriving while it is running? Without an expirationDate, how long does a question stay open for the parent? What does ask do when a question on the same topic is already pending? After a decline, can the child send a new question? "Testing Age Assurance in Sandbox" says that for a selected scenario PermissionKit returns the associated response status. Does that response arrive through responses(for:) after ask, and can the closed-app case in question 1 be exercised in sandbox? We have not yet run this on a device. Environment: iPhone 17e, iOS 27.2.1. Xcode 26.6 (17F113) with the iOS 26.5 SDK.
Replies
0
Boosts
0
Views
40
Activity
2d
Declared Age Range: does a sandbox tester's Age Assurance setting reach other installs after sign-out?
The problem. We are trying to confirm, before release, what our app's age check will read on an App Store install. On a development-signed install, a sandbox tester's Age Assurance setting was still returned after the tester signed out. We want to know whether a TestFlight or App Store install would read the same state. The app is not yet released; everything here is pre-release testing. Questions On a development-signed install with no sandbox tester signed in, does the API answer from the device's real Apple Account as production would, or from sandbox state? Is a sandbox tester's Age Assurance setting expected to stay in effect after the tester signs out? If so, what clears it? Can that state reach a TestFlight install or an App Store install on the same device? Do TestFlight installs read production or sandbox for this API? How should a developer verify before release what an App Store install will read? Other developers have asked near questions 3 and 4 (threads 851245 and 854172) without an Apple answer. What we read (iPhone 17e, iOS 27.2.1; a small native sample app, development-signed, that reads requiredRegulatoryFeatures and calls requestAgeRange(ageGates: 16, in:)) With the device's own adult account and no sandbox tester signed in: [declaredAgeRangeRequired], sharing with a lower bound of 18, declaration confirmed, no sheet. We signed in a new sandbox tester and set Age Assurance to '13 - 15, significant change approved': the set gained .significantAppChangeRequiresParentalConsent, and the request returned 13 to 15 with .significantAppChangeApprovalRequired in activeParentalControls. After the tester signed out, with no sandbox tester signed in, reads still returned the tester's 13 to 15 on every read for the next 21 minutes, one of them after a restart, and again the next morning, about 16 hours later. No sheet was seen on any of these reads. The next morning we signed the same tester back in (its Age Assurance still showed '13 - 15'; the set read empty) and made one request by hand, which presented a sheet; we chose Share and it returned 16 or older, self-declared. We then set the tester to '18+, age confirmed, significant change not applicable' and signed it out. From then on, with no tester signed in, reads returned a lower bound of 18 again. On TestFlight. A TestFlight build of our app has no console, so we could not read what the API returned there. Once (iOS 26.6.2), three sandbox testers had used the phone earlier in the day, the last set to '13 - 15', and all were signed out. With the phone then signed out of every Apple Account, a TestFlight build opened in about a second. Just after, a development build of the same source read both .declaredAgeRangeRequired and .significantAppChangeRequiresParentalConsent and ended on the screen our app shows when the request returns anything other than a shared range of 16 or older. Environment: iPhone 17e, iOS 27.2.1 and iOS 26.6.2. Xcode 26.6 (17F113) with the iOS 26.5 SDK. Related Feedback: FB25530441, FB25530501, FB25530513.
Replies
0
Boosts
0
Views
41
Activity
2d
Declared Age Range: when can the requirement be absent or removed, and what if the read throws?
The problem. Our iOS app decides at launch whether to ask for a person's age range, from whether requiredRegulatoryFeatures contains .declaredAgeRangeRequired. The app is not yet released; everything here is pre-release testing. We want to confirm the cases where that member can be absent or can change, and what to do when the read fails. Questions Thread 815952 (Apple, March 2026) says the set could be empty while isEligibleForAgeFeatures is true. Can that case occur on iOS 27? The article "Requesting people's age range information in your app" says that in some regulated regions people "can't decline sharing". Is Texas one of those regions? Where .declaredAgeRangeRequired is present, can a decline remove it afterwards? Another developer reports Texas users who read the requirement and could still decline (thread 836191, no answer yet). What we saw in sandbox is below. Apple's news post of June 3, 2026 says the Texas requirements apply to new Apple Accounts in Texas from June 4, 2026. Does an account created before that date ever read .declaredAgeRangeRequired (iOS 26.4 or later), for example after moving to Texas or after an OS update? (A related question, about the sheet, is in thread 853955, no answer yet.) The requiredRegulatoryFeatures page says it throws notAvailable when the service is unavailable, and the article's example has a bare catch. When it throws, should the app treat the person as required, not required, or retry? (Another developer reports notAvailable after a device was switched from a parent's account to a child's, thread 854397, no answer yet. That report is theirs, not ours.) What we saw on a decline (question 2). In sandbox (iOS 26.6.2), with a tester on '13 - 15' signed in, a request we made by hand presented the sheet; we declined and it returned declinedSharing. A read after that, tester still on '13 - 15', did not contain .declaredAgeRangeRequired; it was present again once the tester was switched to an 18+ scenario. We had not read the set just before the decline. The device's own account later listed a decline for our app dated that day, so we cannot say which account the sheet belonged to. What we read (question 1). On iOS 26.6.2 we printed the whole set together with isEligibleForAgeFeatures on 15 reads of sandbox testers created in App Store Connect with region United States. isEligibleForAgeFeatures was true on every read where the set was not empty (7) and false on every read where it was empty (8). On iOS 27.2.1, with a small native sample app that reads the set and isEligibleForAgeFeatures and calls requestAgeRange(ageGates: 16, in:), every launch where we printed both had a non-empty set and true (7 launches). On two further launches the set was empty (a tester signed in, its Age Assurance showing '13 - 15') and we did not print isEligibleForAgeFeatures, so we cannot say whether those were the case in question 1. Environment: iPhone 17e, iOS 26.6.2 and iOS 27.2.1. Xcode 26.6 (17F113) with the iOS 26.5 SDK. Reads made from development builds. Related Feedback: FB25530441, FB25530501, FB25530513.
Replies
0
Boosts
0
Views
41
Activity
2d
Improve PTT System UI Visibility When Location Indicators Are Active
Observed Limitation When location services are active, the iOS location indicator may overlap with or hide the PTT blue button or system UI in the notch / Dynamic Island area. Requested Changes Ensure PTT controls remain visible and accessible when location indicators are displayed. Improve system UI positioning to prevent conflicts with other system indicators.
Replies
1
Boosts
0
Views
35
Activity
2d