Posts under App & System Services topic

Post

Replies

Boosts

Views

Activity

Tap To Pay Account Not Linked Issue
I am currently having issues getting tap to pay to work locally for development. I have: the tap to pay development entitlement a verified test device a test sandbox user tap to pay / NFC / app apptest capabilities the correct provisioning profile We are currently working a payment service provider NMI to support tap to pay. Part of that process has been getting entitlements, and we now have the developer entitlement for tap to pay. We are having an issue with an "account not linked" error. We have been told by NMI this is an issue on Apple's side since we have the correct provisioning profile, capabilities, and entitlements set up for our company. This issue is when using a sandbox account. When I use a developer account I get an "invalid apple account" issue. Any combination of user / provisioning profile / and capabilities that I have tried have not produced better results. Versions: IOS version is 26.6 and xcode is also 26.6. I have followed these steps: https://developer.apple.com/forums/thread/775784 here is my feedback assistant ID which contains my sys logs and a video. FB24822720
1
1
386
1d
Apple iCloud Log TimeZone Verification
Hello, I'm using some of the data from apple icloud logs and hoping someone can help from the Apple community. When an app is autimatically updated there is a column called 'Activity Date' in the 'App-Book Re-download and Update History.csv' log file. Can you confirm the timezone? Here is an example date: 2025-02-02T02:13:40. Thank you!
2
0
109
1d
iOS 27: domain-bound SMS one-time codes are not offered in an associated app ("Could not fetch application record"), worked on iOS 26.6 and 18
Since iOS 27.0, domain-bound SMS one-time codes are no longer offered above the keyboard in our app, where the code is entered on a web page in a WKWebView, although the app is associated with the domain through webcredentials. The same SMS is offered in Safari on the same device, and it is offered in our app on iOS 26.6 and iOS 18. SMS format (last line per the domain-bound code format): Your verification code is: 123456 @app.example.com #123456Setup Several builds of the same app with different bundle IDs (App Store, internal, development), all under one team Entitlement com.apple.developer.associated-domains: webcredentials:app.example.com (plus two more environments of the same domain) AASA at https://app.example.com/.well-known/apple-app-site-association: 200, application/json, no redirect, same content on app-site-association.cdn-apple.com: {"webcredentials":{"apps":["TEAMID.com.example.app","TEAMID.com.example.app.internal","TEAMID.com.example.app.dev"]}} The code field is an <input type="tel" autocomplete="one-time-code"> in a WKWebView showing a page on that domain. We also tested a native field with the one-time-code content type (the app is built with Flutter; the field is a Flutter TextField with the one-time-code autofill hint). Steps Open the verification page in the app and focus the code field. Receive the SMS above. Expected: the code is offered in the QuickType bar, as it is in Safari on the same domain and as it is in our app on iOS 26.6 and iOS 18. Actual: nothing is offered. The keyboard log: kbd Received verification code from Messages kbd One Time Code field has been entered. kbd Retrieving Current One-Time Codes for App kbd Current verification code is domain-bound to <mask.hash: '…'>. kbd Domain-bound verification code is NOT valid for app <mask.hash: 'X'>. E kbd Could not fetch application record for application identifier: <mask.hash: 'X'>. kbd Returning 0 available one-time codesWhat we checked swcd downloads the AASA for all domains without errors after a reinstall. The installed app's entitlements (read from the device) contain the expected application-identifier and associated domains; the profile is validated. The failure is the same in the WKWebView field and in a native one-time-code field, in the App Store build, a distribution-signed internal build and a development build, and in an older app version that used to work. The masked application identifier in the log (X above) is the same for two builds with different bundle IDs, so the lookup does not seem to use the app's bundle ID. All our builds share CFBundleExecutable = Runner (the Flutter default) and the same CFBundleName. The same app build and the same SMS work on iOS 26.6 and iOS 18.x, so the change happened between iOS 26.6 and 27.0. An SMS without the @domain #code line is offered in the app on iOS 27 (Returning 1 available one-time code), although Could not fetch application record is still logged. Questions Is this a known iOS 27 regression, or is there a new requirement for apps to receive domain-bound codes? What application identifier does the keyboard use for this lookup, and can anything in the app's configuration (for example the executable name) affect it? Device: iPhone 17 Pro Max, iOS 27.0
8
3
997
1d
Removing File Provider domains when a Mac App Store app is deleted
My Mac App Store apps use NSFileProviderReplicatedExtension, and users keep asking how to remove the folder in ~/Library/CloudStorage after deleting the app. Deleting the app leaves the domain registered and the folder in place. fileproviderctl dump shows the domain as "extension not found", and on my own Mac one such domain had survived for five months. As far as I can tell there is no supported way for the developer to clean this up: A sandboxed Mac App Store app cannot run code when it is deleted. NSFileProviderManager.remove(_:mode:) and removeAllDomains only work while the app is installed. fileproviderctl has no command to remove a domain. invalidate() is called when the extension is turned off in System Settings, but also on routine teardown, so it cannot drive cleanup. The one way out I have found is manual. Open the leftover folder in Finder, which says "The application "X" could not be found", and click Delete "X"… in the upper right corner. That removes both the domain and the folder, but users rarely find it on their own. Is there a mechanism I have missed, such as an Info.plist key or a system behavior, that removes a deleted app's domains automatically? If not, the best I can do seems to be an in-app "Remove from Finder" command that users have to run before deleting the app. I have filed FB25610224 asking for the system to remove a deleted app's domains, keeping unsynced changes the way .preserveDirtyUserData does.
1
0
64
2d
Sandbox: CONSUMPTION_REQUEST received but REFUND / REFUND_DECLINED never sent (auto-renewable subscription)
We are testing refunds for an auto-renewable subscription in the Sandbox environment using Transaction.beginRefundRequest(in:), following "Testing refund requests". Our server receives CONSUMPTION_REQUEST, but a REFUND or REFUND_DECLINED notification never follows. What we did (4 transactions, Nov 16, 2026) Purchased a monthly subscription with sandbox renewal rates of 1 hour, 30 minutes and 5 minutes, then turned off auto-renew. Submitted the refund sheet: one request with a standard reason; others with Issue = Other and text GRANT_PRORATED. We also used a second sandbox account. For one transaction, we called Send Consumption Information v2 within 5 minutes of the CONSUMPTION_REQUEST. The body was customerConsented: true, deliveryStatus: DELIVERED, sampleContentProvided: false, refundPreference: GRANT_PRORATED. The API returned 202 Accepted. What we see CONSUMPTION_REQUEST arrives 1–2 minutes after the refund sheet is submitted. Our server returns HTTP 200, and Get Notification History shows the send attempt as SUCCESS. No REFUND or REFUND_DECLINED arrived. Get Refund History v2 is empty, Get Transaction Info shows no revocationDate, and Get Notification History has no refund notification. All other sandbox notifications are delivered within a second: SUBSCRIBED, DID_CHANGE_RENEWAL_STATUS, EXPIRED. In production, REFUND, REFUND_DECLINED and REFUND_REVERSED are delivered normally for the same app. Sandbox transaction IDs 2000001266241009, 2000001266277405, 2000001266288964, 2000001266312137 Feedback: FB25595203 Questions Is there a known issue with Sandbox not deciding refund requests for auto-renewable subscriptions after CONSUMPTION_REQUEST? Is there a supported way to receive a real REFUND notification in Sandbox for end-to-end server testing? Thank you.
0
0
63
2d
MapKit JS token returns 401 only for mainland China while Apple's official sample works
Hello Apple engineers, Feedback Assistant report: FB25612837 (submitted under our developer team). We are investigating a production Web MapKit JS authorization failure. Our native iOS App works normally; this report concerns Web MapKit JS only. Observed on 14 November 2026: Our portal-generated MapKit JS token returned HTTP 401 for mainland-China bootstrap authorization and HTTP 200 for US authorization. Apple's official embedded-map example worked in the same browser and network, returning countryCode CN and displaying Amap attribution. A minimal page using SDK 6.1.205 on our production Web domain also returned 401. SDK 5.81.72 had the same result. Exact-domain, wildcard-domain, expiring, and temporarily unrestricted diagnostic tokens produced the same China-only failure. The unrestricted token was revoked immediately after the test and was never deployed. Rechecked on 17 November 2026: The locally configured production token, whose hash matches the token inspected in production on 14 November, still returns HTTP 401 with {"error":{"message":"Not Authorized","details":[]}}. It uses ES256, scope mapkit_js, and an origin matching our Web domain pattern. It is not expired and has no duplicate header or payload claims. Separately configured root-domain MapKit JS tokens also return 401 when tested with their matching origin. These 17 November probes used locally configured tokens; the authenticated production token value was not freshly read back that day. We found matching reports: https://developer.apple.com/forums/thread/766180 https://developer.apple.com/forums/thread/748764 https://developer.apple.com/forums/thread/684701 We checked the duplicate-claims fix described here and ruled it out for our configured token: https://developer.apple.com/forums/thread/113670 Questions: Is any additional team provisioning or authorization required for the mainland-China MapKit JS service? Can regional validation treat portal-generated tokens differently, despite the same token being accepted by another region? Is there a supported corrective configuration we can apply? We have not found one in the current Maps token documentation. Developer Support case 30000015236904 directed us to the forums. We can provide account-specific details privately through Feedback Assistant. This public question intentionally omits tokens, private keys, account identifiers, customer data, and production logs.
0
0
50
2d
File Handle Exhaustion Issue with com.apple.Virtualization.VirtualMachine in VZ Environment
We are currently utilizing VZ with Lima (details: Lima VM and VZ) for our development environment. However, we're encountering a critical issue with the com.apple.Virtualization.VirtualMachine process leading to open file handle exhaustion. When mounting our programming languages dependency cache folder (Which can have a lot of files) into the VZ VM, we encounter an operating system error related to open file limits: /gomodcache/github.com/go-git/go-git/v5@v5.4.2/plumbing/object/patch.go:14:2: open /gomodcache/github.com/go-git/go-git/v5@v5.4.2/plumbing/format/diff/unified_encoder.go: too many open files in system Further investigation revealed an abnormally high number of open files associated with the com.apple.Virtualization.VirtualMachine process. A significant portion of these files are not actively used but remain open. Example Case: A file (/Users/rcurrah/test.txt) created on the Mac host and listed (ls) in the VM remains open even 20 minutes later, as evidenced by the following command output: ❯ lsof | grep 11208 | grep test.txt COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME com.apple 11208 rcurrah 4823r REG 1,13 0 46200882 /Users/rcurrah/test.txt Steps to Reproduce the Issue: To reproduce the file handle exhaustion follow the below steps. This process will create a large number of files on the Mac host, listing them on the VZ VM, and then verifying their open status using lsof. Setup the VZ Environment with Sharing: Create a VZ VM with your home directory shared to the VM. Create a Test Directory on the Mac Host: Create a new directory on your Mac host, e.g., mkdir ~/test-file-exhaustion. Generate a Large Number of Files: Navigate to the created directory: cd ~/test-file-exhaustion. Use a loop to create a large number of files, e.g., for i in {1..10000}; do touch "file_${i}.txt"; done. This will create 10,000 files named file_1.txt, file_2.txt, etc. List Files in the VM: Access the VZ VM shell. Navigate to the mounted directory and list the files using the ls command, e.g., ls /path/to/mounted/test-file-exhaustion. Check Open Files on Mac Host: Exit the VM and return to your Mac host terminal. Use the lsof command to check for open files related to the com.apple.Virtualization.VirtualMachine process: lsof | grep "$(pgrep com.apple.Virtualization.VirtualMachine)" | grep 'test-file-exhaustion' | wc -l. Document the Output: Record the output of the lsof command. Note the number of open files. Verify File Closure (or Lack Thereof): After a certain period, e.g., 20 minutes, repeat the lsof command to see if the files are still open, indicating that they haven’t been closed properly by the process. Given these observations, we have a couple of questions: Is this behavior of com.apple.Virtualization.VirtualMachine retaining open file handles a known issue or a bug? Should VZ be managing the closure of these file handles more efficiently, especially when they are no longer in use? This issue is impacting our development workflow significantly. Any guidance or insights on resolving this would be highly appreciated. Thank you for your attention to this matter. Best regards, Ryan
16
1
2.6k
2d
Account deletion flow for an app with user accounts
Title: Account deletion flow for an app with user accounts Post: Hello, Our app supports account creation and sign-in using Apple, Google, Facebook, and email. App Review cited Guideline 5.1.1(v) because users could not initiate account deletion in the app. We understand that users must be able to initiate deletion within the app, and that a confirmation step is allowed. We are planning to add a clearly labeled “Delete Account” option in the account settings, followed by a confirmation screen and a deletion process that removes the user’s account and associated personal data from our systems. We would appreciate advice on the implementation details: Is it generally acceptable for the in-app option to open a dedicated web page where the user can complete the deletion process, provided the link goes directly to that page? Does the deletion need to be completed immediately, or can processing take a short, clearly disclosed period? If a user has posted content, should that content be deleted, anonymized, or handled separately when their account is deleted? We are reviewing the App Review Guidelines and understand that this post cannot provide pre-approval of our app. We are looking for implementation guidance from developers who have handled similar requirements. Thank you.
0
0
26
2d
TipKit crash on launch (iOS 27.2) — swift_unexpectedError with no app frames
We're seeing a crash from a user on iOS 27.2 that we can't reproduce locally. The crash shows swift_unexpectedError on the main thread with no application frames between the concurrency runtime and the crash. Our app binary hasn't changed since summer 2025 but this user started experiencing the crash for the first time about a week ago. Thread 0 (crashed): Thread 0 Crashed (com.apple.main-thread): 0 libswiftCore.dylib _assertionFailure(_:_:file:line:flags:) 1 libswiftCore.dylib swift_unexpectedError 2 libswift_Concurrency.dylib swift::runJobInEstablishedExecutorContext(...) 3 libswift_Concurrency.dylib swift_job_runImpl(...) 4 libdispatch.dylib _dispatch_main_queue_drain 5 libdispatch.dylib _dispatch_main_queue_callback_4CF 6 CoreFoundation __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ ... (standard UIApplicationMain run loop)The crash occurs 0.45 seconds after launch. The only other active thread at the time of the crash is Thread 6, which shows TipKit driving SwiftData/CoreData work: Thread 6: Thread 6 name: Dispatch queue: NSManagedObjectContext 0x110f99500 0 CoreFoundation CFBasicHashGetPtrIndex 1 CoreFoundation CFBasicHashCreate 2 CoreFoundation CFDictionaryCreateMutable 3 CoreData _PFCMT_SetValue 4 CoreData -[NSManagedObjectContext _retainedObjectWithID:optionalHandler:withInlineStorage:] 5 CoreData -[NSManagedObjectContext objectWithID:] 6 SwiftData (SwiftData + 373080) 7 SwiftData (SwiftData + 281172) 8 SwiftData (SwiftData + 359244) 9 SwiftData (SwiftData + 355724) 10 SwiftData (SwiftData + 359208) 11 CoreData thunk for @callee_guaranteed () -> (@out A, @error @owned Error) 12 CoreData partial apply for thunk for @callee_guaranteed () -> (@out A, @error @owned Error) 13 CoreData NSManagedObjectContext._rethrowsHelper_performAndWait(...) 14 CoreData thunk for @callee_guaranteed @Sendable () -> () 15 CoreData thunk for @escaping @callee_guaranteed @Sendable () -> () 16 CoreData developerSubmittedBlockToNSManagedObjectContextPerform 17 libdispatch.dylib _dispatch_client_callout 18 libdispatch.dylib _dispatch_lane_barrier_sync_invoke_and_complete 19 CoreData -[NSManagedObjectContext performBlockAndWait:] 20 CoreData NSManagedObjectContext.performAndWait(_:) 21 SwiftData (SwiftData + 258584) 22 SwiftData (SwiftData + 257920) 23 SwiftData (SwiftData + 326480) 24 SwiftData (SwiftData + 259564) 25 SwiftData (SwiftData + 56292) 26 SwiftData (SwiftData + 385736) 27 TipKitCore (TipKitCore + 202216) 28 TipKitCore (TipKitCore + 128232) 29 TipKitCore (TipKitCore + 124104) 30 TipKitCore (TipKitCore + 130048) 31 TipKitCore (TipKitCore + 241553) 32 TipKitCore (TipKitCore + 152365) 33 TipKitCore (TipKitCore + 134441) 34 TipKitCore (TipKitCore + 152629) 35 TipKitCore (TipKitCore + 134233) 36 TipKitCore (TipKitCore + 134441) 37 TipKitCore (TipKitCore + 138237) 38 TipKitCore (TipKitCore + 134233) 39 libswift_Concurrency completeTask(swift::AsyncContext*, swift::SwiftError*)All other threads are idle. Context: We call try? Tips.configure([.displayFrequency(.hourly)]) early in our startup sequence. The try? should swallow any error from configure itself, but I'm not sure if TipKit spawns its own internal async tasks. Our app uses UIKit (not SwiftUI App lifecycle). We do not use SwiftData directly — any SwiftData/CoreData frames come from system frameworks. The binary hasn't changed since summer 2025, so this appears to be an OS-level regression on iOS 27.x. We cannot reproduce locally. Questions: Is there a way to get async backtraces in crash reports from the field, or is this only possible under the debugger? If TipKit spawns an internal Task that throws into a non-throwing context, would that produce exactly this crash pattern — swift_unexpectedError on the main thread with no third-party frames? Are there known issues with TipKit's internal SwiftData tasks crashing on iOS 27.x? Any guidance on narrowing this down without a local repro would be appreciated.
7
0
230
2d
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
28
2d
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
250
2d
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
190
2d
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
131
2d
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
64
2d
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
379
3d
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
131
3d
Tap To Pay Account Not Linked Issue
I am currently having issues getting tap to pay to work locally for development. I have: the tap to pay development entitlement a verified test device a test sandbox user tap to pay / NFC / app apptest capabilities the correct provisioning profile We are currently working a payment service provider NMI to support tap to pay. Part of that process has been getting entitlements, and we now have the developer entitlement for tap to pay. We are having an issue with an "account not linked" error. We have been told by NMI this is an issue on Apple's side since we have the correct provisioning profile, capabilities, and entitlements set up for our company. This issue is when using a sandbox account. When I use a developer account I get an "invalid apple account" issue. Any combination of user / provisioning profile / and capabilities that I have tried have not produced better results. Versions: IOS version is 26.6 and xcode is also 26.6. I have followed these steps: https://developer.apple.com/forums/thread/775784 here is my feedback assistant ID which contains my sys logs and a video. FB24822720
Replies
1
Boosts
1
Views
386
Activity
1d
Apple iCloud Log TimeZone Verification
Hello, I'm using some of the data from apple icloud logs and hoping someone can help from the Apple community. When an app is autimatically updated there is a column called 'Activity Date' in the 'App-Book Re-download and Update History.csv' log file. Can you confirm the timezone? Here is an example date: 2025-02-02T02:13:40. Thank you!
Replies
2
Boosts
0
Views
109
Activity
1d
iOS 27: domain-bound SMS one-time codes are not offered in an associated app ("Could not fetch application record"), worked on iOS 26.6 and 18
Since iOS 27.0, domain-bound SMS one-time codes are no longer offered above the keyboard in our app, where the code is entered on a web page in a WKWebView, although the app is associated with the domain through webcredentials. The same SMS is offered in Safari on the same device, and it is offered in our app on iOS 26.6 and iOS 18. SMS format (last line per the domain-bound code format): Your verification code is: 123456 @app.example.com #123456Setup Several builds of the same app with different bundle IDs (App Store, internal, development), all under one team Entitlement com.apple.developer.associated-domains: webcredentials:app.example.com (plus two more environments of the same domain) AASA at https://app.example.com/.well-known/apple-app-site-association: 200, application/json, no redirect, same content on app-site-association.cdn-apple.com: {"webcredentials":{"apps":["TEAMID.com.example.app","TEAMID.com.example.app.internal","TEAMID.com.example.app.dev"]}} The code field is an <input type="tel" autocomplete="one-time-code"> in a WKWebView showing a page on that domain. We also tested a native field with the one-time-code content type (the app is built with Flutter; the field is a Flutter TextField with the one-time-code autofill hint). Steps Open the verification page in the app and focus the code field. Receive the SMS above. Expected: the code is offered in the QuickType bar, as it is in Safari on the same domain and as it is in our app on iOS 26.6 and iOS 18. Actual: nothing is offered. The keyboard log: kbd Received verification code from Messages kbd One Time Code field has been entered. kbd Retrieving Current One-Time Codes for App kbd Current verification code is domain-bound to <mask.hash: '…'>. kbd Domain-bound verification code is NOT valid for app <mask.hash: 'X'>. E kbd Could not fetch application record for application identifier: <mask.hash: 'X'>. kbd Returning 0 available one-time codesWhat we checked swcd downloads the AASA for all domains without errors after a reinstall. The installed app's entitlements (read from the device) contain the expected application-identifier and associated domains; the profile is validated. The failure is the same in the WKWebView field and in a native one-time-code field, in the App Store build, a distribution-signed internal build and a development build, and in an older app version that used to work. The masked application identifier in the log (X above) is the same for two builds with different bundle IDs, so the lookup does not seem to use the app's bundle ID. All our builds share CFBundleExecutable = Runner (the Flutter default) and the same CFBundleName. The same app build and the same SMS work on iOS 26.6 and iOS 18.x, so the change happened between iOS 26.6 and 27.0. An SMS without the @domain #code line is offered in the app on iOS 27 (Returning 1 available one-time code), although Could not fetch application record is still logged. Questions Is this a known iOS 27 regression, or is there a new requirement for apps to receive domain-bound codes? What application identifier does the keyboard use for this lookup, and can anything in the app's configuration (for example the executable name) affect it? Device: iPhone 17 Pro Max, iOS 27.0
Replies
8
Boosts
3
Views
997
Activity
1d
Removing File Provider domains when a Mac App Store app is deleted
My Mac App Store apps use NSFileProviderReplicatedExtension, and users keep asking how to remove the folder in ~/Library/CloudStorage after deleting the app. Deleting the app leaves the domain registered and the folder in place. fileproviderctl dump shows the domain as "extension not found", and on my own Mac one such domain had survived for five months. As far as I can tell there is no supported way for the developer to clean this up: A sandboxed Mac App Store app cannot run code when it is deleted. NSFileProviderManager.remove(_:mode:) and removeAllDomains only work while the app is installed. fileproviderctl has no command to remove a domain. invalidate() is called when the extension is turned off in System Settings, but also on routine teardown, so it cannot drive cleanup. The one way out I have found is manual. Open the leftover folder in Finder, which says "The application "X" could not be found", and click Delete "X"… in the upper right corner. That removes both the domain and the folder, but users rarely find it on their own. Is there a mechanism I have missed, such as an Info.plist key or a system behavior, that removes a deleted app's domains automatically? If not, the best I can do seems to be an in-app "Remove from Finder" command that users have to run before deleting the app. I have filed FB25610224 asking for the system to remove a deleted app's domains, keeping unsynced changes the way .preserveDirtyUserData does.
Replies
1
Boosts
0
Views
64
Activity
2d
Sandbox: CONSUMPTION_REQUEST received but REFUND / REFUND_DECLINED never sent (auto-renewable subscription)
We are testing refunds for an auto-renewable subscription in the Sandbox environment using Transaction.beginRefundRequest(in:), following "Testing refund requests". Our server receives CONSUMPTION_REQUEST, but a REFUND or REFUND_DECLINED notification never follows. What we did (4 transactions, Nov 16, 2026) Purchased a monthly subscription with sandbox renewal rates of 1 hour, 30 minutes and 5 minutes, then turned off auto-renew. Submitted the refund sheet: one request with a standard reason; others with Issue = Other and text GRANT_PRORATED. We also used a second sandbox account. For one transaction, we called Send Consumption Information v2 within 5 minutes of the CONSUMPTION_REQUEST. The body was customerConsented: true, deliveryStatus: DELIVERED, sampleContentProvided: false, refundPreference: GRANT_PRORATED. The API returned 202 Accepted. What we see CONSUMPTION_REQUEST arrives 1–2 minutes after the refund sheet is submitted. Our server returns HTTP 200, and Get Notification History shows the send attempt as SUCCESS. No REFUND or REFUND_DECLINED arrived. Get Refund History v2 is empty, Get Transaction Info shows no revocationDate, and Get Notification History has no refund notification. All other sandbox notifications are delivered within a second: SUBSCRIBED, DID_CHANGE_RENEWAL_STATUS, EXPIRED. In production, REFUND, REFUND_DECLINED and REFUND_REVERSED are delivered normally for the same app. Sandbox transaction IDs 2000001266241009, 2000001266277405, 2000001266288964, 2000001266312137 Feedback: FB25595203 Questions Is there a known issue with Sandbox not deciding refund requests for auto-renewable subscriptions after CONSUMPTION_REQUEST? Is there a supported way to receive a real REFUND notification in Sandbox for end-to-end server testing? Thank you.
Replies
0
Boosts
0
Views
63
Activity
2d
MapKit JS token returns 401 only for mainland China while Apple's official sample works
Hello Apple engineers, Feedback Assistant report: FB25612837 (submitted under our developer team). We are investigating a production Web MapKit JS authorization failure. Our native iOS App works normally; this report concerns Web MapKit JS only. Observed on 14 November 2026: Our portal-generated MapKit JS token returned HTTP 401 for mainland-China bootstrap authorization and HTTP 200 for US authorization. Apple's official embedded-map example worked in the same browser and network, returning countryCode CN and displaying Amap attribution. A minimal page using SDK 6.1.205 on our production Web domain also returned 401. SDK 5.81.72 had the same result. Exact-domain, wildcard-domain, expiring, and temporarily unrestricted diagnostic tokens produced the same China-only failure. The unrestricted token was revoked immediately after the test and was never deployed. Rechecked on 17 November 2026: The locally configured production token, whose hash matches the token inspected in production on 14 November, still returns HTTP 401 with {"error":{"message":"Not Authorized","details":[]}}. It uses ES256, scope mapkit_js, and an origin matching our Web domain pattern. It is not expired and has no duplicate header or payload claims. Separately configured root-domain MapKit JS tokens also return 401 when tested with their matching origin. These 17 November probes used locally configured tokens; the authenticated production token value was not freshly read back that day. We found matching reports: https://developer.apple.com/forums/thread/766180 https://developer.apple.com/forums/thread/748764 https://developer.apple.com/forums/thread/684701 We checked the duplicate-claims fix described here and ruled it out for our configured token: https://developer.apple.com/forums/thread/113670 Questions: Is any additional team provisioning or authorization required for the mainland-China MapKit JS service? Can regional validation treat portal-generated tokens differently, despite the same token being accepted by another region? Is there a supported corrective configuration we can apply? We have not found one in the current Maps token documentation. Developer Support case 30000015236904 directed us to the forums. We can provide account-specific details privately through Feedback Assistant. This public question intentionally omits tokens, private keys, account identifiers, customer data, and production logs.
Replies
0
Boosts
0
Views
50
Activity
2d
File Handle Exhaustion Issue with com.apple.Virtualization.VirtualMachine in VZ Environment
We are currently utilizing VZ with Lima (details: Lima VM and VZ) for our development environment. However, we're encountering a critical issue with the com.apple.Virtualization.VirtualMachine process leading to open file handle exhaustion. When mounting our programming languages dependency cache folder (Which can have a lot of files) into the VZ VM, we encounter an operating system error related to open file limits: /gomodcache/github.com/go-git/go-git/v5@v5.4.2/plumbing/object/patch.go:14:2: open /gomodcache/github.com/go-git/go-git/v5@v5.4.2/plumbing/format/diff/unified_encoder.go: too many open files in system Further investigation revealed an abnormally high number of open files associated with the com.apple.Virtualization.VirtualMachine process. A significant portion of these files are not actively used but remain open. Example Case: A file (/Users/rcurrah/test.txt) created on the Mac host and listed (ls) in the VM remains open even 20 minutes later, as evidenced by the following command output: ❯ lsof | grep 11208 | grep test.txt COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME com.apple 11208 rcurrah 4823r REG 1,13 0 46200882 /Users/rcurrah/test.txt Steps to Reproduce the Issue: To reproduce the file handle exhaustion follow the below steps. This process will create a large number of files on the Mac host, listing them on the VZ VM, and then verifying their open status using lsof. Setup the VZ Environment with Sharing: Create a VZ VM with your home directory shared to the VM. Create a Test Directory on the Mac Host: Create a new directory on your Mac host, e.g., mkdir ~/test-file-exhaustion. Generate a Large Number of Files: Navigate to the created directory: cd ~/test-file-exhaustion. Use a loop to create a large number of files, e.g., for i in {1..10000}; do touch "file_${i}.txt"; done. This will create 10,000 files named file_1.txt, file_2.txt, etc. List Files in the VM: Access the VZ VM shell. Navigate to the mounted directory and list the files using the ls command, e.g., ls /path/to/mounted/test-file-exhaustion. Check Open Files on Mac Host: Exit the VM and return to your Mac host terminal. Use the lsof command to check for open files related to the com.apple.Virtualization.VirtualMachine process: lsof | grep "$(pgrep com.apple.Virtualization.VirtualMachine)" | grep 'test-file-exhaustion' | wc -l. Document the Output: Record the output of the lsof command. Note the number of open files. Verify File Closure (or Lack Thereof): After a certain period, e.g., 20 minutes, repeat the lsof command to see if the files are still open, indicating that they haven’t been closed properly by the process. Given these observations, we have a couple of questions: Is this behavior of com.apple.Virtualization.VirtualMachine retaining open file handles a known issue or a bug? Should VZ be managing the closure of these file handles more efficiently, especially when they are no longer in use? This issue is impacting our development workflow significantly. Any guidance or insights on resolving this would be highly appreciated. Thank you for your attention to this matter. Best regards, Ryan
Replies
16
Boosts
1
Views
2.6k
Activity
2d
Account deletion flow for an app with user accounts
Title: Account deletion flow for an app with user accounts Post: Hello, Our app supports account creation and sign-in using Apple, Google, Facebook, and email. App Review cited Guideline 5.1.1(v) because users could not initiate account deletion in the app. We understand that users must be able to initiate deletion within the app, and that a confirmation step is allowed. We are planning to add a clearly labeled “Delete Account” option in the account settings, followed by a confirmation screen and a deletion process that removes the user’s account and associated personal data from our systems. We would appreciate advice on the implementation details: Is it generally acceptable for the in-app option to open a dedicated web page where the user can complete the deletion process, provided the link goes directly to that page? Does the deletion need to be completed immediately, or can processing take a short, clearly disclosed period? If a user has posted content, should that content be deleted, anonymized, or handled separately when their account is deleted? We are reviewing the App Review Guidelines and understand that this post cannot provide pre-approval of our app. We are looking for implementation guidance from developers who have handled similar requirements. Thank you.
Replies
0
Boosts
0
Views
26
Activity
2d
TipKit crash on launch (iOS 27.2) — swift_unexpectedError with no app frames
We're seeing a crash from a user on iOS 27.2 that we can't reproduce locally. The crash shows swift_unexpectedError on the main thread with no application frames between the concurrency runtime and the crash. Our app binary hasn't changed since summer 2025 but this user started experiencing the crash for the first time about a week ago. Thread 0 (crashed): Thread 0 Crashed (com.apple.main-thread): 0 libswiftCore.dylib _assertionFailure(_:_:file:line:flags:) 1 libswiftCore.dylib swift_unexpectedError 2 libswift_Concurrency.dylib swift::runJobInEstablishedExecutorContext(...) 3 libswift_Concurrency.dylib swift_job_runImpl(...) 4 libdispatch.dylib _dispatch_main_queue_drain 5 libdispatch.dylib _dispatch_main_queue_callback_4CF 6 CoreFoundation __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ ... (standard UIApplicationMain run loop)The crash occurs 0.45 seconds after launch. The only other active thread at the time of the crash is Thread 6, which shows TipKit driving SwiftData/CoreData work: Thread 6: Thread 6 name: Dispatch queue: NSManagedObjectContext 0x110f99500 0 CoreFoundation CFBasicHashGetPtrIndex 1 CoreFoundation CFBasicHashCreate 2 CoreFoundation CFDictionaryCreateMutable 3 CoreData _PFCMT_SetValue 4 CoreData -[NSManagedObjectContext _retainedObjectWithID:optionalHandler:withInlineStorage:] 5 CoreData -[NSManagedObjectContext objectWithID:] 6 SwiftData (SwiftData + 373080) 7 SwiftData (SwiftData + 281172) 8 SwiftData (SwiftData + 359244) 9 SwiftData (SwiftData + 355724) 10 SwiftData (SwiftData + 359208) 11 CoreData thunk for @callee_guaranteed () -> (@out A, @error @owned Error) 12 CoreData partial apply for thunk for @callee_guaranteed () -> (@out A, @error @owned Error) 13 CoreData NSManagedObjectContext._rethrowsHelper_performAndWait(...) 14 CoreData thunk for @callee_guaranteed @Sendable () -> () 15 CoreData thunk for @escaping @callee_guaranteed @Sendable () -> () 16 CoreData developerSubmittedBlockToNSManagedObjectContextPerform 17 libdispatch.dylib _dispatch_client_callout 18 libdispatch.dylib _dispatch_lane_barrier_sync_invoke_and_complete 19 CoreData -[NSManagedObjectContext performBlockAndWait:] 20 CoreData NSManagedObjectContext.performAndWait(_:) 21 SwiftData (SwiftData + 258584) 22 SwiftData (SwiftData + 257920) 23 SwiftData (SwiftData + 326480) 24 SwiftData (SwiftData + 259564) 25 SwiftData (SwiftData + 56292) 26 SwiftData (SwiftData + 385736) 27 TipKitCore (TipKitCore + 202216) 28 TipKitCore (TipKitCore + 128232) 29 TipKitCore (TipKitCore + 124104) 30 TipKitCore (TipKitCore + 130048) 31 TipKitCore (TipKitCore + 241553) 32 TipKitCore (TipKitCore + 152365) 33 TipKitCore (TipKitCore + 134441) 34 TipKitCore (TipKitCore + 152629) 35 TipKitCore (TipKitCore + 134233) 36 TipKitCore (TipKitCore + 134441) 37 TipKitCore (TipKitCore + 138237) 38 TipKitCore (TipKitCore + 134233) 39 libswift_Concurrency completeTask(swift::AsyncContext*, swift::SwiftError*)All other threads are idle. Context: We call try? Tips.configure([.displayFrequency(.hourly)]) early in our startup sequence. The try? should swallow any error from configure itself, but I'm not sure if TipKit spawns its own internal async tasks. Our app uses UIKit (not SwiftUI App lifecycle). We do not use SwiftData directly — any SwiftData/CoreData frames come from system frameworks. The binary hasn't changed since summer 2025, so this appears to be an OS-level regression on iOS 27.x. We cannot reproduce locally. Questions: Is there a way to get async backtraces in crash reports from the field, or is this only possible under the debugger? If TipKit spawns an internal Task that throws into a non-throwing context, would that produce exactly this crash pattern — swift_unexpectedError on the main thread with no third-party frames? Are there known issues with TipKit's internal SwiftData tasks crashing on iOS 27.x? Any guidance on narrowing this down without a local repro would be appreciated.
Replies
7
Boosts
0
Views
230
Activity
2d
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
28
Activity
2d
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
55
Activity
2d
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
250
Activity
2d
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
190
Activity
2d
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
131
Activity
2d
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
64
Activity
2d
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
379
Activity
3d
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
131
Activity
3d