All packsApp Store MachinerySolve
storekit product.products for empty array paid agreement
Product.products(for:) returns nothing until paperwork is done
An empty array from Product.products(for:) usually means the Paid Applications agreement, banking, or tax forms aren't complete in App Store Connect -- not a code bug.
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?
Product.products(for:) silently returns an empty array whenever the Paid Applications agreement, banking information, or tax forms aren't fully complete in App Store Connect -- with no error message pointing at the actual cause. A developer whose StoreKit code is entirely correct spends hours debugging product-loading logic, re-checking product identifiers, and re-reading their own code, because nothing in Xcode or the API response indicates the real problem is an unrelated administrative form.
Why this one is easy to get wrong
An empty array from an API call reads as a code or configuration bug in the calling code -- wrong product identifier, wrong bundle id, a StoreKit configuration file issue -- and every one of those is a plausible, debuggable cause that an agent (or developer) would naturally investigate first. The actual cause lives entirely outside the codebase, in App Store Connect's business paperwork, which nothing in the client-side symptom points toward.
What you get instead
The onboarding documentation calls this out directly and first, before any debugging steps: an empty products array most commonly means the paid-agreement/banking/tax setup in App Store Connect isn't finished, and that's the first thing to check, not the code. Naming the actual cause up front is meant to save exactly the hours of unproductive code debugging this trap otherwise causes.
Source: LISTING.md, 'The five traps this pack pre-solves' — 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 →