Exact artifact
The release candidate itself is the authority. Source intent never substitutes for observed artifact behavior.
Subscription Release Verification
Know whether the exact iOS build is safe to ship revenue on.
ReleaseProof verifies purchase, entitlement and clean-session restore on the release candidate itself, preserves artifact-bound evidence and gives your team a reproducible release verdict.
Exact-build identityEnvironment-bound verdictsEvidence before blockers
Example release candidate
Illustrative iOS build · Build 91
Revenue journeyApple Sandbox
Purchase
Provider + local access verified
Clean-session restore
Provider active · local premium locked
Recheck
Waiting for corrected artifact
Verified blocker
Restore did not reactivate local premium access
The provider entitlement is active, but the exact release candidate still renders premium content as locked after restore.
Artifact
91 · 8f2c…d91
Evidence
Provider + UI
Verdict
Evidence-backed
Free Precheck · $0
Find out whether the current gate fits before you create an account.
Check supported stack, exact candidate availability and journey readiness. The result is deterministic, actionable and based only on the facts you provide — not a sales qualification score.
Run free precheckSupported stack
iOS · Expo / React Native · RevenueCat
Exact candidate
Confirm artifact, version, build and build type
Journey readiness
Account, selectors, entitlement, purchase and restore
Truth boundary
No files uploaded · no release verdict emitted
What ReleaseProof changes
Release confidence should come from the candidate, not the code review.
Subscription failures often appear only when payment state, provider state and local application state diverge. ReleaseProof keeps those observations attached to the exact artifact that produced them.
Evidence-backed blockers
A blocker only exists when supporting evidence proves the failure. Missing evidence produces an inconclusive state, not a guess.
Reproducible recheck
The corrected candidate is rechecked against the same journey semantics so teams can distinguish a real fix from a changed test.
Exact-Build Revenue Journey Verification
One journey. One artifact. A verdict you can reproduce.
The proof loop is deliberately narrow: observe the revenue-critical path, preserve the evidence and require the corrected candidate to survive the same semantic recheck.
Bind the exact candidate
Capture the version, build, source and artifact identity before the revenue journey begins.
Run the revenue journey
Verify purchase, provider entitlement and local premium access against that exact candidate.
Prove clean-session restore
Reset the session and verify restore without silently changing the build or the journey contract.
Fix, rerun, sign off
Preserve the evidence, apply the fix, rerun the same semantic journey and issue an evidence-backed verdict.
Environment belongs to the verdict
Test evidence is only meaningful when its environment is explicit.
ReleaseProof keeps controlled Test Store evidence separate from Apple commercial environment evidence. It never turns one into the other and never guarantees Apple approval.
Controlled mechanism proof
RevenueCat Test Store
Proves the purchase and entitlement mechanism in a controlled non-production environment.
Commercial release gate
Apple Sandbox / TestFlight
Required exact-candidate evidence before ReleaseProof treats the commercial environment gate as satisfied.
Start with your candidate
Qualify the fit before you pay for the Release Gate.
Run the free precheck, resolve any deterministic setup gaps, then move the exact candidate into evidence-backed purchase, restore and recheck verification.