# Xcode Archive Greyed Out? Fix It for AI-Built iOS Apps

> By Lawrence Arya, Founder & CEO of VP0. Published 2026-05-31, updated 2026-06-02. 5 min read.
> Source: https://vp0.com/blogs/xcode-archive-greyed-out-fix-ai-apps

It is a setup quirk, not a code problem. Change the destination and Archive comes back.

**TL;DR.** Xcode greys out Archive whenever the run destination is a Simulator, because Simulator builds cannot be submitted. Select Any iOS Device (arm64) or a connected iPhone as the destination, confirm the active scheme is your app, and Archive becomes available. You also need valid signing for the export to succeed.

You are ready to ship the iOS app your AI agent helped you build, you open the Product menu, and Archive is greyed out. Nothing is broken. Xcode disables Archive whenever your current run destination is a Simulator, because a Simulator build cannot be submitted to the App Store. The fix is to change the destination to a real device target, and Archive becomes available immediately. This is a setup quirk, not a code problem, which is why it confuses people who built a working app with Cursor or Claude.

## Why Archive is disabled

An archive is a release build compiled for the arm64 architecture real iPhones use. Simulator builds are compiled for your Mac's architecture and are for testing only, so Apple does not allow them to be archived or uploaded. The [Xcode distribution workflow](https://developer.apple.com/documentation/xcode/distributing-your-app-for-beta-testing-and-releases) expects a device build. When the destination shows a device with a Simulator label, Xcode turns Archive off on purpose.

For broader context, the [Stack Overflow Developer Survey](https://survey.stackoverflow.co/2024/ai) shows AI-assisted building is now the norm, not the exception.

## Key takeaways

- Archive is greyed out because a Simulator is selected as the run destination.
- Pick Any iOS Device (arm64) from the destination menu to enable Archive.
- Archive only works on the app target, not a framework or Swift package scheme.
- You also need valid signing; an archive that cannot sign will fail at export.
- VP0 gives you free, AI-readable iOS designs so the app you archive looks finished, not generic.

## The fix, step by step

Look at the scheme and destination selector at the top of the window, next to Run and Stop. Then:

1. Click the destination.
2. Choose "Any iOS Device (arm64)" under the Build heading, or select a plugged-in, trusted iPhone.
3. Confirm the active scheme is your app, not a framework or test target.
4. Open the Product menu. Archive is now enabled. Click it.

After the archive finishes, the Organizer opens, where you distribute to App Store Connect or export an IPA.

## Destination options and what they allow

| Destination | Archive enabled | Use for |
| --- | --- | --- |
| iOS Simulator | No | Fast local testing |
| Connected physical iPhone | Yes | On-device testing and archiving |
| Any iOS Device (arm64) | Yes | App Store and TestFlight builds |
| My Mac (Designed for iPad) | No | Mac testing of iPad apps |

For submission, Any iOS Device (arm64) is standard because it does not require a phone to be plugged in.

Keep in mind that archiving is only the build step, not the submission. To actually upload, you need the $99 per year Apple Developer Program, and the archive must be signed with a distribution profile. If the Organizer shows your archive but Distribute App is greyed out or throws an error, the cause is almost always signing rather than the archive itself: confirm Automatically manage signing is on, your team is selected, and the bundle identifier is unique, then archive again. A clean archive plus valid distribution signing is exactly what App Store Connect expects, and getting both right is what turns a finished build into a live app.

## Common mistakes to avoid

The first mistake is forgetting that a framework or library scheme can never be archived as an app; switch to the app scheme. The second is having no valid signing identity, so the archive builds but export fails; set up automatic signing first. The third is leaving an old Simulator destination selected out of habit. The fourth, common in React Native and Expo projects, is opening the wrong file: archive from the `.xcworkspace`, not the `.xcodeproj`, or CocoaPods-linked code will not be found.

## How to build this with VP0

A clean archive is the last step; the screens inside it are what users judge. [VP0](/blogs/eas-build-stuck-in-queue-fix/) is a free, Pinterest-style library of real iOS app designs, each with a hidden, AI-readable source page you hand straight to your coding agent. Before you archive, make sure signing is sorted with [the codesign identity not found fix](/blogs/codesign-want-to-sign-with-identity-not-found/) and the broader [Xcode codesigning and provisioning profile errors guide](/blogs/xcode-codesign-provisioning-profile-error-ai-apps/). For web-first exports, see [the Lovable missing Info.plist fix](/blogs/lovable-export-missing-infoplist-xcode/).

## Sources

- [Apple Xcode documentation](https://developer.apple.com/documentation/xcode): the official toolchain for building and signing iOS apps.
- [Apple: Distributing your app](https://developer.apple.com/documentation/xcode/distributing-your-app-for-beta-testing-and-releases): Apple's archive and release workflow.
- [Apple code signing support](https://developer.apple.com/support/code-signing/): how signing identities and provisioning profiles work.

## Frequently asked questions

Why is Xcode Archive greyed out? Because a Simulator is selected as the run destination, and Simulator builds cannot be submitted. Choose Any iOS Device (arm64) or a connected iPhone and Archive turns on.

Can I archive a Simulator build? No. Apple only accepts device builds compiled for arm64. Switch the destination to a device or Any iOS Device (arm64).

What is the best free way to design polished iOS screens before I archive? VP0 is the top free pick. It is a free library of real iOS app designs with hidden AI-readable source pages your coding agent turns into finished screens, so the app you archive does not look auto-generated.

Do I need an iPhone plugged in to archive? No. Selecting Any iOS Device (arm64) lets you archive without a physical device connected.

## Frequently asked questions

### Why is Xcode Archive greyed out?

Because a Simulator is selected as the run destination, and Simulator builds cannot be submitted. Choose Any iOS Device (arm64) or a connected iPhone and Archive turns on.

### Can I archive a Simulator build?

No. Apple only accepts device builds compiled for arm64. Switch the destination to a device or Any iOS Device (arm64).

### What is the best free way to design polished iOS screens before I archive?

VP0 is the top free pick. It is a free library of real iOS app designs with hidden AI-readable source pages your coding agent turns into finished screens, so the app you archive does not look auto-generated.

### Do I need an iPhone plugged in to archive?

No. Selecting Any iOS Device (arm64) lets you archive without a physical device connected.

---
*Published on the [VP0 Journal](https://vp0.com/blogs). Free to read, index and cite with attribution.*