missingReceiptFileError (error code 9): Missing receipt file

• StoreKit 1 restore or sync: the receipt fetcher returned no data, so the SDK completes with this error instead of posting anything (PurchasesOrchestrator.swift). RevenueCat describes it as no receipt file available on the device (RevenueCat error list).
• A device with no purchase history, which is common on a fresh install, a new sandbox account or a simulator. Apple exposes the receipt location as Bundle.appStoreReceiptURL, and the file may not exist yet.
• StoreKit 1 promotional offers: the SDK needs an existing receipt. With none, it returns ineligibleError and carries this error as the underlying error.
• The app forces StoreKit 1. The SDK's default is StoreKit 2, which reads signed transactions and needs no receipt file.
• The Android SDK has no receipt file, so Android never raises this error even though its enum lists it.

• Retrying right away will not help. Retry after a purchase or after the customer signs in to the store account.
• Show "We could not find any purchases on this device", not a failure message. For a new customer this is the normal answer.
• Do not grant access. There is nothing to verify.

// Swift
do {
  let result = try await Purchases.shared.purchase(package: package)
} catch let error as ErrorCode where error == .missingReceiptFileError {
  // handle missing receipt file
}

// Kotlin
if (error.code == PurchasesErrorCode.MissingReceiptFileError) { /* ... */ }

On RevenueDot: RevenueDot never sees this error, because the SDK raises it on the device before it sends a request. RevenueDot verifies StoreKit 2 signed transactions directly, and it needs the app's In-App Purchase key only for StoreKit 1 receipts.