Posts under App & System Services topic

Post

Replies

Boosts

Views

Activity

Individual to Organization migration pending 8 weeks, membership disabled, no response from support
Hello, I'm hoping someone from Apple Developer Support or Developer Relations can look at our case, as normal support channels have gone silent. Timeline: Sep 18, 2026: Requested migration from Individual to Organization membership (case 102967867566) Sep 22: Sent Certificate of Incorporation and signed letter of authorization as requested Sep 24: Support confirmed the migration had started; we submitted the company enrollment the same day (Enrollment ID Q4PVGUSD8R). The confirmation said Apple would verify our authority to bind the organization and email next steps Since then: no verification call, email, or document request, despite several follow-ups on the original thread and a new case (30000005804312) Current state: Account page shows "We're processing your membership migration" and membership benefits are disabled App Store Connect asks the Account Holder to accept the updated Program License Agreement, but the account does not offer it for acceptance We cannot upload builds or submit apps; releases have been blocked since early October Phone support shows "currently unavailable" for us in India, even during listed hours Team ID: 572T5NQ4J5 Organization: ALLEDA LIFESTYLE PRIVATE LIMITED (D-U-N-S 771424689) We're a digital health company, and we're migrating because Apple requires health apps to be published by a legal entity. We can provide any document the same day. Has anyone faced a similar delay with migration verification from India, and is there anything else we can do? If an Apple staff member can check the status or escalate the case, we'd be very grateful. Thank you.
1
0
101
6d
BLE scan results are reduced on iPhone 17 pro max
I'm seeing for a particular user of iPhone 17 pro max I'm seeing highly reduced BLE scan results in 'didDiscover' for CBCentralManager. I was loging it and saw values like 54 sec between 2 BLE scans. This not to do with background because I have handled scanning with service UUIDs and I've not seen any issue before with that. This I've see currently only for one user. For this user once iBeacon region is entered using ranging and monitoring 0 CLBeacon beacons are received for this user. For same peripheral devices on other phones, the BLE beacons and iBeacon scans look proper and at a constant rate. Model: iPhone18,2 (iPhone 17 Pro Max) OS: 26.6.2
0
0
66
6d
Enrollment through the Apple Developer app is not available "after withdrawing web enrollment"
Hi everyone, I’m running into an issue with my Apple Developer Program enrollment and wanted to see if anyone has experienced this or knows a quick workaround. Here is what happened: I started the enrollment process inside the Apple Developer iOS app (to pay via In-App Purchase in my local currency). I exited the flow right before completing the payment. Afterward, the iOS app greyed out the "Enroll Now" button and displayed: "Enrollment through the Apple Developer app is not available for this Apple Account. Visit https://developer.apple.com/programs/enroll/." I went to the web portal, saw the pending enrollment session there, and clicked "Withdraw enrollment" to clear it. Even after withdrawing the web enrollment, signing out, reinstalling the Apple Developer app, and waiting over 24 hours, the iOS app still shows the same restriction message and won't let me enroll via the app. Has anyone managed to get the iOS app enrollment unlocked again after withdrawing a web session? Do I just need to wait for Apple Developer Support to manually reset the backend flag on my account? Thanks in advance for any help!
0
0
60
6d
Trials entering billing retry instead of converting
We have a monthly subscription and an annual subscription with a 3-day free trial. The monthly converts fine. On the annual, trials tend to enter billing retry rather than convert — users don't cancel, the charge just fails. We've audited our implementation and found nothing on our side that participates in the renewal charge. What can a developer actually do about this? Does trial length, price point, or using a paid introductory offer instead of a free trial make a difference?
1
0
155
6d
APFS directory-entry durability after creating an Application Support subdirectory
On macOS 15.7.2 with a local APFS volume and App Sandbox, which supported filesystem operations and synchronization order make a newly created directory entry and a new database filename durable after an OS crash or sudden power loss? DTS asked me to post this question here for review. This is a design-stage API-contract question, not a report of a reproduced failure. The proposed sequence has not been implemented or tested. I have no focused reproducer, crash report, or power-loss test results for this question. The platform in question is macOS, not iOS. Context The proposed initialization sequence is: Obtain the Application Support directory using Foundation. Call this directory P. Create a new app-specific directory R directly under P, without replacing an existing object. Create a SQLite catalog at R/start.sqlite and commit its initial record. The proposed SQLite configuration is SQLite 3.47.2, the standard Unix VFS, journal_mode=DELETE, and synchronous=EXTRA. These are design assumptions, not verified runtime settings. The filesystem synchronization operations and their ordering relative to directory creation, database-file creation, and the initial transaction are what I need to establish. The specific concern is the durability of the directory entries needed to resolve P/R/start.sqlite. I need to distinguish the persistence of the database contents from the persistence of the names used to reach that database. I am not assuming that a successful SQLite commit, by itself, establishes every parent-directory durability requirement. Questions Is fsync supported on APFS directory file descriptors on macOS 15.7.2? If so, what does successful return guarantee about directory entries created before the call? Does fcntl(fd, F_FULLFSYNC) apply to directory descriptors? If not, what supported operation, if any, should an application use to establish the required directory-entry durability? Which objects need to be synchronized, and in what order: the database file, R, P, or P's parent? Please distinguish the case where P already existed from the case where P was newly created during initialization. What guarantees differ between an OS crash and sudden power loss? What assumptions about the local storage device, write caches, or flush support are required? Is there authoritative documentation applicable to macOS 15.7.2 that describes this contract? If part of the requested guarantee is unspecified or unsupported, please identify that boundary. If the answer differs on later macOS versions, please distinguish that from the 15.7.2 contract. I am asking about supported public filesystem APIs and their documented guarantees, not validation of an application-specific recovery protocol or guarantees against arbitrary hardware failure. Thank you.
5
0
150
6d
Build behaving differently in testflight compared to simulator
Hi all I have an app I’m pretty much done with, and on the Xcode simulator it works perfectly and the IAP shows us when the purchase buttons are clicked but for some reason when it goes to testflight none of the buttons respond, is there any reason that would cause it to behave differently in testflight when its coded correctly and works in the simulator. thanks
1
0
599
6d
Is receiving the same transaction multiple times from Transaction.updates expected behavior?
I'm seeing behavior similar to what was reported in this thread: https://developer.apple.com/forums/thread/816344 I read the discussion in the related thread (816320) as well, but I couldn't determine whether receiving the same transaction multiple times from Transaction.updates is considered expected behavior. In my case, I'm testing an auto-renewable subscription in the Sandbox environment. After successfully processing and calling finish() on a transaction, Transaction.updates sometimes provides another transaction with the same transactionId. I've also observed the same transactionId being delivered multiple times through Transaction.updates itself. I compared the JWS representations of these transactions. They are not byte-for-byte identical, but the transaction information appears to be the same. The only differences I've identified are: signedDate deviceVerificationNonce deviceVerification This looks as though the same transaction is being signed again at a different time. I'd like to clarify the intended way to handle this: Is it expected behavior for Transaction.updates to deliver the same transactionId multiple times in this way? If so, after an app has successfully processed and finished a transaction, is it safe to recognize subsequent transactions with the same transactionId as already processed, skip entitlement-related processing, and simply call finish() on them? In other words, can an app use transactionId to prevent duplicate processing of transactions that it has already successfully handled? I'm specifically interested in whether doing so could cause the app to miss any meaningful update that StoreKit might later deliver using the same transactionId.
3
0
831
6d
Can an iOS app share Screen Time goal progress with friends?
I'm developing an app that helps users reduce social media usage through friendly competitions. With explicit permission, the app would track daily and weekly usage of selected apps like Instagram, TikTok, and YouTube. Users could voluntarily share their live total usage, percentage improvement, or goal-completion status with approved friends. Does Apple's Family Controls policy permit this? If not, is there an approved way to implement a friends leaderboard using Screen Time data? Thank you!
0
0
48
6d
App Review sandbox: revenuecat product loads, then STORE_PROBLEM followed by PRODUCT_NOT_AVAILABLE_FOR_PURCHASE on iPadOS 26.6
Hello, I am investigating an intermittent In-App Purchase failure that occurred during App Review for the first release of my app. Environment Review device: iPad Air 11-inch (M3) OS: iPadOS 26.6 Environment: App Review sandbox Product type: Consumable StoreKit integration: RevenueCat through react-native-purchases 10.4.3 Observed behavior StoreKit successfully returned the products, localized names, and prices. The reviewer could see the credit packs and initiate the native purchase flow. My diagnostics show this sequence: Purchase initiated PURCHASE_CANCELLED; no transaction evidence Purchase initiated again RevenueCat code 2: STORE_PROBLEM elapsed: 9.4 seconds no transaction evidence Purchase initiated again RevenueCat code 5: PRODUCT_NOT_AVAILABLE_FOR_PURCHASE no transaction evidence Purchase initiated again RevenueCat code 5: PRODUCT_NOT_AVAILABLE_FOR_PURCHASE elapsed: 0.6 seconds no transaction evidence code-block The relevant sanitized logs are: { "occurredAt": "2026-08-25T12:52:59.733Z", "platform": "ios", "appVersion": "1.0.0", "build": "14", "productId": "HIDDEN_FOR_DISPLAY", "stage": "STORE_CHECKOUT", "providerCode": "2", "providerReadableCode": "STORE_PROBLEM", "transactionEvidence": false, "elapsedMs": 9417 } code-block { "occurredAt": "2026-08-25T12:55:42.752Z", "platform": "ios", "appVersion": "1.0.0", "build": "14", "productId": "HIDDEN_FOR_DISPLAY", "stage": "STORE_CHECKOUT", "providerCode": "5", "providerReadableCode": "PRODUCT_NOT_AVAILABLE_FOR_PURCHASE", "transactionEvidence": false, "elapsedMs": 637 } code-block No App Store transaction was created, and therefore RevenueCat received no transaction or webhook for these attempts. Configuration verified I confirmed that: The affected product and the other consumable products are attached to the App Review submission. Product IDs match between the app, App Store Connect, and RevenueCat. Prices and localizations are configured. The products are available in the relevant storefronts. The Paid Apps Agreement is active. Banking and tax information are active. The In-App Purchase capability is present. The distribution build does not use a local StoreKit configuration file. The same build and affected product completed successfully afterward on a physical device using Apple Sandbox. The native purchase sheet opened, the transaction completed, and the consumable content was delivered successfully in my reproduction. The product metadata clearly remained available because its localized name and price were displayed. However, after the initial STORE_PROBLEM, subsequent purchase requests were rejected almost immediately as PRODUCT_NOT_AVAILABLE_FOR_PURCHASE. I do not have the underlying Apple NSError, such as an ASDServerErrorDomain or AMSErrorDomain value, because it was not exposed in my remote diagnostic record. Questions Can a failed sandbox transaction leave the StoreKit account/session or commerce-catalog state temporarily inconsistent, causing subsequent requests for an otherwise loaded product to return storeProductNotAvailable? Does StoreKit use separate metadata and transaction-eligibility services, allowing product information to load while the same product is rejected during purchase()? Are there known sandbox or StoreKit issues on iPadOS 26.6 that could produce this sequence? Could a stale App Review sandbox account token or storefront session explain the transition from STORE_PROBLEM to PRODUCT_NOT_AVAILABLE_FOR_PURCHASE? Is there any developer-side configuration that could explain this when the same product and binary complete successfully using another sandbox session? What additional logging should I capture from RevenueCat’s React Native SDK to preserve the complete underlying Apple error chain?
3
0
1k
6d
Entitlement request guidance: com.apple.vm.device-access for a Developer ID VDI client (libusb USB capture)
Hello, This is a code-signing / entitlement-process question. The USB API details are included only to explain why the entitlement is required. We maintain a macOS VDI client distributed with Developer ID (outside the Mac App Store, notarized). USB redirection uses SPICE usbredir over libusb 1.0.30. To redirect USB mass-storage devices and printers, the macOS kernel drivers must be detached before the device can be claimed. libusb does this in darwin_detach_kernel_driver_locked(): it calls IOServiceAuthorize() and then USBDeviceReEnumerate() with kUSBReEnumerateCaptureDeviceBit. The public IOUSBLib.h header documents that this requires either: 1. the com.apple.vm.device-access entitlement plus a successful IOServiceAuthorize(), or 2. root privileges.Running the whole VDI client as root is not acceptable, so we need the entitlement on a Developer ID build. Without it, libusb returns LIBUSB_ERROR_ACCESS when detaching the kernel driver for these devices, which is the only blocker for the feature. In Certificates, Identifiers & Profiles -> Identifiers -> App ID -> Capabilities, the only USB-related entries we see are "Claim USB Accessory" (com.apple.developer.accessory-access.usb) and "DriverKit USB Transport (development)". com.apple.vm.device-access is not listed, and we could not find a request form for it. Could DTS or the entitlements team clarify: Is com.apple.vm.device-access still granted to Developer ID apps? What is the correct request channel (capability request, entitlement request form, TSI, or a Developer ID provisioning profile)? On macOS 27+, is Accessory Access + Claim USB Accessory the supported replacement for IOUSBFamily device capture? Does it expose raw USB transfers suitable for forwarding a device to a remote guest OS over a protocol such as usbredir, or is it limited to local Virtualization.framework VMs? If com.apple.vm.device-access is not available for this use case, is a DriverKit USB transport extension the recommended architecture for a libusb-based redirection client? Any guidance on the correct request process would be appreciated. We can provide the bundle ID, Team ID, target macOS versions, device classes, and user-consent/security design privately if needed. Thanks, liyucai
1
0
66
6d
MobileVLCKit (3.7.3) triggering Local Network permission
The problem manifests itself from 16 to 18 iOS not inclusive Versions from 18 up to and including do not cause this problem. When initializing the player, a request for permission to use the local network appears. The application does not use a local network as a capability, even in plist there is no such key. Apple has granted permission to use multicast networking, and the corresponding capability has also been added. The player is assembled as let player = VLCMediaPlayer() player.media = mediaHaving previously collected media with the options "clock-synchro=..." "avcodec-threads=..." "rtsp-tcp" "network-caching=..." "live-caching=..." "-vv" "clock-jitter=..."and "no-audio", "--no-sout-audio" to mute the audio for the picture during the call How to prevent a library from accessing the local network?
1
0
60
6d
SwiftData with CloudKit failing to migrate schema
My app has been in the App Store a few months. In that time I've added a few updates to my SwiftData schema using a MigrationPlan, and things were seemingly going ok. But then I decided to add CloudKit syncing. I needed to modify my models to be compatible. So, I added another migration stage for it, changed the properties as needed (making things optional or adding default values, etc.). In my tests, everything seemed to work smoothly updating from the previous version to the new version with CloudKit. So I released it to my users. But, that's when I started to see the crashes and error reports come in. I think I've narrowed it down to when users update from older versions of the app. I was finally able to reproduce this on my end, and Core Data is throwing an error when loading the ModelContainer saying "CloudKit integration requires that all attributes be optional, or have a default value set." Even though I did this in the latest schema. It’s like it’s trying to load CloudKit before performing the schema migration, and since it can’t, it just fails and won’t load anything. I’m kinda at a loss how to recover from this for these users other than tell them to delete their app and restart, but obviously they’ll lose their data that way. The only other idea I have is to setup some older builds on TestFlight and direct them to update to those first, then update to the newest production version and hope that solves it. Any other ideas? And what can I do to prevent this for future users who maybe reinstall the app from an older version too? There's nothing special about my code for loading the ModelContainer. Just a basic: let container = try ModelContainer( for: Foo.self, Bar.self, migrationPlan: SchemaMigration.self, configurations: ModelConfiguration(cloudKitDatabase: .automatic) )
8
3
3.6k
6d
iPhone 16e on iOS 27.2.1 intermittently misses BLE extended advertisements until Reset Location & Privacy
I’m investigating intermittent discovery of QuadSense V40.0 sensors on an iPhone 16e running iOS 27.2.1 (24B156). Legacy advertising units remain discoverable, but the phone sometimes misses the V40 units entirely. I’ve also seen intermittent discovery in BLESerial. The V40 uses connectable BLE 5.0 extended advertising, with a 1M primary PHY, 2M secondary PHY, and an advertising interval of about 1 second. The advertisement includes the QuadSense local name and manufacturer data with ID 0xFF02 and a 25-byte payload. During the failure: A native CBCentralManager scan with no service filter and duplicate reports enabled received 4,821 discovery callbacks in 90 seconds, including a legacy QuadSense, but zero matching extended reports. A nearby Mac received 25 matching advertisements during its overlapping scan. The iPhone probe bypassed our Flutter scan and filtering code. After Reset Location & Privacy: The same iPhone reported two V40.0 units within 1.6 seconds. Both were reported as connectable. Core Bluetooth delivered 11 matching advertisements in 10 seconds, and our app accepted both units. Bluetooth authorization was .allowedAlways in both runs. I saw the related extended advertising thread, where Apple clarified that r.188123531 affects iPhone 17 and newer. I’m posting separately because this reproduction is on a 16e and 16. Has anyone seen this on the 16e, or found a way to isolate what changes after Reset Location & Privacy when Bluetooth authorization was already granted? I’m setting up controller traces to compare a working scan with the next failure before resetting again. I’d appreciate guidance on which trace events and sysdiagnose details would be most useful to Apple.
2
0
145
1w
Sandbox startSession returns HTML 500 after ~10s for all registered merchants (platform integrator)
We're an Apple Pay platform integrator (Web Merchant Registration API). Since some point between 27 Oct and 12 Nov 2026, merchant validation against the sandbox gateway fails for every merchant we have registered. Request: POST https://apple-pay-gateway-cert.apple.com/paymentservices/startSession mTLS with our Platform Integrator Identity certificate, body: {"merchantIdentifier":"<registered id>","displayName":"Test","initiative":"web","initiativeContext":"<registered domain>"} Response: after ~8–10s, an HTML page "500 Internal Server Error" (footer "Apple"), not the usual JSON error. With curl --max-time 60 it still returns the 500 at ~10.7s, so the timeout is on Apple's side. What we've checked: Fails under two separate platform integrator identities, from our servers and from a developer laptop with plain curl (no proxy). curl timing: TLS handshake complete in 0.23s, TTFB ~9s. Network/IPv6/OCSP/SSL inspection don't apply. The same request with an unregistered merchantIdentifier returns the expected JSON 417 (mass_enablement_authorization_denied) in <0.5s. registerMerchant, unregisterMerchant and GET /paymentservices/merchant/{id} all work normally; merchant details show the expected domains and encryptTo hash. A newly registered merchant with a single valid domain also gets the 500. Domain verification file is served correctly and its pspId matches. Identity and payment processing certificates are valid and OCSP reports "good". Production gateway responds normally (fast JSON 4xx for unregistered merchants). The same setup returned valid sessions in under a second until at least 27 Oct 2026. Is anyone else seeing sandbox startSession failures, or can Apple check whether something has changed on the sandbox gateway?
0
0
73
1w
Apple Watch Notification Center timestamp drift on notifications processed by a Notification Service Extension
I'm seeing a timestamp display issue on Apple Watch Notification Center, and I'd like to confirm whether this is a known watchOS behavior or whether there's a setup mistake on our side. Symptom The same APNs notification displays the correct time on iPhone Notification Center and on the initial Apple Watch banner. After the Watch screen turns off and the user later opens Notification Center on Apple Watch, the same notification may show an incorrect relative timestamp such as "3 hours ago" or even "yesterday". The drift is per-notification and persists for that notification until it's dismissed. iPhone NC always shows the correct time. WhatsApp tested side-by-side on the same iPhone/Watch pair does not show this drift. Setup iOS 26.4.2 on iPhone 16 Pro watchOS 26.4 on Apple Watch Series 10 App with paired Apple Watch A UNNotificationServiceExtension that decrypts E2EE message previews and applies Communication Notification enrichment via INSendMessageIntent and content.updating(from:) Production APNs environment, TestFlight builds No beta software Isolation tests already performed Test mutable-content NSE invoked Drift on Watch NC Minimal APNs (alert + sound only) no no no drift NSE skips content.updating(from:), INInteraction.donate/delete (still calls them as no-op via diagnostic build) yes yes — modifies content drift NSE bypasses ALL Intents/Communication Notification APIs (no INPerson, no INSendMessageIntent, no avatar, no updating(from:)); just modifies title/body/sound/category and returns the mutable copy yes yes — modifies content drift Production-like APNs payload (thread-id, target-content-id, category, sound, badge, custom userInfo) but WITHOUT mutable-content no no no drift Eliminated as causes: content.updating(from:), INSendMessageIntent, INInteraction.donate, INInteraction.delete(with:), INPerson/INPersonHandle (not even constructed in test 3), avatar fetching, thread-id, target-content-id, category, sound, badge, custom userInfo, custom createdAt timestamp, stale Siri/Apple Intelligence history (cleared manually on iPhone and Watch). The pattern The only consistent variable distinguishing the no-drift cases from the drift cases is whether mutable-content: 1 is set on the APNs payload (i.e. whether the UNNotificationServiceExtension is invoked). Once invoked, the extension's behavior with respect to Communication Notifications does not seem to affect the outcome — the drift reproduces even when the NSE only modifies title/body/sound and returns. Questions Is there a known watchOS behavior where notifications processed by a UNNotificationServiceExtension use a different timestamp source on Apple Watch Notification Center after the Watch screen has been turned off and reopened, while the initial Watch banner and iPhone Notification Center show the correct delivery time? Are there specific UNMutableNotificationContent properties or APNs payload flags that should be preserved (or avoided) when returning content from an NSE to keep the Watch NC timestamp consistent with the delivery time? For E2EE messaging apps, is there a recommended pattern to decrypt and return content from an NSE that avoids this drift on watchOS? Happy to provide an anonymized snippet of NotificationService.swift and the APNs payload format if useful. Thanks.
8
0
1.8k
1w
NSE - Notification Filtering Entitlement - No Progress in Months
It's been 2+ months now since I've submitted an entitlement request for the Notification Service Filtering Entitlement (NSE). I have a mobile app that I transferred from a previous developer account due to business reorganization and the previous account had this entitlement. However, after transferring the app, I am unable to push any updates to the app on iOS because the new developer account does not have the same entitlement. Everything outside of the developer account that the app is associated to remains the same - same workflow, same audience, same app use cases, etc.. However, we still have not had any progress on receiving the entitlement even after multiple escalations and follow-ups with the Apple Developer Support team. I am curious to know if any others within the Developer Community have requested this specific entitlement before and what your experience has been with it? Any advice on how I can expedite the approval for the entitlement? Otherwise our app continues to go stale on the iOS app store.
1
1
980
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
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
Individual to Organization migration pending 8 weeks, membership disabled, no response from support
Hello, I'm hoping someone from Apple Developer Support or Developer Relations can look at our case, as normal support channels have gone silent. Timeline: Sep 18, 2026: Requested migration from Individual to Organization membership (case 102967867566) Sep 22: Sent Certificate of Incorporation and signed letter of authorization as requested Sep 24: Support confirmed the migration had started; we submitted the company enrollment the same day (Enrollment ID Q4PVGUSD8R). The confirmation said Apple would verify our authority to bind the organization and email next steps Since then: no verification call, email, or document request, despite several follow-ups on the original thread and a new case (30000005804312) Current state: Account page shows "We're processing your membership migration" and membership benefits are disabled App Store Connect asks the Account Holder to accept the updated Program License Agreement, but the account does not offer it for acceptance We cannot upload builds or submit apps; releases have been blocked since early October Phone support shows "currently unavailable" for us in India, even during listed hours Team ID: 572T5NQ4J5 Organization: ALLEDA LIFESTYLE PRIVATE LIMITED (D-U-N-S 771424689) We're a digital health company, and we're migrating because Apple requires health apps to be published by a legal entity. We can provide any document the same day. Has anyone faced a similar delay with migration verification from India, and is there anything else we can do? If an Apple staff member can check the status or escalate the case, we'd be very grateful. Thank you.
Replies
1
Boosts
0
Views
101
Activity
6d
BLE scan results are reduced on iPhone 17 pro max
I'm seeing for a particular user of iPhone 17 pro max I'm seeing highly reduced BLE scan results in 'didDiscover' for CBCentralManager. I was loging it and saw values like 54 sec between 2 BLE scans. This not to do with background because I have handled scanning with service UUIDs and I've not seen any issue before with that. This I've see currently only for one user. For this user once iBeacon region is entered using ranging and monitoring 0 CLBeacon beacons are received for this user. For same peripheral devices on other phones, the BLE beacons and iBeacon scans look proper and at a constant rate. Model: iPhone18,2 (iPhone 17 Pro Max) OS: 26.6.2
Replies
0
Boosts
0
Views
66
Activity
6d
Enrollment through the Apple Developer app is not available "after withdrawing web enrollment"
Hi everyone, I’m running into an issue with my Apple Developer Program enrollment and wanted to see if anyone has experienced this or knows a quick workaround. Here is what happened: I started the enrollment process inside the Apple Developer iOS app (to pay via In-App Purchase in my local currency). I exited the flow right before completing the payment. Afterward, the iOS app greyed out the "Enroll Now" button and displayed: "Enrollment through the Apple Developer app is not available for this Apple Account. Visit https://developer.apple.com/programs/enroll/." I went to the web portal, saw the pending enrollment session there, and clicked "Withdraw enrollment" to clear it. Even after withdrawing the web enrollment, signing out, reinstalling the Apple Developer app, and waiting over 24 hours, the iOS app still shows the same restriction message and won't let me enroll via the app. Has anyone managed to get the iOS app enrollment unlocked again after withdrawing a web session? Do I just need to wait for Apple Developer Support to manually reset the backend flag on my account? Thanks in advance for any help!
Replies
0
Boosts
0
Views
60
Activity
6d
Trials entering billing retry instead of converting
We have a monthly subscription and an annual subscription with a 3-day free trial. The monthly converts fine. On the annual, trials tend to enter billing retry rather than convert — users don't cancel, the charge just fails. We've audited our implementation and found nothing on our side that participates in the renewal charge. What can a developer actually do about this? Does trial length, price point, or using a paid introductory offer instead of a free trial make a difference?
Replies
1
Boosts
0
Views
155
Activity
6d
APFS directory-entry durability after creating an Application Support subdirectory
On macOS 15.7.2 with a local APFS volume and App Sandbox, which supported filesystem operations and synchronization order make a newly created directory entry and a new database filename durable after an OS crash or sudden power loss? DTS asked me to post this question here for review. This is a design-stage API-contract question, not a report of a reproduced failure. The proposed sequence has not been implemented or tested. I have no focused reproducer, crash report, or power-loss test results for this question. The platform in question is macOS, not iOS. Context The proposed initialization sequence is: Obtain the Application Support directory using Foundation. Call this directory P. Create a new app-specific directory R directly under P, without replacing an existing object. Create a SQLite catalog at R/start.sqlite and commit its initial record. The proposed SQLite configuration is SQLite 3.47.2, the standard Unix VFS, journal_mode=DELETE, and synchronous=EXTRA. These are design assumptions, not verified runtime settings. The filesystem synchronization operations and their ordering relative to directory creation, database-file creation, and the initial transaction are what I need to establish. The specific concern is the durability of the directory entries needed to resolve P/R/start.sqlite. I need to distinguish the persistence of the database contents from the persistence of the names used to reach that database. I am not assuming that a successful SQLite commit, by itself, establishes every parent-directory durability requirement. Questions Is fsync supported on APFS directory file descriptors on macOS 15.7.2? If so, what does successful return guarantee about directory entries created before the call? Does fcntl(fd, F_FULLFSYNC) apply to directory descriptors? If not, what supported operation, if any, should an application use to establish the required directory-entry durability? Which objects need to be synchronized, and in what order: the database file, R, P, or P's parent? Please distinguish the case where P already existed from the case where P was newly created during initialization. What guarantees differ between an OS crash and sudden power loss? What assumptions about the local storage device, write caches, or flush support are required? Is there authoritative documentation applicable to macOS 15.7.2 that describes this contract? If part of the requested guarantee is unspecified or unsupported, please identify that boundary. If the answer differs on later macOS versions, please distinguish that from the 15.7.2 contract. I am asking about supported public filesystem APIs and their documented guarantees, not validation of an application-specific recovery protocol or guarantees against arbitrary hardware failure. Thank you.
Replies
5
Boosts
0
Views
150
Activity
6d
Build behaving differently in testflight compared to simulator
Hi all I have an app I’m pretty much done with, and on the Xcode simulator it works perfectly and the IAP shows us when the purchase buttons are clicked but for some reason when it goes to testflight none of the buttons respond, is there any reason that would cause it to behave differently in testflight when its coded correctly and works in the simulator. thanks
Replies
1
Boosts
0
Views
599
Activity
6d
Is receiving the same transaction multiple times from Transaction.updates expected behavior?
I'm seeing behavior similar to what was reported in this thread: https://developer.apple.com/forums/thread/816344 I read the discussion in the related thread (816320) as well, but I couldn't determine whether receiving the same transaction multiple times from Transaction.updates is considered expected behavior. In my case, I'm testing an auto-renewable subscription in the Sandbox environment. After successfully processing and calling finish() on a transaction, Transaction.updates sometimes provides another transaction with the same transactionId. I've also observed the same transactionId being delivered multiple times through Transaction.updates itself. I compared the JWS representations of these transactions. They are not byte-for-byte identical, but the transaction information appears to be the same. The only differences I've identified are: signedDate deviceVerificationNonce deviceVerification This looks as though the same transaction is being signed again at a different time. I'd like to clarify the intended way to handle this: Is it expected behavior for Transaction.updates to deliver the same transactionId multiple times in this way? If so, after an app has successfully processed and finished a transaction, is it safe to recognize subsequent transactions with the same transactionId as already processed, skip entitlement-related processing, and simply call finish() on them? In other words, can an app use transactionId to prevent duplicate processing of transactions that it has already successfully handled? I'm specifically interested in whether doing so could cause the app to miss any meaningful update that StoreKit might later deliver using the same transactionId.
Replies
3
Boosts
0
Views
831
Activity
6d
Can an iOS app share Screen Time goal progress with friends?
I'm developing an app that helps users reduce social media usage through friendly competitions. With explicit permission, the app would track daily and weekly usage of selected apps like Instagram, TikTok, and YouTube. Users could voluntarily share their live total usage, percentage improvement, or goal-completion status with approved friends. Does Apple's Family Controls policy permit this? If not, is there an approved way to implement a friends leaderboard using Screen Time data? Thank you!
Replies
0
Boosts
0
Views
48
Activity
6d
App Review sandbox: revenuecat product loads, then STORE_PROBLEM followed by PRODUCT_NOT_AVAILABLE_FOR_PURCHASE on iPadOS 26.6
Hello, I am investigating an intermittent In-App Purchase failure that occurred during App Review for the first release of my app. Environment Review device: iPad Air 11-inch (M3) OS: iPadOS 26.6 Environment: App Review sandbox Product type: Consumable StoreKit integration: RevenueCat through react-native-purchases 10.4.3 Observed behavior StoreKit successfully returned the products, localized names, and prices. The reviewer could see the credit packs and initiate the native purchase flow. My diagnostics show this sequence: Purchase initiated PURCHASE_CANCELLED; no transaction evidence Purchase initiated again RevenueCat code 2: STORE_PROBLEM elapsed: 9.4 seconds no transaction evidence Purchase initiated again RevenueCat code 5: PRODUCT_NOT_AVAILABLE_FOR_PURCHASE no transaction evidence Purchase initiated again RevenueCat code 5: PRODUCT_NOT_AVAILABLE_FOR_PURCHASE elapsed: 0.6 seconds no transaction evidence code-block The relevant sanitized logs are: { "occurredAt": "2026-08-25T12:52:59.733Z", "platform": "ios", "appVersion": "1.0.0", "build": "14", "productId": "HIDDEN_FOR_DISPLAY", "stage": "STORE_CHECKOUT", "providerCode": "2", "providerReadableCode": "STORE_PROBLEM", "transactionEvidence": false, "elapsedMs": 9417 } code-block { "occurredAt": "2026-08-25T12:55:42.752Z", "platform": "ios", "appVersion": "1.0.0", "build": "14", "productId": "HIDDEN_FOR_DISPLAY", "stage": "STORE_CHECKOUT", "providerCode": "5", "providerReadableCode": "PRODUCT_NOT_AVAILABLE_FOR_PURCHASE", "transactionEvidence": false, "elapsedMs": 637 } code-block No App Store transaction was created, and therefore RevenueCat received no transaction or webhook for these attempts. Configuration verified I confirmed that: The affected product and the other consumable products are attached to the App Review submission. Product IDs match between the app, App Store Connect, and RevenueCat. Prices and localizations are configured. The products are available in the relevant storefronts. The Paid Apps Agreement is active. Banking and tax information are active. The In-App Purchase capability is present. The distribution build does not use a local StoreKit configuration file. The same build and affected product completed successfully afterward on a physical device using Apple Sandbox. The native purchase sheet opened, the transaction completed, and the consumable content was delivered successfully in my reproduction. The product metadata clearly remained available because its localized name and price were displayed. However, after the initial STORE_PROBLEM, subsequent purchase requests were rejected almost immediately as PRODUCT_NOT_AVAILABLE_FOR_PURCHASE. I do not have the underlying Apple NSError, such as an ASDServerErrorDomain or AMSErrorDomain value, because it was not exposed in my remote diagnostic record. Questions Can a failed sandbox transaction leave the StoreKit account/session or commerce-catalog state temporarily inconsistent, causing subsequent requests for an otherwise loaded product to return storeProductNotAvailable? Does StoreKit use separate metadata and transaction-eligibility services, allowing product information to load while the same product is rejected during purchase()? Are there known sandbox or StoreKit issues on iPadOS 26.6 that could produce this sequence? Could a stale App Review sandbox account token or storefront session explain the transition from STORE_PROBLEM to PRODUCT_NOT_AVAILABLE_FOR_PURCHASE? Is there any developer-side configuration that could explain this when the same product and binary complete successfully using another sandbox session? What additional logging should I capture from RevenueCat’s React Native SDK to preserve the complete underlying Apple error chain?
Replies
3
Boosts
0
Views
1k
Activity
6d
Entitlement request guidance: com.apple.vm.device-access for a Developer ID VDI client (libusb USB capture)
Hello, This is a code-signing / entitlement-process question. The USB API details are included only to explain why the entitlement is required. We maintain a macOS VDI client distributed with Developer ID (outside the Mac App Store, notarized). USB redirection uses SPICE usbredir over libusb 1.0.30. To redirect USB mass-storage devices and printers, the macOS kernel drivers must be detached before the device can be claimed. libusb does this in darwin_detach_kernel_driver_locked(): it calls IOServiceAuthorize() and then USBDeviceReEnumerate() with kUSBReEnumerateCaptureDeviceBit. The public IOUSBLib.h header documents that this requires either: 1. the com.apple.vm.device-access entitlement plus a successful IOServiceAuthorize(), or 2. root privileges.Running the whole VDI client as root is not acceptable, so we need the entitlement on a Developer ID build. Without it, libusb returns LIBUSB_ERROR_ACCESS when detaching the kernel driver for these devices, which is the only blocker for the feature. In Certificates, Identifiers & Profiles -> Identifiers -> App ID -> Capabilities, the only USB-related entries we see are "Claim USB Accessory" (com.apple.developer.accessory-access.usb) and "DriverKit USB Transport (development)". com.apple.vm.device-access is not listed, and we could not find a request form for it. Could DTS or the entitlements team clarify: Is com.apple.vm.device-access still granted to Developer ID apps? What is the correct request channel (capability request, entitlement request form, TSI, or a Developer ID provisioning profile)? On macOS 27+, is Accessory Access + Claim USB Accessory the supported replacement for IOUSBFamily device capture? Does it expose raw USB transfers suitable for forwarding a device to a remote guest OS over a protocol such as usbredir, or is it limited to local Virtualization.framework VMs? If com.apple.vm.device-access is not available for this use case, is a DriverKit USB transport extension the recommended architecture for a libusb-based redirection client? Any guidance on the correct request process would be appreciated. We can provide the bundle ID, Team ID, target macOS versions, device classes, and user-consent/security design privately if needed. Thanks, liyucai
Replies
1
Boosts
0
Views
66
Activity
6d
MobileVLCKit (3.7.3) triggering Local Network permission
The problem manifests itself from 16 to 18 iOS not inclusive Versions from 18 up to and including do not cause this problem. When initializing the player, a request for permission to use the local network appears. The application does not use a local network as a capability, even in plist there is no such key. Apple has granted permission to use multicast networking, and the corresponding capability has also been added. The player is assembled as let player = VLCMediaPlayer() player.media = mediaHaving previously collected media with the options "clock-synchro=..." "avcodec-threads=..." "rtsp-tcp" "network-caching=..." "live-caching=..." "-vv" "clock-jitter=..."and "no-audio", "--no-sout-audio" to mute the audio for the picture during the call How to prevent a library from accessing the local network?
Replies
1
Boosts
0
Views
60
Activity
6d
SwiftData with CloudKit failing to migrate schema
My app has been in the App Store a few months. In that time I've added a few updates to my SwiftData schema using a MigrationPlan, and things were seemingly going ok. But then I decided to add CloudKit syncing. I needed to modify my models to be compatible. So, I added another migration stage for it, changed the properties as needed (making things optional or adding default values, etc.). In my tests, everything seemed to work smoothly updating from the previous version to the new version with CloudKit. So I released it to my users. But, that's when I started to see the crashes and error reports come in. I think I've narrowed it down to when users update from older versions of the app. I was finally able to reproduce this on my end, and Core Data is throwing an error when loading the ModelContainer saying "CloudKit integration requires that all attributes be optional, or have a default value set." Even though I did this in the latest schema. It’s like it’s trying to load CloudKit before performing the schema migration, and since it can’t, it just fails and won’t load anything. I’m kinda at a loss how to recover from this for these users other than tell them to delete their app and restart, but obviously they’ll lose their data that way. The only other idea I have is to setup some older builds on TestFlight and direct them to update to those first, then update to the newest production version and hope that solves it. Any other ideas? And what can I do to prevent this for future users who maybe reinstall the app from an older version too? There's nothing special about my code for loading the ModelContainer. Just a basic: let container = try ModelContainer( for: Foo.self, Bar.self, migrationPlan: SchemaMigration.self, configurations: ModelConfiguration(cloudKitDatabase: .automatic) )
Replies
8
Boosts
3
Views
3.6k
Activity
6d
iPhone 16e on iOS 27.2.1 intermittently misses BLE extended advertisements until Reset Location & Privacy
I’m investigating intermittent discovery of QuadSense V40.0 sensors on an iPhone 16e running iOS 27.2.1 (24B156). Legacy advertising units remain discoverable, but the phone sometimes misses the V40 units entirely. I’ve also seen intermittent discovery in BLESerial. The V40 uses connectable BLE 5.0 extended advertising, with a 1M primary PHY, 2M secondary PHY, and an advertising interval of about 1 second. The advertisement includes the QuadSense local name and manufacturer data with ID 0xFF02 and a 25-byte payload. During the failure: A native CBCentralManager scan with no service filter and duplicate reports enabled received 4,821 discovery callbacks in 90 seconds, including a legacy QuadSense, but zero matching extended reports. A nearby Mac received 25 matching advertisements during its overlapping scan. The iPhone probe bypassed our Flutter scan and filtering code. After Reset Location & Privacy: The same iPhone reported two V40.0 units within 1.6 seconds. Both were reported as connectable. Core Bluetooth delivered 11 matching advertisements in 10 seconds, and our app accepted both units. Bluetooth authorization was .allowedAlways in both runs. I saw the related extended advertising thread, where Apple clarified that r.188123531 affects iPhone 17 and newer. I’m posting separately because this reproduction is on a 16e and 16. Has anyone seen this on the 16e, or found a way to isolate what changes after Reset Location & Privacy when Bluetooth authorization was already granted? I’m setting up controller traces to compare a working scan with the next failure before resetting again. I’d appreciate guidance on which trace events and sysdiagnose details would be most useful to Apple.
Replies
2
Boosts
0
Views
145
Activity
1w
Sandbox startSession returns HTML 500 after ~10s for all registered merchants (platform integrator)
We're an Apple Pay platform integrator (Web Merchant Registration API). Since some point between 27 Oct and 12 Nov 2026, merchant validation against the sandbox gateway fails for every merchant we have registered. Request: POST https://apple-pay-gateway-cert.apple.com/paymentservices/startSession mTLS with our Platform Integrator Identity certificate, body: {"merchantIdentifier":"<registered id>","displayName":"Test","initiative":"web","initiativeContext":"<registered domain>"} Response: after ~8–10s, an HTML page "500 Internal Server Error" (footer "Apple"), not the usual JSON error. With curl --max-time 60 it still returns the 500 at ~10.7s, so the timeout is on Apple's side. What we've checked: Fails under two separate platform integrator identities, from our servers and from a developer laptop with plain curl (no proxy). curl timing: TLS handshake complete in 0.23s, TTFB ~9s. Network/IPv6/OCSP/SSL inspection don't apply. The same request with an unregistered merchantIdentifier returns the expected JSON 417 (mass_enablement_authorization_denied) in <0.5s. registerMerchant, unregisterMerchant and GET /paymentservices/merchant/{id} all work normally; merchant details show the expected domains and encryptTo hash. A newly registered merchant with a single valid domain also gets the 500. Domain verification file is served correctly and its pspId matches. Identity and payment processing certificates are valid and OCSP reports "good". Production gateway responds normally (fast JSON 4xx for unregistered merchants). The same setup returned valid sessions in under a second until at least 27 Oct 2026. Is anyone else seeing sandbox startSession failures, or can Apple check whether something has changed on the sandbox gateway?
Replies
0
Boosts
0
Views
73
Activity
1w
Apple Watch Notification Center timestamp drift on notifications processed by a Notification Service Extension
I'm seeing a timestamp display issue on Apple Watch Notification Center, and I'd like to confirm whether this is a known watchOS behavior or whether there's a setup mistake on our side. Symptom The same APNs notification displays the correct time on iPhone Notification Center and on the initial Apple Watch banner. After the Watch screen turns off and the user later opens Notification Center on Apple Watch, the same notification may show an incorrect relative timestamp such as "3 hours ago" or even "yesterday". The drift is per-notification and persists for that notification until it's dismissed. iPhone NC always shows the correct time. WhatsApp tested side-by-side on the same iPhone/Watch pair does not show this drift. Setup iOS 26.4.2 on iPhone 16 Pro watchOS 26.4 on Apple Watch Series 10 App with paired Apple Watch A UNNotificationServiceExtension that decrypts E2EE message previews and applies Communication Notification enrichment via INSendMessageIntent and content.updating(from:) Production APNs environment, TestFlight builds No beta software Isolation tests already performed Test mutable-content NSE invoked Drift on Watch NC Minimal APNs (alert + sound only) no no no drift NSE skips content.updating(from:), INInteraction.donate/delete (still calls them as no-op via diagnostic build) yes yes — modifies content drift NSE bypasses ALL Intents/Communication Notification APIs (no INPerson, no INSendMessageIntent, no avatar, no updating(from:)); just modifies title/body/sound/category and returns the mutable copy yes yes — modifies content drift Production-like APNs payload (thread-id, target-content-id, category, sound, badge, custom userInfo) but WITHOUT mutable-content no no no drift Eliminated as causes: content.updating(from:), INSendMessageIntent, INInteraction.donate, INInteraction.delete(with:), INPerson/INPersonHandle (not even constructed in test 3), avatar fetching, thread-id, target-content-id, category, sound, badge, custom userInfo, custom createdAt timestamp, stale Siri/Apple Intelligence history (cleared manually on iPhone and Watch). The pattern The only consistent variable distinguishing the no-drift cases from the drift cases is whether mutable-content: 1 is set on the APNs payload (i.e. whether the UNNotificationServiceExtension is invoked). Once invoked, the extension's behavior with respect to Communication Notifications does not seem to affect the outcome — the drift reproduces even when the NSE only modifies title/body/sound and returns. Questions Is there a known watchOS behavior where notifications processed by a UNNotificationServiceExtension use a different timestamp source on Apple Watch Notification Center after the Watch screen has been turned off and reopened, while the initial Watch banner and iPhone Notification Center show the correct delivery time? Are there specific UNMutableNotificationContent properties or APNs payload flags that should be preserved (or avoided) when returning content from an NSE to keep the Watch NC timestamp consistent with the delivery time? For E2EE messaging apps, is there a recommended pattern to decrypt and return content from an NSE that avoids this drift on watchOS? Happy to provide an anonymized snippet of NotificationService.swift and the APNs payload format if useful. Thanks.
Replies
8
Boosts
0
Views
1.8k
Activity
1w
NSE - Notification Filtering Entitlement - No Progress in Months
It's been 2+ months now since I've submitted an entitlement request for the Notification Service Filtering Entitlement (NSE). I have a mobile app that I transferred from a previous developer account due to business reorganization and the previous account had this entitlement. However, after transferring the app, I am unable to push any updates to the app on iOS because the new developer account does not have the same entitlement. Everything outside of the developer account that the app is associated to remains the same - same workflow, same audience, same app use cases, etc.. However, we still have not had any progress on receiving the entitlement even after multiple escalations and follow-ups with the Apple Developer Support team. I am curious to know if any others within the Developer Community have requested this specific entitlement before and what your experience has been with it? Any advice on how I can expedite the approval for the entitlement? Otherwise our app continues to go stale on the iOS app store.
Replies
1
Boosts
1
Views
980
Activity
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