# Build Apple Apps on Remote Xcode

Local Apple builds require macOS and Xcode infrastructure. This skill sends projects to Limrun for remote builds, simulator installation, signing, previews, and App Store uploads.

## Install

```bash
npx skillstore add limrun-inc/limrun-xcode
```

## Metadata

- Status: approved
- Slug: limrun-inc-limrun-xcode
- Skillstore revision: r1
- Version status: missing
- Tree hash: 3bb012a531e267e034ed001f04714af128f85634811ff01a1c3da84f10502a45
- Author: limrun-inc
- GitHub username: limrun-inc
- License: MIT
- Repository: https://github.com/limrun-inc/skills/tree/e29a129cea3d311d2bd348eef1aadcd1b20397d5/skills/limrun-xcode
- Ref: 4ec79c4a51e6b1df1b440d2b6ae810d3f433a601
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: blocked
- Manual install advisory: allowed\_with\_warning
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network, env\_access
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/limrun-inc-limrun-xcode
- Manifest: https://skillstore.pages.dev/api/skills/limrun-inc-limrun-xcode/manifest

## Capabilities

- Builds Xcode projects and workspaces on Limrun remote Xcode instances.
- Generates gitignored Xcode projects from XcodeGen project specifications before building.
- Builds React Native and Expo native iOS projects with optional development server URLs.
- Installs and relaunches successful builds on an attached remote simulator.
- Creates signed device IPA files using cloud signing or supplied certificates and profiles.
- Uploads build artifacts to Limrun storage or App Store Connect.

## Use Cases

- Build iOS Without Local Xcode: Compile and install an Apple application from Linux, Windows, macOS, a virtual machine, or a container.
- Automate Remote Apple Builds: Run repeatable Debug or Release builds for projects, workspaces, XcodeGen, React Native, and Expo repositories.
- Prepare and Deliver Signed IPAs: Create signed device artifacts and upload approved releases to storage or App Store Connect.

## Prompt Templates

### Build a Basic Xcode Project

```
Build the Apple project in [project path] with Limrun. Use the default scheme and report the build result and artifact location.
```

### Build a Selected Workspace

```
Build [workspace] with scheme [scheme] and configuration [Debug or Release]. Attach a remote simulator only when installation or interaction is required.
```

### Create a Signed Device IPA

```
Create a signed IPA for [bundle identifier] using [cloud or manual] signing. Ask before transmitting credentials, then report the secure download location.
```

### Deliver an App Store Build

```
Build [project] for App Store Connect, increment the build number, and sign with least-privileged credentials. Upload after my explicit confirmation and report processing status.
```

## Limitations

- Requires the Limrun CLI, network access, authentication, and access to Limrun remote infrastructure.
- Does not support Bazel workspaces; those require the separate limrun-xcode-bazel skill.
- Simulator taps, screenshots, recordings, and element inspection require the limrun-ios-simulator skill.
- Large files, absolute symlinks, and links outside the synced root can prevent source synchronization.

## Best Practices

- Confirm the source path, scheme, workspace, configuration, and target before starting a remote build.
- Use interactive login and least-privileged, short-lived signing credentials whenever possible.
- Request explicit approval before source upload, credential transmission, artifact publication, or App Store delivery.

## Anti Patterns

- Do not paste API keys, certificate passwords, private keys, or signed access URLs into conversation history.
- Do not use this skill for Bazel workspaces or local simulator automation.
- Do not retry an accepted App Store upload while Apple is still processing it.

## Security Audit

- Audited at: 2026-08-21T08:33:54.339\+00:00
- Summary: Most static alerts are false positives caused by Markdown backticks, command fences, identifiers, and a documented URL. Confirmed risks involve soliciting an API key and transmitting Apple signing certificates and passwords to a remote build service. Semantic review also identified unpinned global package installation, source-code upload, and privileged App Store credential transfer.

## Stats

- Views: 0
- Downloads: 0
- Favorites: 0
- Popularity score: 0