@hyodotdev/openiap

Connect your app, paywall, commerce service, or data product to OpenIAP. Choose your role, then give the implementation brief to your coding assistant in your existing project. Use doctor to check local purchase configuration.

Requires Node.js 20 or later.

Start with your role

npx @hyodotdev/openiap                              # choose a role in your terminal
npx @hyodotdev/openiap init ./my-product --role experience
npx @hyodotdev/openiap doctor ./my-app --json

| Role | Connect | | ------------ | ----------------------------------------------------- | | app | Purchases to customer access | | experience | Paywalls and experiments to the app's purchase flow | | commerce | Verification and access through the Commerce Protocol | | data | Normalized events to analytics and automation |

The brief points your assistant to the matching implementation guide. Fill in the customer outcome, choose any missing product decisions, and review the running result. Run again for each role your product supplies.

Both commands only read local files. They do not install dependencies, change your project, contact a server, or invoke an AI. init prints a brief; your coding assistant performs the implementation when you give it that brief. For scripts, select a role explicitly with --role.

Severity

Error means the checkout proves it: two files disagree, or a value is wrong for its documented use. Errors exit 1.

Warning means the checkout suggests it but cannot settle it — Gradle can inject a manifest placeholder, a linked framework can supply a class, and no file records whether the app reads a given variable. Warnings exit 0.

A build for another store is settled but deliberate, so it is a warning too: the tool cannot know which device you are about to install on.

Both means the level depends on what the checkout shows. A malformed base URL is an error where something inlines the name it is assigned to, and a warning where nothing does; a missing scene delegate is an error when the Info.plist names the app's own module or no class at all, and a warning when the name could come from a linked framework.

What it finds

Most of these produce no error message that says what is actually wrong.

| Check | Level | What goes wrong without it | | ----------------------------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | android-store-flavor-mismatch | error | A half-finished regeneration links one store while the flags select another. | | android-store-flavor-conflict | error | Both store flags are true. Gradle also refuses this; the doctor sees it before a build. | | android-store-not-play | warning | The build targets Horizon or Amazon, so Play billing cannot connect on a Play device. | | android-horizon-app-id-missing | warning | Horizon is selected but no manifest declares an app id. | | iapkit-secret-key-in-client | error | A secret key is on a name that reaches the app bundle. | | iapkit-secret-key-in-env | warning | A secret key is in an env file on a name nothing here proves is inlined. | | iapkit-secret-key-in-config | warning | Executable app configuration contains a secret, but its presence in the app bundle is unproven. | | iapkit-env-missing-expo-prefix | warning | Expo inlines only EXPO_PUBLIC_ names, so the bare name reads as undefined. | | iapkit-env-unexpected-expo-prefix | warning | An EXPO_PUBLIC_ name is set where nothing inlines that prefix. | | iapkit-base-url-has-path | both | The base URL is not a bare origin; every SDK rejects a path, userinfo, a query or a fragment. | | iapkit-base-url-invalid | both | The base URL is not a URL. | | iapkit-base-url-scheme | both | The base URL is not http or https. | | ios-scene-delegate-missing | both | The Info.plist names a scene delegate the target lacks; the app opens to a black screen. Error when the plist names the app's own module or no class at all, warning when a linked framework could supply it. | | project-file-unreadable | error | A path could not be read, so nothing in it was checked. | | project-manifest-unreadable | error | package.json exists but will not parse, so framework detection read nothing. | | project-not-a-directory | error | The path given is not a readable directory. |

What it does not find

Dynamic app configuration is never executed. Secret literals in it stay warnings unless the file is a declared bundled asset. Reading an unprefixed environment variable during configuration also does not prove its value reaches the app.

A checkout cannot answer for a device or a store account. The command prints these as unchecked rather than guessing:

• Store account state: agreements, product status, and license testers.
• Device state: a scene session or an installed build left by another app that shares the bundle id.
• Play billing availability on the device and its signed-in account.

Usage

npx @hyodotdev/openiap doctor            # the working directory
npx @hyodotdev/openiap doctor ./my-app   # a project elsewhere
npx @hyodotdev/openiap doctor --json     # one JSON report
npx @hyodotdev/openiap --version         # the version and nothing else

Exit code is 1 when there is an error, 0 otherwise.

--json emits {framework, findings, errors, warnings, notCheckedLocally}. Each finding carries a stable id, a level, the file it was read from, a message, a fix, and — where the check can point at one — a line, expected, and actual. Match on id; the prose is for people.

Sponsors

Thank you to Meta and Amazon Developer for supporting OpenIAP. View sponsorship options.

OpenCollective

We also recognize sponsors and backers through OpenCollective. The original react-native-iap collective now supports the broader OpenIAP ecosystem and is managed separately from the main sponsor program.

Sponsors:

Backers:

Become a sponsor | Become a backer

Past supporters

Supported the project before the OpenIAP sponsor program.