Capacitor Dual-Store Release Preflight (Play + App Store)

    1

    A hybrid app has five places that hold its version and two stores with their own signing, hardening and disclosure rules.

    $29

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Capacitor Dual-Store Release Preflight (Play + App Store)

    Example session with this skill installed

    Run the release preflight on my Capacitor project at C:\Projects\myapp in strict mode and tell me what blocks a store upload.

    • Read your context and instructions
    • Compiled the capacitor dual-store release

    Summary

    Strict preflight: 9 passed, 1 warning, 2 failed. Not ready for upload.

    Failures

    • Version consistency: package.json=2.3.0; Android versionName=2.2.9
    • Signing-secret exclusion: android/upload.jks is in the tree

    Warning

    • Store screenshots: 3 files; take final device screenshots from signed builds

    Next steps

    1. Bump versionName to 2.3.0 in android/app/build.gradle and raise versionCode.
    2. Move android/upload.jks out of the repository; pass its path through MYAPP_KEYSTORE_PATH.
    3. Re-run node scripts/release-preflight.mjs . --strict --out dist, then generate the SBOM and release manifest.
    package.json

    Connects securely to your tools. The creator never sees your data.

    About this skill

    A hybrid app has five places that hold its version and two stores with their own signing, hardening and disclosure rules. The submissions that fail are rarely code: a versionName left behind, a keystore committed under android/, a privacy URL on localhost, an iOS package path with a Windows drive letter the Mac cannot resolve, a privacy manifest that still says "collects nothing" after sign-in shipped, an upload signed with a key Play never registered. This kit catches those before the upload.

    release-preflight.mjs: version agreement across package.json, both lockfile entries, the web manifest, Android versionName and iOS MARKETING_VERSION (extra sources by config); required release files; lockfile resolving only to the public registry; no .jks/.keystore/.p12/.mobileprovision/private PEM in the tree; Android target SDK, versionCode, minify and shrink, cleartext off, backup warning; iOS export-compliance answer and PrivacyInfo.xcprivacy consistent with whether the app collects identifiers; CSP on primary pages; public-HTTPS policy URLs (warn in development, fail in --strict); support email; screenshots. JSON and Markdown reports, exit 1 on failure.

    fix-native-package-paths.mjs: rewrites the absolute node_modules paths cap sync writes into Package.swift and capacitor.settings.gradle to portable relative ones; --check for CI.

    generate-sbom.mjs (CycloneDX 1.5 with purl, licence, integrity hash, dev flag) and generate-release-manifest.mjs (SHA-256 of every source file, excluding dependencies, build output, generated native assets, .env and signing material).

    Reference: the dual-store checklist with the irreversible decisions first and a go/no-go section; Google Data safety and Apple App Privacy worksheet templates with the gap that gets caught at submission; upload-key custody and the three version numbers; permission disclosure template with a worked example; real-device matrix.

    8 offline tests on a synthetic project. Node 20+, no packages, no network.

    Reads source files only, not signed binaries. Requires manual updates for yearly SDK policy changes. Does not drive physical devices for the testing matrix.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 18 days ago

    Requires

    node

    Permissions

    Read Files
    Terminal / Shell
    Write Files

    Reads the project's source files and writes reports under dist/. No network access, no environment variables read, no secrets handled.

    Listed18 days ago

    What's inside

    Frequently Asked Questions

    This skill automates the cross-referencing of version strings, security audits for leaked signing keys, and validation of native settings across Android and iOS to prevent store rejections and rebuild cycles.

    The skill is designed for any environment with Node 20+, making it compatible with AI agents that have filesystem access, local development terminals, or CI/CD runner environments.

    You receive a suite of Node-based validation scripts, a path normalizer for cross-platform builds, compliance generators for SBOMs, and comprehensive privacy/testing worksheets.

    Yes, the scripts are specifically designed to be integrated as a 'release gate' in CI/CD pipelines to ensure every build meets compliance standards before deployment.

    The skill audits your local source code and configuration files, but it does not perform binary analysis on the final compiled .ipa or .aab files.

    While the scripts automate the checks, users must still manually update their project's target SDK levels to meet the evolving annual requirements from Google and Apple.

    New in Mobile Development