deploy-ios

Deploy Expo iOS apps to TestFlight and the App Store via EAS Build.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/atemaguer/bfloat-ide --skill deploy-ios-atemaguer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy-ios
Source: https://github.com/atemaguer/bfloat-ide/tree/main/resources/skills/deploy-ios
Command: npx skills add https://github.com/atemaguer/bfloat-ide --skill deploy-ios-atemaguer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual, error-prone work of preparing and submitting an iOS app release, helping you move from a local project to TestFlight and the App Store with fewer setup mistakes.

Core Features & Use Cases

  • Project validation: Checks that the app is configured with an Expo app manifest and a saved App Store Connect app ID.
  • First-time setup guidance: Explains the one-time use of the Deploy Modal to link App Store Connect and capture the ASC App ID.
  • Automated build and submit: Runs EAS init, installs dependencies, builds for iOS, and auto-submits to TestFlight for production releases.
  • Use case: A developer who already has an Expo app can hand this Skill the project and have it verify prerequisites, build the release, and submit it without interactive prompts.

Quick Start

Use this skill to deploy the current iOS app to TestFlight after confirming the project is linked and the Apple session is available.

Frequently Asked Questions about deploy-ios

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy an Expo iOS app to TestFlight from my local project?

To deploy an Expo iOS app to TestFlight, the Skill validates your project, runs EAS Build, and auto-submits the production release to App Store Connect without interactive prompts. It requires a configured ascAppId and a cached Apple session.

How do I link App Store Connect for a first-time iOS deployment?

For a first-time iOS deployment, you must use the Deploy Modal to link App Store Connect and capture your ASC App ID. This one-time setup is required before the Skill can validate your project and auto-submit builds.

Do I need an ascAppId configured before submitting my iOS app to TestFlight?

Yes, an ascAppId is required before submitting your iOS app to TestFlight. The Skill performs project validation to ensure your Expo app manifest has a saved App Store Connect app ID before running EAS Build.

Can I automate non-interactive production iOS submissions using EAS Build?

Yes, you can automate non-interactive production iOS submissions using EAS Build. The Skill runs EAS init, installs dependencies, builds for iOS, and auto-submits to TestFlight after verifying prerequisites and the Apple session.

What prerequisites are needed to ship an iOS build to TestFlight?

Prerequisites to ship an iOS build to TestFlight include an Expo-based project, EAS Build, a cached Apple session, and a configured ascAppId. The Skill checks these during project validation before running the automated build and submit process.

Why does my iOS app submission fail during project validation?

iOS app submission validation fails if the project lacks an Expo app manifest or a saved App Store Connect app ID. Ensure your ascAppId is configured and your Apple session is cached before attempting a non-interactive submission.