Posts under App & System Services topic

Post

Replies

Boosts

Views

Activity

SKTestSession.setSimulatedError does not work - Products load successfully despite error configuration
Description I'm attempting to test error handling in my StoreKit implementation using SKTestSession.setSimulatedError(), but it doesn't trigger any errors. All StoreKit APIs (.loadProducts, .purchase, .appTransaction) succeed despite error simulation being configured before API calls. According to Apple's documentation, setSimulatedError(_:forAPI:) should cause the specified API to throw an error, but this doesn't happen in my testing environment. Background / Known issue I found a previous forum discussion: "SKTestSession.setSimulatedError() not working for .loadProducts API in iOS 26.2" which mentioned this was a bug in iOS 26.2 and was supposedly fixed in iOS 26.3. However, I'm experiencing the same issue in my current environment (Xcode 26.6 / iOS 26.5), which suggests either: The bug has regressed, or There's a different underlying issue, or I'm missing something in my implementation I wanted to report this to confirm whether this is still a known issue or if additional steps are needed. Environment Xcode: 26.6 Test Environment: iOS Simulator - iPhone 17 Pro(26.5) Testing Framework: XCTest StoreKitTest Framework: Included in Xcode Code Unit test code import XCTest import StoreKit import StoreKitTest final class StoreKitErrorTests: XCTestCase { func test_LoadProducts_SetSimulatedError() async throws { // Arrange let session = try SKTestSession(configurationFileNamed: "storekit") session.clearTransactions() session.disableDialogs = true // Set simulated error for loadProducts API try await session.setSimulatedError( .generic(.unknown), forAPI: .loadProducts ) // Act - Attempt to load products do { let products = try await Product.products(for: ["com.example.app.testproduct"]) // This line executes - products were loaded successfully print("[TEST] FAIL: Loaded \(products.count) products") XCTFail("setSimulatedError did not work - products loaded successfully") } catch { // This should execute, but it doesn't print("[TEST] PASS: Error was thrown") } } }.storekit file Note: Showing only the product definition. File also contains settings and version info. { "products" : [ { "displayPrice" : "1.23", "familyShareable" : false, "internalID" : "5AE6F98A", "localizations" : [ { "description" : "Test app", "displayName" : "LsStorekit", "locale" : "en_US" } ], "productID" : "com.example.app.testproduct", "referenceName" : "LsStorekit", "type" : "NonConsumable" } ] }Expected Behavior The Product.products(for:) call should throw an error because setSimulatedError(.generic(.unknown), forAPI: .loadProducts) was called before the API invocation. The test should: Configure the simulated error Attempt to load products Catch an error in the catch block Test passes with: "[TEST] PASS: Error was thrown" Actual Behavior Products are loaded successfully despite the error simulation: • The do block completes without throwing • 1 product is returned from Product.products(for:) • XCTFail() is called, indicating the error simulation didn't work • Test fails with: "[TEST] FAIL: Loaded 1 products" Console Output [TEST] FAIL: Loaded 1 products Additional Testing I've tested setSimulatedError with multiple APIs, and all show the same behavior: APIError configurationResult.loadProducts.generic(.unknown)No error thrown.purchase.generic(.unknown)No error thrown.appTransaction.generic(.unknown)No error thrown.appStoreSync.generic(.unknown)No error thrownWhat I've Already Tried • Calling setSimulatedError before app launch (in UI tests) • Calling setSimulatedError after app launch but before API calls • Using different error types (.generic(.unknown), .generic(.networkError(...))) • Testing in both Unit Tests and UI Tests • Using different APIs (.loadProducts, .purchase, .appTransaction) • Clearing transactions and resetting session state • Verifying the .storekit file is correctly loaded (products load successfully) • Running the app first (⌘R) to ensure StoreKit configuration is registered with the StoreKit daemon - This was necessary to fix an initial issue where products weren't loading at all Questions Is this a known limitation of SKTestSession.setSimulatedError()? Are there additional steps required to make error simulation work? Is there an alternative approach to test StoreKit error handling? Does this work in specific Xcode/iOS SDK versions only? Any guidance would be greatly appreciated. I need to test error handling in my StoreKit implementation, but cannot find a way to simulate errors reliably.
0
0
40
5d
Local Network Privacy Child Process Behavior
I have a Java Swing application that is bundled into an app bundle using jpackage. The app basically launches a newer version of itself, when there is a new version downloaded in the users installation directory. I have noticed a regression or change in behavior with how LocalNetwork privacy works now. Previously, we would launch our Java application using the .app bundle. This is a launcher that checks for updates and will launch another JVM instance using any new jars it downloads when updating. So, it is closing the original process and spawning a new process using the downloaded jar. The new process is where the app connects to a server on the Local Network. This new process cannot access the Local Network even when the entry in privacy and security is enabled for the parent process. I have changed the behavior of my launcher application so that it keeps the process alive after launching the client application. When doing this, Local Network access works. So, my question is: is it required for the parent process to be running in order for a child process to have Local Network access? In previous macOS versions, this was not an issue, so something has changed with Local Network security across all the latest versions 26 and 27.
8
0
256
5d
Production AppTransaction.shared throws StoreKitError.unknown when reading original app acquisition date
I'm the developer of Freezon, and I ran into this on my own iPhone with the App Store version of the app. I use the verified AppTransaction.originalPurchaseDate to give Pro access to people who first downloaded the app before a published cutoff. This includes free downloads; I need the original acquisition date of the app itself, not an in-app purchase date. On this device, AppTransaction.shared repeatedly threw StoreKitError.unknown before returning a VerificationResult: let result = try await AppTransaction.shared switch result { case let .verified(transaction): let firstAcquisitionDate = transaction.originalPurchaseDate // Check early-adopter eligibility. case let .unverified(_, error): throw error }The error occurs at shared, before the switch. The App Store on this iPhone shows my Apple Account as signed in. However, when I purchase or restore, I keep getting asked for my password, and sometimes for both my Apple Account and password. I used to get the usual purchase confirmation more directly. I don't know whether these prompts are related to the shared failure. For context: App Store release 1.1.1 (2), bundle com.zyiszy.PrivateVault, App Store ID 6810494416. The app diagnostic recorded iOS 27.0.1. It did not capture the exact OS build or hardware model. In one capture, 13 native shared calls failed between 2026-11-16 01:11:43.824 and 01:13:16.124 UTC. All were matched as StoreKitError.unknown, with NSError domain StoreKit.StoreKitError, code 2, and no underlying error. This is not SKErrorDomain code 2 / payment cancellation. The first call failed while the network path was unsatisfied. The next 12 failed with a satisfied path, the app active and protected data available. Those calls returned in 0-1 ms. Bounded retries, with about 2- and 5-second delays, did not help in that capture. Product catalog requests succeeded during the same period. I realize that does not confirm connectivity to every App Store endpoint. The app does not automatically call refresh() or AppStore.sync() during this eligibility check. After force-quitting, reopening and using Restore, I eventually got access again. Unfortunately, I don't have a log of the successful recovery, so I can't tell which call succeeded. Could StoreKit still need fresh authentication even though the App Store shows the account as signed in? Can that cause shared to throw unknown without an underlying error, and is there a supported way to distinguish it from missing app transaction data? For this acquisition-date check, should the recovery button call AppTransaction.refresh() and use its verified result directly? Is AppStore.sync() needed at all? If more evidence is needed, which StoreKit logs or diagnostic profile should I collect before trying recovery next time? I also submitted DTS Case-ID: 23550827 with a small Xcode project and the redacted timeline. The project builds and isolates the API calls, but it has its own bundle identity and does not reproduce this production account state.
1
0
209
5d
CloudKit public database: unknownItem despite earlier Console visibility — interpreting fetch and authorization diagnostics
We are investigating one completed CloudKit Development test in a separate test container using only synthetic data. Shortly before an iOS client attempted to fetch a record from the public database’s default zone, that synthetic record was visible in CloudKit Console. The native client returned: CKErrorDomain code 11 (unknownItem) Underlying CKInternalErrorDomain code 2003 Sanitized diagnostic: record_not_found No record We verified that the client’s intended container, database, zone and record name matched the reference. A CloudKit Console event showed RecordFetch, operation-level SUCCESS, and approximately 171 ms execution time. However: The event was correlated by context and timestamp, not by a directly matched client operation or request ID. The available event did not expose a per-record result or an authorization decision. Earlier Console visibility does not establish availability or client access at the exact time of the fetch. The cause therefore remains unresolved. We have not established that a permissions restriction caused the error. We understand that Apple documents unknownItem for a nonexistent record and permissionFailure for insufficient permission to fetch or save data. We also understand that operation-level success and per-record fetch success are distinct. Our questions are: Can a public-database read restriction cause an existing record to be reported to a native client as unknownItem, rather than permissionFailure? If so, is this documented behavior? What does operation-level SUCCESS mean specifically for a RecordFetch event in CloudKit Console? Can that event still contain an unsuccessful individual record lookup? Which supported diagnostics can distinguish a missing or unavailable record from an authorization-based visibility restriction? Can Apple determine the authorization outcome of an existing request from retained diagnostics, and which correlation identifiers are required? What evidence is sufficient to verify server-enforced read restrictions in Development while preserving the existing roles and leaving production untouched? We are seeking clarification of the existing evidence, not proposing another reproduction attempt. No customer data, credentials or production records are involved.
3
0
138
5d
Can one Apple Developer team issue Wallet loyalty passes for multiple independent businesses?
In a web-based loyalty platform, each participating business defines its own rewards and authorizes the platform to display its name and logo on Apple Wallet passes. The platform would identify itself as the issuer and handle pass distribution and updates. Can the platform sign and update these passes using Pass Type IDs registered to a single Apple Developer team, or does each participating business need its own Apple Developer team and signing certificate? Is there official Apple documentation that covers this setup?
0
0
72
5d
WCSession.sendMessage is crashing when a reply or error handler is attached, why?
The following code should send a message from the watch to the iPhone. Unfortunately, it is crashing. I have no clue why. if WCSession.isSupported() { let session = WCSession.default if ((session.activationState == .activated) && session.isReachable) { session.sendMessage(["SimpleMessages":["start"]], replyHandler:{reply in _ = 0 }, errorHandler:nil) } } If the reply handler is set to nil, the code does not crash. Anyway, in both cases the message is correctly sent from the watch to the phone. The code itself is run on the main thread (verified). I am running watchOS 26.6 and iOS 27. Here is the crash : Stack trace
4
0
386
5d
StoreKit 2 returns USA/USD in TestFlight but DEU/EUR in local Release build on the same device
Hi everyone, We are currently preparing the release of our Flutter-based iOS application and are experiencing an unusual StoreKit 2 storefront issue that only occurs when the app is installed through TestFlight. The problem When our application is installed through TestFlight, StoreKit 2 consistently returns the United States storefront (USA), and all six auto-renewable subscription products are displayed with USD prices. However, both the regular Apple Account and the Sandbox Apple Account are configured for Germany. We have verified the following: All six subscription products are correctly configured in App Store Connect with EUR prices for Germany. The subscriptions are available in Germany, Austria, and Switzerland. We created a completely new Sandbox tester with Germany selected during account creation, using an email address that had never previously been used for sandbox testing. The issue occurs on two different physical devices (iPhone and iPad). No local StoreKit configuration file is used. Our application does not override the storefront, modify localized prices, or contain any hardcoded USD fallback. Controlled comparison We performed additional tests using the same application code on the same iPhone. The results were: Installation method Storefront Currency Local Debug build via Xcode/Flutter DEU EUR Local development-signed Release build via Flutter DEU EUR TestFlight Release build USA USD The locally installed Release build successfully retrieves all six subscription products with their correct German prices. For example, StoreKit returns the following values for one of our subscriptions: Local Release build: Storefront.current.countryCode = DEU Product currencyCode = EUR Product.displayPrice = 6,99 € TestFlight build: Storefront.current.countryCode = USA Product currencyCode = USD Both builds use the same StoreKit 2 integration and product identifiers. Technical environment Framework: Flutter StoreKit integration: StoreKit 2 Flutter plugin: in_app_purchase_storekit 0.4.11+2 Devices: Physical iPhone and iPad iOS/iPadOS: 26.6.2 Subscription products: Six auto-renewable subscriptions Expected storefront: Germany (DEU) Actual TestFlight storefront: United States (USA) We have traced the storefront country code directly to StoreKit 2’s Storefront.current.countryCode and the localized prices to the product information returned by Product.products(for:). There is no application-level storefront override or price conversion. Questions Why would StoreKit 2 return a different storefront in TestFlight compared with a locally installed development-signed Release build on the same physical device? Could TestFlight use a different sandbox storefront or Apple Account context than a locally installed build? Is there a recommended way to diagnose or reset the storefront association used by TestFlight? Has anyone experienced similar behavior where TestFlight consistently returns USA despite using a German Apple Account and newly created German sandbox testers? We have already contacted Apple Developer Support and followed their recommendation to create a completely new German sandbox tester, but the issue persists. Any guidance from Apple engineers or developers who have encountered similar behavior would be greatly appreciated. Thank you!
4
0
146
5d
StoreKit 2 returns USA/USD in TestFlight but DEU/EUR in local Release build on the same device
Hi everyone, We are currently preparing the release of our Flutter-based iOS application and are experiencing an unusual StoreKit 2 storefront issue that only occurs when the app is installed through TestFlight. The problem When our application is installed through TestFlight, StoreKit 2 consistently returns the United States storefront (USA), and all six auto-renewable subscription products are displayed with USD prices. However, both the regular Apple Account and the Sandbox Apple Account are configured for Germany. We have verified the following: All six subscription products are correctly configured in App Store Connect with EUR prices for Germany. The subscriptions are available in Germany, Austria, and Switzerland. We created a completely new Sandbox tester with Germany selected during account creation, using an email address that had never previously been used for sandbox testing. The issue occurs on two different physical devices (iPhone and iPad). No local StoreKit configuration file is used. Our application does not override the storefront, modify localized prices, or contain any hardcoded USD fallback. Controlled comparison We performed additional tests using the same application code on the same iPhone. The results were: Installation method Storefront Currency Local Debug build via Xcode/Flutter DEU EUR Local development-signed Release build via Flutter DEU EUR TestFlight Release build USA USD The locally installed Release build successfully retrieves all six subscription products with their correct German prices. For example, StoreKit returns the following values for one of our subscriptions: Local Release build: Storefront.current.countryCode = DEU Product currencyCode = EUR Product.displayPrice = 6,99 € TestFlight build: Storefront.current.countryCode = USA Product currencyCode = USD Both builds use the same StoreKit 2 integration and product identifiers. Technical environment Framework: Flutter StoreKit integration: StoreKit 2 Flutter plugin: in_app_purchase_storekit 0.4.11+2 Devices: Physical iPhone and iPad iOS/iPadOS: 26.6.2 Subscription products: Six auto-renewable subscriptions Expected storefront: Germany (DEU) Actual TestFlight storefront: United States (USA) We have traced the storefront country code directly to StoreKit 2’s Storefront.current.countryCode and the localized prices to the product information returned by Product.products(for:). There is no application-level storefront override or price conversion. Questions Why would StoreKit 2 return a different storefront in TestFlight compared with a locally installed development-signed Release build on the same physical device? Could TestFlight use a different sandbox storefront or Apple Account context than a locally installed build? Is there a recommended way to diagnose or reset the storefront association used by TestFlight? Has anyone experienced similar behavior where TestFlight consistently returns USA despite using a German Apple Account and newly created German sandbox testers? We have already contacted Apple Developer Support and followed their recommendation to create a completely new German sandbox tester, but the issue persists. Any guidance from Apple engineers or developers who have encountered similar behavior would be greatly appreciated. Thank you!
1
0
82
5d
TestFlight: StoreKit 2 product metadata shows USD 0.99 and no trial while the purchase sheet reports the configured offer
We are investigating a discrepancy between StoreKit 2 product metadata and the Apple purchase confirmation sheet in an iPad app distributed through internal TestFlight. The app offers one auto-renewable monthly subscription, configured for China mainland at CNY 6.80/month with a two-week introductory free trial. We would appreciate guidance on targeted diagnostics, without assuming that the cause is an Apple platform defect. Observed product metadata: build 1.0 (4) On an iPad (A16) running iPadOS 27.0.1, we independently verified the installed build and captured these public diagnostic fields during one product-loading invocation: Storefront.current.countryCode = CHN Product.priceFormatStyle.currencyCode = USD Product.price = 0.99 Product.displayPrice = US$0.99 Product.subscription.introductoryOffer = nil Product.subscription.isEligibleForIntroOffer = trueThe product and subscription-group identifiers matched the configured identifiers. Product metadata and Storefront.current were read sequentially with asynchronous calls, so this is not an atomic StoreKit snapshot. The currency and offer fields above are logged values, rather than an inference from the custom UI. For this build and product, the tester reported that the Apple system purchase sheet displayed a two-week free trial followed by CNY 6.80/month. We did not capture a screenshot of that system sheet, and no successful purchase or charge is being claimed. Subsequent replacement product: build 1.0 (5) The developer subsequently deleted the original product and created a replacement in the same subscription group. We saved and refreshed App Store Connect to check the replacement's China-mainland availability, CNY 6.80 monthly price, and two-week free-trial offer. Build 1.0 (5) uses the replacement identifier and is available in the existing internal TestFlight group. The tester confirmed installing build 5 and supplied an App screenshot showing US$0.99/month without the trial overview. The screenshot itself does not contain the build number; that attribution relies on the installation report. We have not yet captured fresh raw Product fields for this replacement. The tester also reports that its system purchase sheet is normal, but has not supplied its exact current wording or a screenshot. We therefore keep this evidence separate from the build 4 log values. Changing the ordinary Apple account under Media & Purchases did not change the reported App display. This was not a dedicated Sandbox Apple Account comparison. We have not established the replacement product's propagation state or the platform root cause. Relevant implementation path The following condensed excerpts show the production path, not a standalone reproduction project. Validation, state handling, and transaction verification are omitted here: // Product loading: let values = try await Product.products(for: [id]) guard values.count == 1, let product = values.first, product.id == id else { throw SubscriptionClientError.invalidProduct } products[id] = product // The UI model copies product.displayPrice directly. // Later, in the purchase method: guard let product = products[productID] else { throw SubscriptionClientError.unavailable } return try resolvePurchase(try await product.purchase(confirmIn: scene))Within a single completed load, the UI fields and cached purchase Product come from the same result and configured identifier. We do not convert the display price to USD or configure a separate CNY price for the system sheet. The trial overview requires an eligible two-week free-trial offer in the product data. Audited distribution artifacts did not contain a local StoreKit testing configuration or price fixture. What diagnostics would help distinguish product-metadata/storefront behavior from application state handling? Is a dedicated Sandbox-account storefront comparison the appropriate next control? Are there documented refresh requirements or known TestFlight issues relevant to this discrepancy? The existing build already logs product identifiers, raw price, currency, offer structure, and eligibility, so we can collect a targeted replacement-product observation if useful.
3
0
110
5d
MapKit route animation exported to MP4: permitted use and appropriate Apple contact
Hello, I am Rabia, publisher of RotaTakip, a pre-launch iOS outdoor GPS app being developed with my son. We are evaluating Apple Maps for a user-initiated route-video feature and would appreciate a reference to official guidance or the appropriate Apple contact before enabling it. Proposed use: A user selects their own recorded GPS route and creates a short animated recap over an Apple map. The app saves an MP4 to Photos, and the user may share it on social media or play it on non-Apple devices. Rendering would happen on the user's device using public APIs. Required Apple and third-party attribution would remain visible. We would not extract raw tiles, scrape map data, build a map database, or perform bulk/server-side rendering. The app is planned as a paid, one-time-purchase GPS app. The map would be a main visual element in the exported recap. Video export remains disabled pending clarification. We are considering two approaches separately: MKMapSnapshotter images with our own route overlays, potentially a sequence of camera views, encoded with AVFoundation. A user-initiated ReplayKit recording of an animated MKMapView, with the required system consent and recording indication. I have reviewed Attachment 6 of the Apple Developer Program License Agreement, especially sections 2.1-2.5, and the snapshot documentation. I found guidance on static snapshots, but not a clear explanation of this MP4 export and end-user sharing scenario. Questions: Is either approach a supported, permitted use under the standard agreement and documentation? Is there an official document addressing it? Does the answer differ for standard versus satellite/hybrid or 3D views, or for a fixed map with an animated route versus a moving camera? How should attribution and the Legal link be handled in a non-interactive exported video, and are there specific limits on intermediate-frame retention or rendering frequency? If separate permission or a different implementation is required, which Apple team or support category should we contact? We have submitted a Rights and Permissions inquiry and would appreciate guidance on the correct channel for this MapKit-specific question. Apps such as ReRun advertise route-video export, and Huawei Health offers dynamic route videos. We do not know the map source used in every exported video or whether these apps have separate agreements, so we are not assuming their availability grants permission for our implementation. We are looking for the documented path available to other developers. Thank you for any official references or routing guidance. Rabia / RotaTakip
0
0
36
5d
CloudKit sync fails in macOS TestFlight build – sandbox denies com.apple.cloudd
I have a macOS SwiftUI app using SwiftData with CloudKit synchronization. Bundle ID: com.mjsapps.PhrasePin CloudKit container: iCloud.com.mjsapps.PhrasePin CloudKit synchronization works when running the app from Xcode using the Development environment. However, synchronization does not work in the TestFlight / Production build. The Production schema has been deployed successfully. The TestFlight build has the expected entitlements, including: com.apple.developer.icloud-container-environment = Production com.apple.developer.icloud-container-identifiers = iCloud.com.mjsapps.PhrasePin com.apple.developer.icloud-services = CloudKit com.apple.security.app-sandbox = true com.apple.security.network.client = true The TestFlight build is signed as: Authority=TestFlight Beta Distribution Identifier=com.mjsapps.PhrasePin TeamIdentifier=8D6TX86CQK CloudKit/Core Data logging shows that the app is trying to use: container=iCloud.com.mjsapps.PhrasePin:Production but synchronization fails with: CKErrorDomain Code=6 Error connecting to CloudKit daemon NSCocoaErrorDomain Code=4099 The macOS sandbox log shows: Sandbox: PhrasePin(...) deny(1) mach-lookup com.apple.cloudd As a result, no com.apple.coredata.cloudkit.zone is created in the Production private database and no SwiftData records are synchronized. The problem has been reproduced on: macOS Sequoia 15.7.7 macOS Sequoia 15.7.9 The same app works with CloudKit in Development when run from Xcode. I have already submitted a Feedback Assistant report, but have not received a response. Has anyone seen this behavior with SwiftData + CloudKit in a sandboxed macOS TestFlight build? Is there an additional entitlement or provisioning requirement needed for access to com.apple.cloudd in Production?
1
0
67
6d
Cellular data unavailable while an underwater-depth WKExtendedRuntimeSession is running (Wi-Fi unaffected)
Our freediving app for Apple Watch Ultra declares WKBackgroundModes "underwater-depth" and "workout-processing". During a session it runs an HKWorkoutSession, enables Water Lock and starts a WKExtendedRuntimeSession. While the diver is at the surface it sends small URLSession uploads: a live position share for the people watching from shore. On an Apple Watch Ultra with its own cellular plan and the paired iPhone switched off, every URLSession request fails while the underwater-depth runtime session is running. We tested each piece on its own, checking connectivity every 10 seconds and logging URLSessionTaskTransactionMetrics.isCellular and NWPathMonitor. Cellular only: with nothing running, 26 of 27 requests succeeded over cellular. Within seconds of the underwater-depth runtime session starting, requests time out (-1001) and NWPathMonitor reports no available interface. With the HKWorkoutSession and Water Lock running but the runtime session ended, 8 of 8 succeeded over cellular. Cellular returns within about 5 seconds of the runtime session ending. Wi-Fi only (iPhone switched off, known Wi-Fi): 34 of 34 requests succeeded over the watch's own Wi-Fi in every stage, including while the underwater-depth runtime session was running. Another shipping dive app loses cellular the same way when its dive session starts, so it does not appear to be specific to our app. Steps to reproduce: on an Apple Watch Ultra with an active cellular plan, switch the paired iPhone off and move away from any known Wi-Fi network. In an app with the underwater-depth background mode, start a WKExtendedRuntimeSession, then make a URLSession request. It times out while the session runs, and succeeds again within seconds of the session ending. Our questions: Q1. Is cellular data intentionally unavailable to apps while an underwater-depth session runs, while Wi-Fi remains available? Q2. Is there a supported way to send a small amount of data over cellular during an underwater-depth session (for example while the diver is at the surface) without ending the session? Q3. If neither, we have filed FB25362581 asking for cellular to be allowed at the surface, as Wi-Fi already is. We have a focused test project (about 140 lines) that reproduces it and can share it with DTS. watchOS 27.0.1, Apple Watch Ultra 2, Xcode 27.1.
1
0
106
6d
App Review device never reaches our domain (NSURLErrorDomain -1001, no requests in server or Cloudflare logs)
Hello, Our iOS app has been rejected four times under Guideline 2.1(a) because sign-in fails on the review iPad. The latest rejection showed NSURLErrorDomain error -1001 (the request timed out) on an iPad Air 11-inch (M3) with iPadOS 27.0, on November 5, 2026, at about 11:54 UTC. The same happened on October 16, 2026. Setup: API: https://wp.pavilion.az, HTTPS on port 443, fixed DNS name DNS and proxy on Cloudflare (IPv4 and IPv6), publicly trusted certificate The app uses URLSession, with no custom certificate checks and no proxy settings What we checked: Neither our origin server nor Cloudflare logged any request from the review device on either day. Other clients were served normally during the same minutes. The domain resolves normally from many public DNS resolvers in the United States and Europe, over IPv4 and IPv6. The app signs in in under one second on an iPad simulator in a data center in Los Angeles, and on our own devices through TestFlight. This looks similar to https://developer.apple.com/forums/thread/773444, where a Cloudflare-hosted domain resolved to a wrong address inside Apple's network. Could someone from Apple check how wp.pavilion.az resolves, and whether it is reachable, from the App Review network? We have resubmitted a build that adds a short network check to the error message (the DNS result and which connection step fails), but each review cycle takes many days. Thank you.
5
0
341
6d
Egress addresses of the URL filter OHTTP relay
Hello, I am wondering about the egress addresses of the Oblivious HTTP relay that Apple runs for Network Extension URL filters. I am building an iOS app that uses NEURLFilterManager. The app builds a Bloom filter from the block lists a user picks. The system only asks our server about a site when that filter has a hit. Each lookup is encrypted with keyword PIR and carries a Privacy Pass token instead of anything tied to the user. It reaches our server through your relay, which strips the device's address. We run our own PIR server, Privacy Pass issuer and OHTTP gateway instead of a hosted service. The gateway is the one part of the setup that should only ever hear from your relay. Since every real lookup comes through the relay, I would really like to drop all other traffic to it at the firewall. Right now I can't do that. I also can't rate limit by address because every legitimate request shares the relay's addresses. As a result the gateway just has to stay open to everyone and rely on global limits, which is a far cry from what I'd want for a service that only one client is meant to reach. I have three questions about this. 1) Are the relay's egress address ranges published somewhere, or can they be shared with developers who have been onboarded? 2) If they are shared, how would we find out when they change and how much notice there is? 3) If the addresses can't be shared, is there another way to tell that a request came from the relay, such as a header or a client certificate? Please let me know if any of this is unclear or if there is a better place to ask. Thank you in advance, Alexander
1
0
92
6d
macos 27 - unexpected/new errno from BSD socket connect() when pending connections exceed backlog
Please consider the trivial C program attached to this thread. The code creates a socket() and listen()s for connections, but (intentionally) doesn't accept() the connections. The listen() is done using a small backlog (of 1). This test then does several connect() attempts and expects that the connect() attempts will accumulate in the pending queue and once the queue exceeds the backlog limit, then as specified in man listen: The backlog parameter defines the maximum length for the queue of pending connections. If a connection request arrives with the queue full, the client may receive an error with an indication of ECONNREFUSED. then the connect() attempt will receive a ECONNREFUSED. However, in macos 27, such a connect() attempt leads to ECONNRESET (Connection reset by peer) instead of ECONNREFUSED. Is this expected? Experiments show that prior versions of macos were returning a ETIMEDOUT for such connect() attempts. If this new error is expected from connect() when the backlog limit has exceeded, should it be specified in the man listen documentation? Rename the attached main.c.txt to main.c. Compiling the attached program on macos 27, using clang main.c and then running ./a.out results in: ----------------------- MacOS version: 27.0.1 Kernel version: Darwin Kernel Version 27.0.0: Tue Aug 11 21:02:16 PDT 2026; root:xnu-13432.1.9~1/RELEASE_ARM64_T8112 ----------------------- started server at at 127.0.0.1:52753 with a backlog of 1 connect() attempt 1 - connected connect() attempt 2 - connected connect() attempt 3 - connected connect() attempt 4 - connected connect() attempt 5 - failed to connect() - Connection reset by peer <-- FAILURE: Unexpected error code, expected either ETIMEDOUT or ECONNREFUSED but got 54 connect() attempt 6 - connected connect() attempt 7 - connected connect() attempt 8 - connected connect() attempt 9 - failed to connect() - Connection reset by peer <-- FAILURE: Unexpected error code, expected either ETIMEDOUT or ECONNREFUSED but got 54 connect() attempt 10 - failed to connect() - Connection reset by peer <-- FAILURE: Unexpected error code, expected either ETIMEDOUT or ECONNREFUSED but got 54 connect() attempt 11 - failed to connect() - Connection reset by peer <-- FAILURE: Unexpected error code, expected either ETIMEDOUT or ECONNREFUSED but got 54 On a related note, it's unclear why several of the connect() attempts succeeded instead of just 1 of them succeeding. On prior versions of macos, the output of the same program is: ----------------------- MacOS version: 26.7.1 Kernel version: Darwin Kernel Version 25.6.0: Tue Aug 18 17:49:13 PDT 2026; root:xnu-12377.161.15.700.19~2/RELEASE_ARM64_T6000 ----------------------- started server at at 127.0.0.1:52451 with a backlog of 1 connect() attempt 1 - connected connect() attempt 2 - failed to connect() - Operation timed out connect() attempt 3 - failed to connect() - Operation timed out connect() attempt 4 - failed to connect() - Operation timed out connect() attempt 5 - failed to connect() - Operation timed out connect() attempt 6 - failed to connect() - Operation timed out connect() attempt 7 - failed to connect() - Operation timed out connect() attempt 8 - failed to connect() - Operation timed out connect() attempt 9 - failed to connect() - Operation timed out connect() attempt 10 - failed to connect() - Operation timed out connect() attempt 11 - failed to connect() - Operation timed out and this output is much more understandable and deterministic. main.c.txt
3
0
380
6d
Instructions for debugging recent macos kernel versions?
Is there any recent and a bit authoritative documentation which explains how to debug recent versions of macos kernel? I have found some blog posts from other users but those are either outdated or don't work for some other reason. I am guessing kernel debugging is pretty common for developers working on macos itself, so I'm hoping someone in this forum would have some working instructions for that.
20
1
1.6k
6d
AccessoryAccess for a Developer ID virtualization app: can it replace a root daemon for USB storage devices?
I build AVM, the Accessible Virtual Machine, a free, open source Mac app that runs Windows 11 for ARM in QEMU. It's built for blind people who use VoiceOver on the Mac and a screen reader in Windows. It's on GitHub at https://github.com/allisonfm85/accessible-virtual-machine. AVM ships with Developer ID, it's notarized, and it isn't sandboxed. QEMU runs as a child process, signed by the same team, and does the USB work itself through usbredir and libusb. I asked DTS about this (case 23107052), and Quinn pointed me to thread 851767. Today AVM captures USB devices from a root daemon registered with SMAppService. That works for braille displays and microphones. It fails for USB flash drives. Opening interface 0 returns 0xe00002c9. I measured why with a small IOUSBHost tool: Run with sudo from a terminal that has Removable Volumes: works. Same command with Removable Volumes turned off: fails with 0xe00002c9. Run as a launchd daemon in the system domain: fails. Full Disk Access makes no difference. So the block is the Removable Volumes permission, and a daemon has no responsible app to carry it. Granting it to AVM doesn't help the daemon. Thread 851767 shows a flash drive working through AccessoryAccess and IOUSBHostDevice, with interfaces opened through IOUSBLib. That looks like the path I should be on. My questions: Is the Claim USB Accessory capability (com.apple.developer.accessory-access.usb) available to Developer ID apps outside the Mac App Store? Does it require the App Sandbox? Does the user's AccessoryAccess consent cover a USB storage device's interfaces? In other words, would it get past the Removable Volumes check that stops my daemon? Can AVM pass createXPCRepresentation to QEMU, a non-sandboxed child process from the same team, and have QEMU open the accessory there? libusb opens interfaces through IOUSBLib. Given FB25324561, is it reasonable to ship on that path for now? If AccessoryAccess isn't available to Developer ID apps, I'd still welcome guidance on a supported way, such as com.apple.vm.device-access. I'm happy to share my sample project or logs. Thank you, Allison Meloy
1
0
123
6d
SKTestSession.setSimulatedError does not work - Products load successfully despite error configuration
Description I'm attempting to test error handling in my StoreKit implementation using SKTestSession.setSimulatedError(), but it doesn't trigger any errors. All StoreKit APIs (.loadProducts, .purchase, .appTransaction) succeed despite error simulation being configured before API calls. According to Apple's documentation, setSimulatedError(_:forAPI:) should cause the specified API to throw an error, but this doesn't happen in my testing environment. Background / Known issue I found a previous forum discussion: "SKTestSession.setSimulatedError() not working for .loadProducts API in iOS 26.2" which mentioned this was a bug in iOS 26.2 and was supposedly fixed in iOS 26.3. However, I'm experiencing the same issue in my current environment (Xcode 26.6 / iOS 26.5), which suggests either: The bug has regressed, or There's a different underlying issue, or I'm missing something in my implementation I wanted to report this to confirm whether this is still a known issue or if additional steps are needed. Environment Xcode: 26.6 Test Environment: iOS Simulator - iPhone 17 Pro(26.5) Testing Framework: XCTest StoreKitTest Framework: Included in Xcode Code Unit test code import XCTest import StoreKit import StoreKitTest final class StoreKitErrorTests: XCTestCase { func test_LoadProducts_SetSimulatedError() async throws { // Arrange let session = try SKTestSession(configurationFileNamed: "storekit") session.clearTransactions() session.disableDialogs = true // Set simulated error for loadProducts API try await session.setSimulatedError( .generic(.unknown), forAPI: .loadProducts ) // Act - Attempt to load products do { let products = try await Product.products(for: ["com.example.app.testproduct"]) // This line executes - products were loaded successfully print("[TEST] FAIL: Loaded \(products.count) products") XCTFail("setSimulatedError did not work - products loaded successfully") } catch { // This should execute, but it doesn't print("[TEST] PASS: Error was thrown") } } }.storekit file Note: Showing only the product definition. File also contains settings and version info. { "products" : [ { "displayPrice" : "1.23", "familyShareable" : false, "internalID" : "5AE6F98A", "localizations" : [ { "description" : "Test app", "displayName" : "LsStorekit", "locale" : "en_US" } ], "productID" : "com.example.app.testproduct", "referenceName" : "LsStorekit", "type" : "NonConsumable" } ] }Expected Behavior The Product.products(for:) call should throw an error because setSimulatedError(.generic(.unknown), forAPI: .loadProducts) was called before the API invocation. The test should: Configure the simulated error Attempt to load products Catch an error in the catch block Test passes with: "[TEST] PASS: Error was thrown" Actual Behavior Products are loaded successfully despite the error simulation: • The do block completes without throwing • 1 product is returned from Product.products(for:) • XCTFail() is called, indicating the error simulation didn't work • Test fails with: "[TEST] FAIL: Loaded 1 products" Console Output [TEST] FAIL: Loaded 1 products Additional Testing I've tested setSimulatedError with multiple APIs, and all show the same behavior: APIError configurationResult.loadProducts.generic(.unknown)No error thrown.purchase.generic(.unknown)No error thrown.appTransaction.generic(.unknown)No error thrown.appStoreSync.generic(.unknown)No error thrownWhat I've Already Tried • Calling setSimulatedError before app launch (in UI tests) • Calling setSimulatedError after app launch but before API calls • Using different error types (.generic(.unknown), .generic(.networkError(...))) • Testing in both Unit Tests and UI Tests • Using different APIs (.loadProducts, .purchase, .appTransaction) • Clearing transactions and resetting session state • Verifying the .storekit file is correctly loaded (products load successfully) • Running the app first (⌘R) to ensure StoreKit configuration is registered with the StoreKit daemon - This was necessary to fix an initial issue where products weren't loading at all Questions Is this a known limitation of SKTestSession.setSimulatedError()? Are there additional steps required to make error simulation work? Is there an alternative approach to test StoreKit error handling? Does this work in specific Xcode/iOS SDK versions only? Any guidance would be greatly appreciated. I need to test error handling in my StoreKit implementation, but cannot find a way to simulate errors reliably.
Replies
0
Boosts
0
Views
40
Activity
5d
CrashReporterExtension does not work on MacOS.
The new CrashReporterExtension is documented as working on MacOS, but the system extension definition disagrees, it only shows it as working on iOS: /System/Library/ExtensionKit/ExtensionPoints/com.apple.crash-reporter.extension.appexpt How can we work around that problem?
Replies
1
Boosts
0
Views
63
Activity
5d
Local Network Privacy Child Process Behavior
I have a Java Swing application that is bundled into an app bundle using jpackage. The app basically launches a newer version of itself, when there is a new version downloaded in the users installation directory. I have noticed a regression or change in behavior with how LocalNetwork privacy works now. Previously, we would launch our Java application using the .app bundle. This is a launcher that checks for updates and will launch another JVM instance using any new jars it downloads when updating. So, it is closing the original process and spawning a new process using the downloaded jar. The new process is where the app connects to a server on the Local Network. This new process cannot access the Local Network even when the entry in privacy and security is enabled for the parent process. I have changed the behavior of my launcher application so that it keeps the process alive after launching the client application. When doing this, Local Network access works. So, my question is: is it required for the parent process to be running in order for a child process to have Local Network access? In previous macOS versions, this was not an issue, so something has changed with Local Network security across all the latest versions 26 and 27.
Replies
8
Boosts
0
Views
256
Activity
5d
Production AppTransaction.shared throws StoreKitError.unknown when reading original app acquisition date
I'm the developer of Freezon, and I ran into this on my own iPhone with the App Store version of the app. I use the verified AppTransaction.originalPurchaseDate to give Pro access to people who first downloaded the app before a published cutoff. This includes free downloads; I need the original acquisition date of the app itself, not an in-app purchase date. On this device, AppTransaction.shared repeatedly threw StoreKitError.unknown before returning a VerificationResult: let result = try await AppTransaction.shared switch result { case let .verified(transaction): let firstAcquisitionDate = transaction.originalPurchaseDate // Check early-adopter eligibility. case let .unverified(_, error): throw error }The error occurs at shared, before the switch. The App Store on this iPhone shows my Apple Account as signed in. However, when I purchase or restore, I keep getting asked for my password, and sometimes for both my Apple Account and password. I used to get the usual purchase confirmation more directly. I don't know whether these prompts are related to the shared failure. For context: App Store release 1.1.1 (2), bundle com.zyiszy.PrivateVault, App Store ID 6810494416. The app diagnostic recorded iOS 27.0.1. It did not capture the exact OS build or hardware model. In one capture, 13 native shared calls failed between 2026-11-16 01:11:43.824 and 01:13:16.124 UTC. All were matched as StoreKitError.unknown, with NSError domain StoreKit.StoreKitError, code 2, and no underlying error. This is not SKErrorDomain code 2 / payment cancellation. The first call failed while the network path was unsatisfied. The next 12 failed with a satisfied path, the app active and protected data available. Those calls returned in 0-1 ms. Bounded retries, with about 2- and 5-second delays, did not help in that capture. Product catalog requests succeeded during the same period. I realize that does not confirm connectivity to every App Store endpoint. The app does not automatically call refresh() or AppStore.sync() during this eligibility check. After force-quitting, reopening and using Restore, I eventually got access again. Unfortunately, I don't have a log of the successful recovery, so I can't tell which call succeeded. Could StoreKit still need fresh authentication even though the App Store shows the account as signed in? Can that cause shared to throw unknown without an underlying error, and is there a supported way to distinguish it from missing app transaction data? For this acquisition-date check, should the recovery button call AppTransaction.refresh() and use its verified result directly? Is AppStore.sync() needed at all? If more evidence is needed, which StoreKit logs or diagnostic profile should I collect before trying recovery next time? I also submitted DTS Case-ID: 23550827 with a small Xcode project and the redacted timeline. The project builds and isolates the API calls, but it has its own bundle identity and does not reproduce this production account state.
Replies
1
Boosts
0
Views
209
Activity
5d
CloudKit public database: unknownItem despite earlier Console visibility — interpreting fetch and authorization diagnostics
We are investigating one completed CloudKit Development test in a separate test container using only synthetic data. Shortly before an iOS client attempted to fetch a record from the public database’s default zone, that synthetic record was visible in CloudKit Console. The native client returned: CKErrorDomain code 11 (unknownItem) Underlying CKInternalErrorDomain code 2003 Sanitized diagnostic: record_not_found No record We verified that the client’s intended container, database, zone and record name matched the reference. A CloudKit Console event showed RecordFetch, operation-level SUCCESS, and approximately 171 ms execution time. However: The event was correlated by context and timestamp, not by a directly matched client operation or request ID. The available event did not expose a per-record result or an authorization decision. Earlier Console visibility does not establish availability or client access at the exact time of the fetch. The cause therefore remains unresolved. We have not established that a permissions restriction caused the error. We understand that Apple documents unknownItem for a nonexistent record and permissionFailure for insufficient permission to fetch or save data. We also understand that operation-level success and per-record fetch success are distinct. Our questions are: Can a public-database read restriction cause an existing record to be reported to a native client as unknownItem, rather than permissionFailure? If so, is this documented behavior? What does operation-level SUCCESS mean specifically for a RecordFetch event in CloudKit Console? Can that event still contain an unsuccessful individual record lookup? Which supported diagnostics can distinguish a missing or unavailable record from an authorization-based visibility restriction? Can Apple determine the authorization outcome of an existing request from retained diagnostics, and which correlation identifiers are required? What evidence is sufficient to verify server-enforced read restrictions in Development while preserving the existing roles and leaving production untouched? We are seeking clarification of the existing evidence, not proposing another reproduction attempt. No customer data, credentials or production records are involved.
Replies
3
Boosts
0
Views
138
Activity
5d
Can one Apple Developer team issue Wallet loyalty passes for multiple independent businesses?
In a web-based loyalty platform, each participating business defines its own rewards and authorizes the platform to display its name and logo on Apple Wallet passes. The platform would identify itself as the issuer and handle pass distribution and updates. Can the platform sign and update these passes using Pass Type IDs registered to a single Apple Developer team, or does each participating business need its own Apple Developer team and signing certificate? Is there official Apple documentation that covers this setup?
Replies
0
Boosts
0
Views
72
Activity
5d
WCSession.sendMessage is crashing when a reply or error handler is attached, why?
The following code should send a message from the watch to the iPhone. Unfortunately, it is crashing. I have no clue why. if WCSession.isSupported() { let session = WCSession.default if ((session.activationState == .activated) && session.isReachable) { session.sendMessage(["SimpleMessages":["start"]], replyHandler:{reply in _ = 0 }, errorHandler:nil) } } If the reply handler is set to nil, the code does not crash. Anyway, in both cases the message is correctly sent from the watch to the phone. The code itself is run on the main thread (verified). I am running watchOS 26.6 and iOS 27. Here is the crash : Stack trace
Replies
4
Boosts
0
Views
386
Activity
5d
StoreKit 2 returns USA/USD in TestFlight but DEU/EUR in local Release build on the same device
Hi everyone, We are currently preparing the release of our Flutter-based iOS application and are experiencing an unusual StoreKit 2 storefront issue that only occurs when the app is installed through TestFlight. The problem When our application is installed through TestFlight, StoreKit 2 consistently returns the United States storefront (USA), and all six auto-renewable subscription products are displayed with USD prices. However, both the regular Apple Account and the Sandbox Apple Account are configured for Germany. We have verified the following: All six subscription products are correctly configured in App Store Connect with EUR prices for Germany. The subscriptions are available in Germany, Austria, and Switzerland. We created a completely new Sandbox tester with Germany selected during account creation, using an email address that had never previously been used for sandbox testing. The issue occurs on two different physical devices (iPhone and iPad). No local StoreKit configuration file is used. Our application does not override the storefront, modify localized prices, or contain any hardcoded USD fallback. Controlled comparison We performed additional tests using the same application code on the same iPhone. The results were: Installation method Storefront Currency Local Debug build via Xcode/Flutter DEU EUR Local development-signed Release build via Flutter DEU EUR TestFlight Release build USA USD The locally installed Release build successfully retrieves all six subscription products with their correct German prices. For example, StoreKit returns the following values for one of our subscriptions: Local Release build: Storefront.current.countryCode = DEU Product currencyCode = EUR Product.displayPrice = 6,99 € TestFlight build: Storefront.current.countryCode = USA Product currencyCode = USD Both builds use the same StoreKit 2 integration and product identifiers. Technical environment Framework: Flutter StoreKit integration: StoreKit 2 Flutter plugin: in_app_purchase_storekit 0.4.11+2 Devices: Physical iPhone and iPad iOS/iPadOS: 26.6.2 Subscription products: Six auto-renewable subscriptions Expected storefront: Germany (DEU) Actual TestFlight storefront: United States (USA) We have traced the storefront country code directly to StoreKit 2’s Storefront.current.countryCode and the localized prices to the product information returned by Product.products(for:). There is no application-level storefront override or price conversion. Questions Why would StoreKit 2 return a different storefront in TestFlight compared with a locally installed development-signed Release build on the same physical device? Could TestFlight use a different sandbox storefront or Apple Account context than a locally installed build? Is there a recommended way to diagnose or reset the storefront association used by TestFlight? Has anyone experienced similar behavior where TestFlight consistently returns USA despite using a German Apple Account and newly created German sandbox testers? We have already contacted Apple Developer Support and followed their recommendation to create a completely new German sandbox tester, but the issue persists. Any guidance from Apple engineers or developers who have encountered similar behavior would be greatly appreciated. Thank you!
Replies
4
Boosts
0
Views
146
Activity
5d
StoreKit 2 returns USA/USD in TestFlight but DEU/EUR in local Release build on the same device
Hi everyone, We are currently preparing the release of our Flutter-based iOS application and are experiencing an unusual StoreKit 2 storefront issue that only occurs when the app is installed through TestFlight. The problem When our application is installed through TestFlight, StoreKit 2 consistently returns the United States storefront (USA), and all six auto-renewable subscription products are displayed with USD prices. However, both the regular Apple Account and the Sandbox Apple Account are configured for Germany. We have verified the following: All six subscription products are correctly configured in App Store Connect with EUR prices for Germany. The subscriptions are available in Germany, Austria, and Switzerland. We created a completely new Sandbox tester with Germany selected during account creation, using an email address that had never previously been used for sandbox testing. The issue occurs on two different physical devices (iPhone and iPad). No local StoreKit configuration file is used. Our application does not override the storefront, modify localized prices, or contain any hardcoded USD fallback. Controlled comparison We performed additional tests using the same application code on the same iPhone. The results were: Installation method Storefront Currency Local Debug build via Xcode/Flutter DEU EUR Local development-signed Release build via Flutter DEU EUR TestFlight Release build USA USD The locally installed Release build successfully retrieves all six subscription products with their correct German prices. For example, StoreKit returns the following values for one of our subscriptions: Local Release build: Storefront.current.countryCode = DEU Product currencyCode = EUR Product.displayPrice = 6,99 € TestFlight build: Storefront.current.countryCode = USA Product currencyCode = USD Both builds use the same StoreKit 2 integration and product identifiers. Technical environment Framework: Flutter StoreKit integration: StoreKit 2 Flutter plugin: in_app_purchase_storekit 0.4.11+2 Devices: Physical iPhone and iPad iOS/iPadOS: 26.6.2 Subscription products: Six auto-renewable subscriptions Expected storefront: Germany (DEU) Actual TestFlight storefront: United States (USA) We have traced the storefront country code directly to StoreKit 2’s Storefront.current.countryCode and the localized prices to the product information returned by Product.products(for:). There is no application-level storefront override or price conversion. Questions Why would StoreKit 2 return a different storefront in TestFlight compared with a locally installed development-signed Release build on the same physical device? Could TestFlight use a different sandbox storefront or Apple Account context than a locally installed build? Is there a recommended way to diagnose or reset the storefront association used by TestFlight? Has anyone experienced similar behavior where TestFlight consistently returns USA despite using a German Apple Account and newly created German sandbox testers? We have already contacted Apple Developer Support and followed their recommendation to create a completely new German sandbox tester, but the issue persists. Any guidance from Apple engineers or developers who have encountered similar behavior would be greatly appreciated. Thank you!
Replies
1
Boosts
0
Views
82
Activity
5d
TestFlight: StoreKit 2 product metadata shows USD 0.99 and no trial while the purchase sheet reports the configured offer
We are investigating a discrepancy between StoreKit 2 product metadata and the Apple purchase confirmation sheet in an iPad app distributed through internal TestFlight. The app offers one auto-renewable monthly subscription, configured for China mainland at CNY 6.80/month with a two-week introductory free trial. We would appreciate guidance on targeted diagnostics, without assuming that the cause is an Apple platform defect. Observed product metadata: build 1.0 (4) On an iPad (A16) running iPadOS 27.0.1, we independently verified the installed build and captured these public diagnostic fields during one product-loading invocation: Storefront.current.countryCode = CHN Product.priceFormatStyle.currencyCode = USD Product.price = 0.99 Product.displayPrice = US$0.99 Product.subscription.introductoryOffer = nil Product.subscription.isEligibleForIntroOffer = trueThe product and subscription-group identifiers matched the configured identifiers. Product metadata and Storefront.current were read sequentially with asynchronous calls, so this is not an atomic StoreKit snapshot. The currency and offer fields above are logged values, rather than an inference from the custom UI. For this build and product, the tester reported that the Apple system purchase sheet displayed a two-week free trial followed by CNY 6.80/month. We did not capture a screenshot of that system sheet, and no successful purchase or charge is being claimed. Subsequent replacement product: build 1.0 (5) The developer subsequently deleted the original product and created a replacement in the same subscription group. We saved and refreshed App Store Connect to check the replacement's China-mainland availability, CNY 6.80 monthly price, and two-week free-trial offer. Build 1.0 (5) uses the replacement identifier and is available in the existing internal TestFlight group. The tester confirmed installing build 5 and supplied an App screenshot showing US$0.99/month without the trial overview. The screenshot itself does not contain the build number; that attribution relies on the installation report. We have not yet captured fresh raw Product fields for this replacement. The tester also reports that its system purchase sheet is normal, but has not supplied its exact current wording or a screenshot. We therefore keep this evidence separate from the build 4 log values. Changing the ordinary Apple account under Media & Purchases did not change the reported App display. This was not a dedicated Sandbox Apple Account comparison. We have not established the replacement product's propagation state or the platform root cause. Relevant implementation path The following condensed excerpts show the production path, not a standalone reproduction project. Validation, state handling, and transaction verification are omitted here: // Product loading: let values = try await Product.products(for: [id]) guard values.count == 1, let product = values.first, product.id == id else { throw SubscriptionClientError.invalidProduct } products[id] = product // The UI model copies product.displayPrice directly. // Later, in the purchase method: guard let product = products[productID] else { throw SubscriptionClientError.unavailable } return try resolvePurchase(try await product.purchase(confirmIn: scene))Within a single completed load, the UI fields and cached purchase Product come from the same result and configured identifier. We do not convert the display price to USD or configure a separate CNY price for the system sheet. The trial overview requires an eligible two-week free-trial offer in the product data. Audited distribution artifacts did not contain a local StoreKit testing configuration or price fixture. What diagnostics would help distinguish product-metadata/storefront behavior from application state handling? Is a dedicated Sandbox-account storefront comparison the appropriate next control? Are there documented refresh requirements or known TestFlight issues relevant to this discrepancy? The existing build already logs product identifiers, raw price, currency, offer structure, and eligibility, so we can collect a targeted replacement-product observation if useful.
Replies
3
Boosts
0
Views
110
Activity
5d
MapKit route animation exported to MP4: permitted use and appropriate Apple contact
Hello, I am Rabia, publisher of RotaTakip, a pre-launch iOS outdoor GPS app being developed with my son. We are evaluating Apple Maps for a user-initiated route-video feature and would appreciate a reference to official guidance or the appropriate Apple contact before enabling it. Proposed use: A user selects their own recorded GPS route and creates a short animated recap over an Apple map. The app saves an MP4 to Photos, and the user may share it on social media or play it on non-Apple devices. Rendering would happen on the user's device using public APIs. Required Apple and third-party attribution would remain visible. We would not extract raw tiles, scrape map data, build a map database, or perform bulk/server-side rendering. The app is planned as a paid, one-time-purchase GPS app. The map would be a main visual element in the exported recap. Video export remains disabled pending clarification. We are considering two approaches separately: MKMapSnapshotter images with our own route overlays, potentially a sequence of camera views, encoded with AVFoundation. A user-initiated ReplayKit recording of an animated MKMapView, with the required system consent and recording indication. I have reviewed Attachment 6 of the Apple Developer Program License Agreement, especially sections 2.1-2.5, and the snapshot documentation. I found guidance on static snapshots, but not a clear explanation of this MP4 export and end-user sharing scenario. Questions: Is either approach a supported, permitted use under the standard agreement and documentation? Is there an official document addressing it? Does the answer differ for standard versus satellite/hybrid or 3D views, or for a fixed map with an animated route versus a moving camera? How should attribution and the Legal link be handled in a non-interactive exported video, and are there specific limits on intermediate-frame retention or rendering frequency? If separate permission or a different implementation is required, which Apple team or support category should we contact? We have submitted a Rights and Permissions inquiry and would appreciate guidance on the correct channel for this MapKit-specific question. Apps such as ReRun advertise route-video export, and Huawei Health offers dynamic route videos. We do not know the map source used in every exported video or whether these apps have separate agreements, so we are not assuming their availability grants permission for our implementation. We are looking for the documented path available to other developers. Thank you for any official references or routing guidance. Rabia / RotaTakip
Replies
0
Boosts
0
Views
36
Activity
5d
CloudKit sync fails in macOS TestFlight build – sandbox denies com.apple.cloudd
I have a macOS SwiftUI app using SwiftData with CloudKit synchronization. Bundle ID: com.mjsapps.PhrasePin CloudKit container: iCloud.com.mjsapps.PhrasePin CloudKit synchronization works when running the app from Xcode using the Development environment. However, synchronization does not work in the TestFlight / Production build. The Production schema has been deployed successfully. The TestFlight build has the expected entitlements, including: com.apple.developer.icloud-container-environment = Production com.apple.developer.icloud-container-identifiers = iCloud.com.mjsapps.PhrasePin com.apple.developer.icloud-services = CloudKit com.apple.security.app-sandbox = true com.apple.security.network.client = true The TestFlight build is signed as: Authority=TestFlight Beta Distribution Identifier=com.mjsapps.PhrasePin TeamIdentifier=8D6TX86CQK CloudKit/Core Data logging shows that the app is trying to use: container=iCloud.com.mjsapps.PhrasePin:Production but synchronization fails with: CKErrorDomain Code=6 Error connecting to CloudKit daemon NSCocoaErrorDomain Code=4099 The macOS sandbox log shows: Sandbox: PhrasePin(...) deny(1) mach-lookup com.apple.cloudd As a result, no com.apple.coredata.cloudkit.zone is created in the Production private database and no SwiftData records are synchronized. The problem has been reproduced on: macOS Sequoia 15.7.7 macOS Sequoia 15.7.9 The same app works with CloudKit in Development when run from Xcode. I have already submitted a Feedback Assistant report, but have not received a response. Has anyone seen this behavior with SwiftData + CloudKit in a sandboxed macOS TestFlight build? Is there an additional entitlement or provisioning requirement needed for access to com.apple.cloudd in Production?
Replies
1
Boosts
0
Views
67
Activity
6d
Cellular data unavailable while an underwater-depth WKExtendedRuntimeSession is running (Wi-Fi unaffected)
Our freediving app for Apple Watch Ultra declares WKBackgroundModes "underwater-depth" and "workout-processing". During a session it runs an HKWorkoutSession, enables Water Lock and starts a WKExtendedRuntimeSession. While the diver is at the surface it sends small URLSession uploads: a live position share for the people watching from shore. On an Apple Watch Ultra with its own cellular plan and the paired iPhone switched off, every URLSession request fails while the underwater-depth runtime session is running. We tested each piece on its own, checking connectivity every 10 seconds and logging URLSessionTaskTransactionMetrics.isCellular and NWPathMonitor. Cellular only: with nothing running, 26 of 27 requests succeeded over cellular. Within seconds of the underwater-depth runtime session starting, requests time out (-1001) and NWPathMonitor reports no available interface. With the HKWorkoutSession and Water Lock running but the runtime session ended, 8 of 8 succeeded over cellular. Cellular returns within about 5 seconds of the runtime session ending. Wi-Fi only (iPhone switched off, known Wi-Fi): 34 of 34 requests succeeded over the watch's own Wi-Fi in every stage, including while the underwater-depth runtime session was running. Another shipping dive app loses cellular the same way when its dive session starts, so it does not appear to be specific to our app. Steps to reproduce: on an Apple Watch Ultra with an active cellular plan, switch the paired iPhone off and move away from any known Wi-Fi network. In an app with the underwater-depth background mode, start a WKExtendedRuntimeSession, then make a URLSession request. It times out while the session runs, and succeeds again within seconds of the session ending. Our questions: Q1. Is cellular data intentionally unavailable to apps while an underwater-depth session runs, while Wi-Fi remains available? Q2. Is there a supported way to send a small amount of data over cellular during an underwater-depth session (for example while the diver is at the surface) without ending the session? Q3. If neither, we have filed FB25362581 asking for cellular to be allowed at the surface, as Wi-Fi already is. We have a focused test project (about 140 lines) that reproduces it and can share it with DTS. watchOS 27.0.1, Apple Watch Ultra 2, Xcode 27.1.
Replies
1
Boosts
0
Views
106
Activity
6d
App Review device never reaches our domain (NSURLErrorDomain -1001, no requests in server or Cloudflare logs)
Hello, Our iOS app has been rejected four times under Guideline 2.1(a) because sign-in fails on the review iPad. The latest rejection showed NSURLErrorDomain error -1001 (the request timed out) on an iPad Air 11-inch (M3) with iPadOS 27.0, on November 5, 2026, at about 11:54 UTC. The same happened on October 16, 2026. Setup: API: https://wp.pavilion.az, HTTPS on port 443, fixed DNS name DNS and proxy on Cloudflare (IPv4 and IPv6), publicly trusted certificate The app uses URLSession, with no custom certificate checks and no proxy settings What we checked: Neither our origin server nor Cloudflare logged any request from the review device on either day. Other clients were served normally during the same minutes. The domain resolves normally from many public DNS resolvers in the United States and Europe, over IPv4 and IPv6. The app signs in in under one second on an iPad simulator in a data center in Los Angeles, and on our own devices through TestFlight. This looks similar to https://developer.apple.com/forums/thread/773444, where a Cloudflare-hosted domain resolved to a wrong address inside Apple's network. Could someone from Apple check how wp.pavilion.az resolves, and whether it is reachable, from the App Review network? We have resubmitted a build that adds a short network check to the error message (the DNS result and which connection step fails), but each review cycle takes many days. Thank you.
Replies
5
Boosts
0
Views
341
Activity
6d
Egress addresses of the URL filter OHTTP relay
Hello, I am wondering about the egress addresses of the Oblivious HTTP relay that Apple runs for Network Extension URL filters. I am building an iOS app that uses NEURLFilterManager. The app builds a Bloom filter from the block lists a user picks. The system only asks our server about a site when that filter has a hit. Each lookup is encrypted with keyword PIR and carries a Privacy Pass token instead of anything tied to the user. It reaches our server through your relay, which strips the device's address. We run our own PIR server, Privacy Pass issuer and OHTTP gateway instead of a hosted service. The gateway is the one part of the setup that should only ever hear from your relay. Since every real lookup comes through the relay, I would really like to drop all other traffic to it at the firewall. Right now I can't do that. I also can't rate limit by address because every legitimate request shares the relay's addresses. As a result the gateway just has to stay open to everyone and rely on global limits, which is a far cry from what I'd want for a service that only one client is meant to reach. I have three questions about this. 1) Are the relay's egress address ranges published somewhere, or can they be shared with developers who have been onboarded? 2) If they are shared, how would we find out when they change and how much notice there is? 3) If the addresses can't be shared, is there another way to tell that a request came from the relay, such as a header or a client certificate? Please let me know if any of this is unclear or if there is a better place to ask. Thank you in advance, Alexander
Replies
1
Boosts
0
Views
92
Activity
6d
macos 27 - unexpected/new errno from BSD socket connect() when pending connections exceed backlog
Please consider the trivial C program attached to this thread. The code creates a socket() and listen()s for connections, but (intentionally) doesn't accept() the connections. The listen() is done using a small backlog (of 1). This test then does several connect() attempts and expects that the connect() attempts will accumulate in the pending queue and once the queue exceeds the backlog limit, then as specified in man listen: The backlog parameter defines the maximum length for the queue of pending connections. If a connection request arrives with the queue full, the client may receive an error with an indication of ECONNREFUSED. then the connect() attempt will receive a ECONNREFUSED. However, in macos 27, such a connect() attempt leads to ECONNRESET (Connection reset by peer) instead of ECONNREFUSED. Is this expected? Experiments show that prior versions of macos were returning a ETIMEDOUT for such connect() attempts. If this new error is expected from connect() when the backlog limit has exceeded, should it be specified in the man listen documentation? Rename the attached main.c.txt to main.c. Compiling the attached program on macos 27, using clang main.c and then running ./a.out results in: ----------------------- MacOS version: 27.0.1 Kernel version: Darwin Kernel Version 27.0.0: Tue Aug 11 21:02:16 PDT 2026; root:xnu-13432.1.9~1/RELEASE_ARM64_T8112 ----------------------- started server at at 127.0.0.1:52753 with a backlog of 1 connect() attempt 1 - connected connect() attempt 2 - connected connect() attempt 3 - connected connect() attempt 4 - connected connect() attempt 5 - failed to connect() - Connection reset by peer <-- FAILURE: Unexpected error code, expected either ETIMEDOUT or ECONNREFUSED but got 54 connect() attempt 6 - connected connect() attempt 7 - connected connect() attempt 8 - connected connect() attempt 9 - failed to connect() - Connection reset by peer <-- FAILURE: Unexpected error code, expected either ETIMEDOUT or ECONNREFUSED but got 54 connect() attempt 10 - failed to connect() - Connection reset by peer <-- FAILURE: Unexpected error code, expected either ETIMEDOUT or ECONNREFUSED but got 54 connect() attempt 11 - failed to connect() - Connection reset by peer <-- FAILURE: Unexpected error code, expected either ETIMEDOUT or ECONNREFUSED but got 54 On a related note, it's unclear why several of the connect() attempts succeeded instead of just 1 of them succeeding. On prior versions of macos, the output of the same program is: ----------------------- MacOS version: 26.7.1 Kernel version: Darwin Kernel Version 25.6.0: Tue Aug 18 17:49:13 PDT 2026; root:xnu-12377.161.15.700.19~2/RELEASE_ARM64_T6000 ----------------------- started server at at 127.0.0.1:52451 with a backlog of 1 connect() attempt 1 - connected connect() attempt 2 - failed to connect() - Operation timed out connect() attempt 3 - failed to connect() - Operation timed out connect() attempt 4 - failed to connect() - Operation timed out connect() attempt 5 - failed to connect() - Operation timed out connect() attempt 6 - failed to connect() - Operation timed out connect() attempt 7 - failed to connect() - Operation timed out connect() attempt 8 - failed to connect() - Operation timed out connect() attempt 9 - failed to connect() - Operation timed out connect() attempt 10 - failed to connect() - Operation timed out connect() attempt 11 - failed to connect() - Operation timed out and this output is much more understandable and deterministic. main.c.txt
Replies
3
Boosts
0
Views
380
Activity
6d
Instructions for debugging recent macos kernel versions?
Is there any recent and a bit authoritative documentation which explains how to debug recent versions of macos kernel? I have found some blog posts from other users but those are either outdated or don't work for some other reason. I am guessing kernel debugging is pretty common for developers working on macos itself, so I'm hoping someone in this forum would have some working instructions for that.
Replies
20
Boosts
1
Views
1.6k
Activity
6d
AccessoryAccess for a Developer ID virtualization app: can it replace a root daemon for USB storage devices?
I build AVM, the Accessible Virtual Machine, a free, open source Mac app that runs Windows 11 for ARM in QEMU. It's built for blind people who use VoiceOver on the Mac and a screen reader in Windows. It's on GitHub at https://github.com/allisonfm85/accessible-virtual-machine. AVM ships with Developer ID, it's notarized, and it isn't sandboxed. QEMU runs as a child process, signed by the same team, and does the USB work itself through usbredir and libusb. I asked DTS about this (case 23107052), and Quinn pointed me to thread 851767. Today AVM captures USB devices from a root daemon registered with SMAppService. That works for braille displays and microphones. It fails for USB flash drives. Opening interface 0 returns 0xe00002c9. I measured why with a small IOUSBHost tool: Run with sudo from a terminal that has Removable Volumes: works. Same command with Removable Volumes turned off: fails with 0xe00002c9. Run as a launchd daemon in the system domain: fails. Full Disk Access makes no difference. So the block is the Removable Volumes permission, and a daemon has no responsible app to carry it. Granting it to AVM doesn't help the daemon. Thread 851767 shows a flash drive working through AccessoryAccess and IOUSBHostDevice, with interfaces opened through IOUSBLib. That looks like the path I should be on. My questions: Is the Claim USB Accessory capability (com.apple.developer.accessory-access.usb) available to Developer ID apps outside the Mac App Store? Does it require the App Sandbox? Does the user's AccessoryAccess consent cover a USB storage device's interfaces? In other words, would it get past the Removable Volumes check that stops my daemon? Can AVM pass createXPCRepresentation to QEMU, a non-sandboxed child process from the same team, and have QEMU open the accessory there? libusb opens interfaces through IOUSBLib. Given FB25324561, is it reasonable to ship on that path for now? If AccessoryAccess isn't available to Developer ID apps, I'd still welcome guidance on a supported way, such as com.apple.vm.device-access. I'm happy to share my sample project or logs. Thank you, Allison Meloy
Replies
1
Boosts
0
Views
123
Activity
6d