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.

Update — November 17, 2026 (all times below are UTC+08:00)

I first noticed the acquisition-date failure on Sunday morning, November 15. I reproduced it again after reinstalling the App Store version of Freezon 1.1.2 (1) on my iPhone 17 Pro this morning. It has occurred on separate days; I cannot say it failed continuously between those observations.

At 10:23:04, AppTransaction.shared threw StoreKitError.unknown (NSError domain StoreKit.StoreKitError, code 2). Retries on the Pro page at 10:23:32, 10:23:34 and 10:23:39 failed as well. At the same time, the iPhone's live logs in macOS Console included these storekitd messages (excerpts):

AppTransaction throttled for error: StoreKitServiceError(... StoreKitServerError(rawValue: -2) ..., environment: Production, storefront: CHN)
Received error that does not have a corresponding StoreKit Error

I understand that -2 is an internal StoreKit error with no public meaning I can rely on. These messages do not establish a specific server failure or a wider outage.

Later, I reopened the app without tapping Restore, and launch-user Pro access appeared automatically. At 10:32:16, Console showed AppTransactionQuery, then “No AppTransaction for revision Optional(1)”, followed by CreateAppTransactionRequest with signIn: false and useBiometrics: false. The request ended at 10:32:22; another query appeared around 10:34.

I then confirmed that live Console capture was running and its entries were increasing before another App Store reinstall. At 11:17:56, the logs showed:

  • Production - AppTransactionQuery(... cached ... first)
  • No AppTransaction for revision Optional(1)
  • CreateAppTransactionRequest(... signIn: false, useBiometrics: false, client: com.zyiszy.PrivateVault Production, destination: app-receipt-create)

That query ended at 11:18:02, and another ran at 11:18:20–11:18:25. I did not see the earlier StoreKitServerError(-2) or throttling message during this capture. The app displayed launch-user Pro access again, without Restore or any account/password prompt. Despite the cached-query wording, the log also reports no AppTransaction for revision 1 and a create request.

These logs do not expose the verified AppTransaction fields or tell me which query updated the app's state. They do show that the app can recognize launch access without my explicitly restoring or entering a password, so my earlier recovery observation should not be read as proof that manual Restore is required.

This evidence is from the App Store app and live iPhone Console logs, not a sysdiagnose or a new Pro diagnostic export. I have not captured a sysdiagnose, installed a Debug build, or tested a newer OS/beta for this update. The app currently shows launch access.

Could the StoreKit team help interpret the internal -2/throttling in this case and explain why shared repeatedly fails before access later appears without explicit authentication? Which diagnostic profile or logs would help if it happens again?

I filed FB25605680 at the suggestion of DTS (Case-ID: 23550827) and added this evidence there as well.