[RN-IAP] [getReceiptDataIOS] Failed: Error: Error Domain=com.margelo.nitro.rniap Code=-1

[leineveber]

Hi!
Just migrated from version 12 to 14.7.3 version
Previously we've used on start our application function to get receipts like so:

const receipt = await getReceiptIOS({ forceRefresh: false }).catch(() => null);

after the migration, getReceiptIOS always prompts dialog "Sign in with apple account" when used
tried to use getReceiptDataIOS, it triggers an error shown in the title of issue. Error code is "receipt-failed"

what's interesting I get this error on install and open, but for some reason after some actions which i havent figured out yet the error is not triggering anymore. but on reinstall i get it again

[gitdogdev]

@leineveber ## Analysis

You've hit a known StoreKit 2 behavior in v14.7.3. The receipt-failed error (ErrorCode.ReceiptFailed) occurs because:

Root Cause

iOS receipts in StoreKit 2 are cumulative — they contain ALL app transactions, not just the latest one. After purchase/app install, the receipt may be temporarily unavailable from the App Store, triggering the error.

Why It Works After Some Actions

Once StoreKit syncs with Apple's servers (which happens during various app interactions), the receipt becomes available.

---

Migration Issues from v12→v14

Your v12 code:

// v12 - Direct receipt access
let receiptURL = Bundle.main.appStoreReceiptURL
let receiptData = try Data(contentsOf: receiptURL!)

Doesn't translate 1:1 to v14.7.3 because:

1. No direct file access — StoreKit 2 handles receipt management internally
2. Async operations required — Transaction.currentEntitlements is async
3. JWS format — Receipts are now JWT-like tokens, not PKCS#7 blobs

---

Recommended Fix

Option 1: Use StoreKit 2 Properly (Recommended)

import StoreKit

func verifyPurchase() async throws {
    // Get all verified transactions
    var entitlements: [VerificationResult<Transaction>] = []
    
    for await result in Transaction.currentEntitlements {
        entitlements.append(result)
    }
    
    // Check if any are verified
    let verified = entitlements.compactMap { result -> Transaction? in
        if case .verified(let transaction) = result {
            return transaction
        }
        return nil
    }
    
    guard !verified.isEmpty else {
        throw PurchaseError.noVerifiedTransactions
    }
    
    print("✅ Verified transactions: \(verified.count)")
}

Option 2: Delay Receipt Check (Temporary Workaround)

func checkReceiptWithRetry(maxAttempts: Int = 3) async throws {
    var lastError: Error?
    
    for attempt in 1...maxAttempts {
        do {
            let receipt = try await SKReceiptRefreshRequest().receiptsData()
            return receipt
        } catch {
            lastError = error
            if attempt < maxAttempts {
                try await Task.sleep(nanoseconds: UInt64(attempt) * 1_000_000_000)
            }
        }
    }
    
    throw lastError ?? NSError(domain: "ReceiptError", code: -1)
}

Option 3: Request Fresh Receipt Explicitly

import StoreKit

func refreshReceiptIfNeeded() async throws {
    do {
        try await AppStore.sync()
        // Receipt should now be available
    } catch {
        print("⚠️ Sync failed: \(error)")
        throw error
    }
}

---

v14.7.3 Specific Workarounds

Add this to your app initialization:

@main
struct MyApp: App {
    var body: some Scene {
        WindowGroup {
            ContentView()
                .task {
                    // Force StoreKit sync on launch
                    do {
                        try await AppStore.sync()
                    } catch {
                        print("Initial sync failed: \(error)")
                    }
                }
        }
    }
}

For background receipt checks:

func setupReceiptObserver() {
    Task {
        for await result in Transaction.updates {
            if case .verified(let transaction) = result {
                await transaction.finish()
                // Receipt now updated
            }
        }
    }
}

---

Prevention Checklist

• Remove direct Bundle.main.appStoreReceiptURL calls
• Use Transaction.currentEntitlements instead
• Call AppStore.sync() after critical events (app launch, resume)
• Implement exponential backoff for receipt checks
• Test on real device + sandbox (simulator has different behavior)
• Update to latest StoreKit 2 patch if available

---

Known Issues (v14.7.3)

Issue	Workaround
Receipt unavailable immediately after purchase	Wait 1-3 seconds, then retry
ReceiptFailed in sandbox	Refresh receipt via AppStore.sync()
Receipt stale after app update	Call sync in @main app initializer

Would you like specific code for your exact use case?

---

🤖 Generated by gitdog.dev · Have more questions? Tag @gitdog and let me know!

