Your Apple Account
Signing in, two-factor codes, the Apple Developer Program enrollment ($99 per year) and accepting new agreements. Only the Account Holder can accept the Program License Agreement; the enrollment guide covers the account side.
Give Claude Code the real log
Xcode's red banner is a summary; the cause usually sits a few hundred lines earlier. There are two ways to get the real log to Claude Code. In Xcode, open the Report navigator (Cmd + 9), select the failed build or archive and copy or export the full transcript. Or, simpler, let Claude Code run the build itself: start it in Terminal inside the iOS project folder on your Mac, and it can call xcodebuild, save the output and search it.
Two details save hours. Always open and build WebViewGold.xcworkspace, not WebView.xcodeproj; the iOS setup documentation insists on this because only the workspace includes the dependencies. And Claude Code on the web runs on Linux: a cloud session can edit Info.plist or project settings in your repository, but it cannot run Xcode. iOS builds happen on a Mac, a rented Mac, or in the Cloud Builder.
The commands Claude Code will run
Run them yourself or let the agent run them. Step 1 tells you the real scheme name; use it in the other commands.
bash
mkdir -p build
# 1. List schemes and targets (always use the workspace, not the .xcodeproj)
xcodebuild -list -workspace WebViewGold.xcworkspace
# 2. Archive for the App Store and keep the complete log
# (replace WebViewGold with the app scheme from step 1 if it differs)
xcodebuild -workspace WebViewGold.xcworkspace \
-scheme WebViewGold \
-configuration Release \
-destination 'generic/platform=iOS' \
-archivePath build/App.xcarchive \
archive 2>&1 | tee build/archive.log
# 3. The lines that usually matter
grep -nE "error:|Provisioning|provisioning profile|Signing for|entitlement" build/archive.log | head -40
# 4. What Xcode actually used for each target
xcodebuild -workspace WebViewGold.xcworkspace -scheme WebViewGold -showBuildSettings \
| grep -E "TARGET_NAME|PRODUCT_BUNDLE_IDENTIFIER|DEVELOPMENT_TEAM|CODE_SIGN_STYLE|MARKETING_VERSION|CURRENT_PROJECT_VERSION"Errors you will meet, and who fixes them
| Error (excerpt) | Usual cause in a WebViewGold project | Fix | Who |
|---|---|---|---|
No such module '…', or hundreds of errors in the pods | The .xcodeproj was opened instead of the workspace | Quit Xcode (Cmd + Q) and open WebViewGold.xcworkspace | You |
Signing for "WebViewGold" requires a development team | No team selected for a target | Signing & Capabilities: select your team for the app target and every extension target | You, in Xcode |
No profiles for 'com.example.app' were found | Xcode is not signed in to your developer account, or the App ID does not exist yet | Xcode Settings, Accounts: add your Apple Account, keep automatic signing on and let Xcode create the profile | You |
Provisioning profile … doesn't include the Push Notifications capability (or App Groups, or the aps-environment entitlement) | The App ID lacks capabilities the project uses | Enable Push Notifications and App Groups on the App ID in the Apple Developer portal, as the publishing docs describe, then restart Xcode | You |
Embedded binary's bundle identifier is not prefixed with the parent app's bundle identifier | An extension such as OneSignalNotificationServiceExtension still has the template bundle ID | Use your main ID plus a suffix, for example com.example.app.OneSignalNotificationServiceExtension | Claude finds every mismatch, you confirm in Xcode |
Sandbox: rsync(…) deny(1) file-write-create during "Embed Pods Frameworks" | User script sandboxing in newer Xcode versions blocks CocoaPods build scripts | Set User Script Sandboxing (ENABLE_USER_SCRIPT_SANDBOXING) to No for the app target | Claude |
Command PhaseScriptExecution failed with a nonzero exit code | A build script failed; this line is only the consequence | Search upward in the log for the first error: of that script | Claude |
| Archive is greyed out or produces nothing | A simulator is the selected run destination | Select "Any iOS Device (arm64)", then Product, Archive | You |
| "Missing private key" next to a certificate in Xcode Settings, Accounts | The distribution certificate was created on another Mac | Export it as .p12 on that Mac, or revoke it and let Xcode create a new one | You |
ITMS-90189: Redundant Binary Upload, or "bundle version must be higher" | The build number was already used | Raise CURRENT_PROJECT_VERSION (Build) for every upload and MARKETING_VERSION (Version) for a new release | Claude |
| SDK version error on upload | Built with an Xcode that App Store Connect no longer accepts; since April 2026 uploads need Xcode 26 and the iOS 26 SDK or later | Update Xcode (and macOS if required) and download the current WebViewGold version, free for license holders | You |
ITMS-90683: Missing purpose string in Info.plist | A usage description was deleted although the binary still references that API | Restore the key with an honest, specific purpose text | Claude |
Unable to process request - PLA Update available | Apple published a new Program License Agreement | The Account Holder accepts it in the developer account | You (Account Holder) |
With a good optimized version of your web app you can have a stunning mobile app within a couple of minutes. Additionally to that the customer service is very nice and very helpful! I can just recommend WebViewGold :-)
The repair loop
Diagnose first, edit second, and keep your keys to yourself.
Open Claude Code in the iOS project folder
In Terminal,
cdinto the folder that containsWebViewGold.xcworkspaceand startclaude. Open Xcode itself at least once beforehand, so the command-line tools and your account are set up.Let it reproduce the failure
Paste the diagnosis prompt below. The agent lists the schemes, runs the archive and saves the full log to
build/archive.log, so you are both looking at the same text.Separate file fixes from account fixes
The prompt makes Claude sort each fix into "I can change this file" (Info.plist, build numbers, a build setting, extension bundle IDs) and "you must do this in Xcode or the developer portal". Approve the first kind; do the second kind yourself with the click path it gives you.
Archive again
Re-run the same archive command. A new error is progress: signing errors often come in layers, first the team, then the profile, then a capability.
Upload with a fresh build number
Distribute the archive from the Xcode Organizer or with Transporter. Every upload needs a new build number, so ask Claude to raise it before each archive.
Test before you submit
Install the build through TestFlight on a real iPhone and check push, Face ID and the offline screen before you send it to App Review.
The diagnosis prompt
It tells the agent what it may change and what it must hand back to you. The rules in point 5 are the ones that prevent a one-error problem from becoming a three-error problem.
Paste into Claude Code on your Mac, in the iOS project folder
This folder contains a WebViewGold iOS project. The App Store archive fails and I want a diagnosis before any change. 1. Run xcodebuild -list -workspace WebViewGold.xcworkspace and pick the app scheme. 2. Archive with -configuration Release -destination 'generic/platform=iOS' and save the complete output to build/archive.log. 3. Find the first real error, not the follow-up errors. Quote the relevant log lines and explain in plain English what they mean. 4. Sort the fix into one of two groups: (a) a file change you can make: Info.plist, version or build number, a build setting, a bundle ID mismatch between the app target and its extension targets; (b) something I must do myself in Xcode Settings > Accounts, the Signing & Capabilities tab or the Apple Developer portal. For (b), give me the exact click path. 5. Rules: do not change the team, the signing style, certificates or provisioning profiles; do not run pod update or change dependency versions; do not rename the Xcode project; never access the keychain or print certificates. Show me the proposed file changes and wait for my OK before applying them.
What Claude Code cannot do for you
None of these are missing features. They are tied to your identity and your keys, and they should stay that way.
Certificates and private keys
Creating or revoking distribution certificates, exporting a .p12 from the Mac that holds the private key, answering keychain prompts. Never paste a certificate password into a chat.
App IDs and capabilities
Registering the bundle ID, enabling Push Notifications and App Groups, creating the app record in App Store Connect. Automatic signing in Xcode does part of this, but you are the one who clicks.
Devices and trust
Registering test devices, turning on Developer Mode on the iPhone, trusting the computer. The agent can list the steps; your hands and your phone do them.
Submission decisions
Picking the build in App Store Connect, the export compliance answer, the review notes and pressing Submit. Claude can draft the texts; you own the answers.
Choosing identifiers
The bundle ID is permanent once the app is live. Decide it yourself, once; the bundle ID guide explains why.
Pitfalls
- Letting the agent "fix" signing. Switching to manual signing, pasting team IDs into project.pbxproj or deleting provisioning settings usually turns one error into three. Signing changes belong in the Signing & Capabilities tab.
- Renaming the Xcode project. The project is called WebViewGold and should stay that way; only the Product Name and the Bundle Display Name are meant to change.
- Updating dependencies to silence a warning.
pod updateor a new SDK version in the middle of a release is the classic way to break a build that only needed a new build number. - Deleting the tracking usage description. The WebViewGold docs ask you to keep the Privacy - Tracking Usage Description key; removing it crashes the app.
- Generic advice from old forum answers. On Apple Silicon Macs the setup docs describe Rosetta simulator destinations for some setups. If simulator builds fail with architecture errors, read that section before changing architecture build settings.
- Reusing build numbers. Every upload needs a higher build number, even when the version stays the same.
Checklist before every archive
WebViewGold.xcworkspaceopened in Xcode 26 or later.- A team is selected for the app target and every extension target.
- Extension bundle IDs start with the main bundle ID.
- The App ID has Push Notifications and App Groups if you use push.
- Version raised for a new release, build number raised for every upload.
- Config.swift points to the production URL, not a development server.
- Usage descriptions are specific and honest, and the tracking key is still there.
Frequently asked questions
Can Claude Code build and archive my iOS app?
On a Mac, yes: it can run xcodebuild for builds and archives in the terminal and read the results. It cannot click through Xcode, sign in to your Apple Account or approve keychain prompts, so signing has to be set up once by you.
Can I fix Xcode errors with Claude Code on the web?
Only partly. Cloud sessions run on Linux without Xcode, so the agent can edit Info.plist or project files in your repository but cannot build to verify the fix. Build on a Mac or with the Cloud Builder.
Should I give the agent my certificate or my Apple Account password?
No. Nothing in a normal build fix requires it. If a suggested fix needs your credentials, do that step yourself in Xcode or in the developer portal.
Why does the archive succeed but the upload fail?
App Store Connect runs its own checks after the archive: SDK version, build number, bundle ID registration, purpose strings and capabilities. Paste the exact upload error into Claude Code; most of these are one-line fixes.
Do I need a new WebViewGold version when Apple raises the Xcode requirement?
Often it is the easiest path. Updates are free for license holders: download the current project and let Claude Code copy your settings from the old Config.swift into the new one.
Three ways to get your app into the stores
Same result, different amount of work on your side. All three come with the approval guarantee and 24/7 human support.
Do it yourself
$109 per platform, one-time
The WebViewGold license: a finished Xcode or Android Studio project. Paste your URL, set name and icon, switch on features, build and submit. Free updates forever.
See plans on the main pageCloud Builder
$349 per license, one-time add-on
No Mac, no Xcode, no Android Studio: configure in the browser, we build both apps in the cloud and hand them to App Store Connect and the Play Console.
How the Cloud Builder works Try the free demoFull Service
$698 per platform $798
Send us your URL and icon. Our team configures, builds and delivers your app within 72 hours, white-label, with source projects. Both platforms for $1,158.
Full Service details Powered by
Winter Sale prices valid until December 31, 2026.