AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Rn Eas Build Submit Update

skill-lukedj78-dev-flow-rn-eas-build-submit-update · by lukedj78

Use for cloud builds and OTA updates of an Expo + RN app via EAS: configuring eas.json profiles (development/preview/production), managing credentials (APNs key, Android keystore) without committing them to git, submitting builds to App Store Connect / Google Play via EAS Submit, shipping JS-only fixes via EAS Update with channels/branches, EAS Workflows for CI. Triggers on: "set up EAS Build", "…

No reviews yet
0 installs
10 views
0.0% view→install

Install

$ agentstack add skill-lukedj78-dev-flow-rn-eas-build-submit-update

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-lukedj78-dev-flow-rn-eas-build-submit-update)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
16d ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Rn Eas Build Submit Update? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

rn-eas-build-submit-update — guardrail for EAS Build / Submit / Update / Workflows

The 5 rules (non-negotiable)

  1. 3 profiles in eas.json: development (dev client, internal), preview (TestFlight / Play Internal — test on real devices), production (the store). NEVER ship from a profile not pre-tested in preview.
  2. Credentials server-side via eas credentials. NEVER commit .p12, .p8, *.keystore, *.jks, or google-services.json for production accounts. EAS holds them; local Apple/Google CLI never touches them.
  3. OTA only for JS-only changes. If the diff touches app.json config plugins, native modules, or anything that would change prebuild output → it's a new build, not an Update.
  4. Channels separate environments. preview channel for QA, production channel for end users. Ship updates to preview first, promote to production only after smoke-test.
  5. expo-updates config in app.json is the source of truth for runtime version (runtimeVersion: { policy: "appVersion" } or "sdkVersion"). Mismatched runtime versions = OTAs ignored.

Quick decision tree

  • "Build, Submit, or Update — which do I need now?" → references/decision-tree.md
  • "How do I write the eas.json profiles?" → references/eas-json.md
  • "How do credentials work — where does the cert live?" → references/credentials.md
  • "How do I set up EAS Workflows for CI?" → references/workflows.md
  • "Did the build/OTA I just shipped actually land OK — do I need a hotfix or rollback?" → rn-eas-deploy/references/observability.md (EAS Observe for build performance, EAS Update Insights for OTA rollout health)

Common anti-patterns (NEVER do)

  • ❌ Committing certificates / keystores to git.
  • eas build --profile production without ever having built --profile preview for that commit.
  • eas update --channel production without --branch and without testing on preview channel first.
  • ❌ Updating app.json config plugins and shipping via OTA — fails silently or crashes on user devices.
  • ❌ Bumping version in app.json without also bumping ios.buildNumber / android.versionCode — store reject.
  • expo-updates with default runtimeVersion (none) — OTA gets applied to incompatible native builds → crash.
  • ❌ Promoting an update to the production channel and never checking eas channel:insights / eas update:insights afterwards — see rn-eas-deploy/references/observability.md.

Sources

  • Course: codewithbeto.dev/rnCourse — EAS Build/Submit/Update/Workflows modules (paid).
  • Official: https://docs.expo.dev/eas/
  • Official: https://docs.expo.dev/eas-update/introduction/
  • Official: https://docs.expo.dev/eas-workflows/get-started/
  • Observability (post-Update health): rn-eas-deploy/references/observability.md, https://github.com/expo/skills (eas-update-insights)

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.