[leineveber]

I think I figured it out. I stopped receiving the error after a purchase. And relogging to different acc throws the error as in new account there are no purchases. We use that receipt to let users login to their accounts, we have a sync between receipt and user in our db. I think I'll just silence that error.

Another problem is in v12 version "Purchase" contained "transactionReceipt" which we used on our backend. The problem is how to receive it now. I think "getReceiptDataIOS" returns back needed information but at the moment of purchaseUpdatedListener there is still no purchase so I get nothing

[hyochan]

@leineveber We now have new apis to validate in Storekit2.

• verifyPurchase: https://hyochan.github.io/react-native-iap/docs/api/methods/unified-apis?_highlight=verifypurchase#verifypurchase

• verifyPurchaseWithProvider: https://hyochan.github.io/react-native-iap/docs/api/methods/unified-apis?_highlight=verifypurchase#verifypurchasewithprovider

[leineveber]

@hyochan I think I got it, thanks!

just to be sure, about "getReceiptIOS / getReceiptDataIOS"

is it a bug that getReceiptIOS always triggers "Sign in to Apple account" popup?
and is it intended that getReceiptDataIOS triggers an error without purchases?

[leineveber]

  const verifyResult = await verifyPurchase({
        apple: {
          sku: purchase.productId,
        },
      });

@hyochan could you help identify the root case of that error while validating purchase from purchaseUpdateListener?

[leineveber]

@hyochan please let me know if it's a bug from my side & incorrect API usage / from your side and I should wait for a fix

[hyochan]

@leineveber Thanks for the detailed feedback. Let me clarify both behaviors:

1. getReceiptIOS prompting Apple ID sign-in

This is expected StoreKit 2 behavior, not a bug. In v14, getReceiptIOS calls AppStore.sync() internally (see RnIapHelper.swift:325-340) which triggers Apple's authentication flow. This was also the case with StoreKit 1's SKReceiptRefreshRequest.

If you want to avoid the sign-in prompt, use getReceiptDataIOS instead—it reads the local receipt without forcing a refresh.

2. getReceiptDataIOS returning error when no purchases exist

This is also expected behavior. On iOS, the App Store receipt file (StoreKit/receipt) doesn't exist until the user makes their first purchase or restores purchases. When you call getReceiptDataIOS on a fresh install with no purchase history, there's literally no receipt file to read—hence the receipt-failed error.

This is a fundamental StoreKit 2 design change: receipts are no longer the primary way to verify entitlements.

Recommended Migration Approach

Instead of relying on receipt-based validation (v12 pattern), use transaction-based validation with StoreKit 2:

import { 
  getAvailablePurchases, 
  getActiveSubscriptions,
  verifyPurchaseWithProvider  // Recommended
} from 'react-native-iap';

// Option 1: Check current entitlements
const purchases = await getAvailablePurchases();
// purchases contains all active entitlements

// Option 2: For subscriptions specifically
const subscriptions = await getActiveSubscriptions(['your.subscription.id']);

// Option 3: Verify with IAPKit (recommended for backend sync)
const result = await verifyPurchaseWithProvider({
  provider: 'iapkit',
  iapkit: {
    apple: { jws: purchase.purchaseToken },
  },
});

StoreKit 2 fundamentally shifted from receipt-based to transaction-based validation. Instead of a single receipt file, each transaction now has its own JWS (JSON Web Signature) that can be verified independently. The purchase.purchaseToken field contains this JWS.

For backend synchronization, you can:

Use verifyPurchaseWithProvider with IAPKit (no server setup needed)
Use validateReceipt with a specific SKU to get the JWS for that product
Send the JWS to your server and verify it using Apple's App Store Server API
See our Subscription Validation guide for detailed examples.

Let me know if you need help migrating your specific use case!

[leineveber]

@hyochan thanks for the answer!
I think next week we will continue migration on our side and I'll let you know if any help needed, thanks in advance!

[lachtos]

  const verifyResult = await verifyPurchase({
        apple: {
          sku: purchase.productId,
        },
      });

@hyochan could you help identify the root case of that error while validating purchase from purchaseUpdateListener?

@leineveber Have you found a solution for this error? (Error: RnIap.validateReceipt(...): Value is null, expected an Object)
I am facing the same issue, verifyPurchase doesn't seem to work.

[leineveber]

@lachtos I guess that the problem is at that moment of time we dont have a receipt
Solution is to migrate, as suggested by @hyochan, to transaction-based validation approach
Unfortunately, currently we're working on more important tasks so from my side that's still not migrated so cannot help on migration