All packsApp Store MachinerySolve
storekit 2 transaction.updates listener missed renewals
Forgetting the updates listener misses renewals, refunds, and offer codes
Transaction.updates delivers renewals, Ask to Buy approvals, cross-device purchases, and offer-code redemptions -- not just the purchase you just made. Skipping it misses all of them.
This is one of the things App Store Machinery already handles. Sell subscriptions and one-time unlocks in your iOS app, and get it through App Review.
Is this you?
A purchase flow that only reads the transaction StoreKit hands back from Product.purchase() correctly handles that one purchase, but misses everything that arrives afterward through a different path: subscription renewals, Ask to Buy parental approvals that complete later, purchases restored on another device, and offer-code redemptions specifically arrive through the Transaction.updates async stream, not the purchase() call's return value. An app without that listener running silently stops learning about any of these events.
Why this one is easy to get wrong
The purchase() call's return value looks like the complete answer to "did the purchase work" -- it returns a transaction, the transaction verifies, the code moves on. Nothing about that call signature hints that a second, separate, long-running listener is required to catch everything that isn't the immediate purchase itself; it's a StoreKit 2 architectural requirement that has to be known in advance, not inferred from any one API's shape.
What you get instead
Decision 9 has the app start the Transaction.updates listener in its init, before any UI renders -- explicitly documented as "the #1 StoreKit 2 bug" to forget. Offer-code redemption specifically is called out as arriving through this listener, not the purchase return path, which is exactly why the listener has to already be running before a user could possibly redeem a code from the paywall.
Source: ARCHITECTURE.md decision 9 — checkable in the pack you receive
How you actually use this
You don’t install a library or wire up an SDK. Your own coding agent builds the code in your project, and you keep it — no runtime dependency on us.
Step 1
Download and unzip
You get a folder: the docs that tell an agent what to build, a starting skeleton, and the test suite that decides when it's done.
Step 2
Open it in Claude Code or Cursor
Point your coding agent at the folder. Nothing to install, no account with us, no API key.
Step 3
Paste one prompt
The pack contains the exact prompt. Paste it as your first message and leave it alone — it works through the build itself, choosing a cheaper or stronger model per task.
Step 4
Run ./verify.sh
One command. It prints a pass or fail for every check. Green means the build is done — the same script we ran to produce the receipt on this page.
Typical build: about 21 minutes of your agent working, mostly unattended. Then you integrate the working module into your app the way you would any code you’d written yourself.
Why you can believe this
3 of 3 runs passedWe ran this pack from an empty folder 3 times and published exactly what happened — every check, the model, the token cost, the wall time. Not a testimonial, and not our opinion: the same verify.sh you run yourself. Read the full receipt →