Reads the log
Give it the full xcodebuild output, not a screenshot. Codex finds the first real error under hundreds of warnings and explains it in plain words, which is half of every fix.
Five facts about the WebViewGold Xcode project
Most Xcode loops come from treating the project like a fresh Xcode template. It is not, and five facts from the iOS setup docs and our support desk explain most errors:
- Open the workspace. The project uses CocoaPods. Always open
WebViewGold.xcworkspace, never the.xcodeprojon its own, or the pods (OneSignal, AdMob and others) are missing. - There is more than one target. Next to the
WebViewGoldapp target sit extension targets such asOneSignalNotificationServiceExtension(and App Clip or others if present). Each needs a team, and each bundle ID must start with the app's:com.yourbrand.app.OneSignalNotificationServiceExtension. - Versions must match. All targets carry the same version and build number.
- The name lives in two places. The Product Name in Build Settings must not contain accented letters; the home screen name with accents goes into Bundle Display Name in Info.plist. Do not rename the project itself ("WebViewGold"); the publishing docs warn that it causes issues.
- One Info.plist key must stay. Remove permission texts you do not need, but keep Privacy - Tracking Usage Description; the docs note that the app crashes without it.
And one fact from Apple: since April 28, 2026, App Store Connect accepts only builds made with Xcode 26 or later. Use the current non-beta Xcode from the Mac App Store and a current WebViewGold version.
The errors we see most, and their fixes
| Message or symptom | Cause | Fix | Who |
|---|---|---|---|
| "No such module …" or "framework not found Pods_WebViewGold" | The .xcodeproj was opened instead of the workspace, or the unzip tool damaged the pods | Open WebViewGold.xcworkspace. Still failing: download the zip again, unzip with another tool, keep the folder names; run pod install in the project folder if needed | Codex can run it |
| "Pods-WebViewGold-frameworks.sh: Permission denied" with "Command PhaseScriptExecution failed with a nonzero exit code" | The script lost its executable flag during unzip | chmod +x on the script named in the log, then Product → Clean Build Folder | Codex |
| "… cannot be opened because the developer cannot be verified" | macOS Gatekeeper blocks the downloaded script | Close Xcode, Control-click the file in Finder (Pods/Target Support Files), choose Open, reopen the workspace | You |
| "Signing for OneSignalNotificationServiceExtension requires a development team" | Team set on the app target only | Select the same team in Signing & Capabilities for every target | You, or Codex with your Team ID |
| "Failed to register bundle identifier" / "… is not available" | The template bundle ID, or one another developer registered | Choose your own reverse-DNS ID and change it in every target | Codex |
| "The embedded binary's bundle identifier is not prefixed with the parent app's bundle identifier" | The extension ID still has the old prefix | Your app ID plus .OneSignalNotificationServiceExtension | Codex |
| ITMS-90685 "CFBundleIdentifier Collision" | An extension uses the same ID as the app | Give every extension its own suffix | Codex |
| ITMS-90473 "CFBundleVersion Mismatch" | The extension build number differs from the app's | Same version and build number in all targets | Codex |
| "Provisioning profile doesn't support the Push Notifications capability" | The App ID lacks the capability | Enable Push Notifications and App Groups for the App ID in the Apple Developer portal, remove and re-add the capability in Xcode, restart Xcode | You |
| "Failed to create provisioning profile" / "No profiles for … were found" | Wrong Apple ID or team in Xcode, or a simulator selected as destination | Check Xcode Settings → Accounts; archive with "Any iOS Device (arm64)" | You |
| "errSecInternalComponent" / "Command CodeSign failed with a nonzero exit code" | Locked keychain or missing certificate | Unlock the login keychain; if no Apple Distribution certificate is listed, create one under Settings → Accounts → Manage Certificates | You |
| ITMS-90717 "Invalid App Store Icon" (transparency or alpha channel) | The 1024 px icon has an alpha channel | Export it flattened without alpha and replace it in the AppIcon set | Codex can check it |
| ITMS-90725 "SDK version issue" | Built with an older Xcode and SDK | Update Xcode and rebuild | You |
| The app crashes right at launch after Info.plist edits | Privacy - Tracking Usage Description was removed | Restore the key with a short, true purpose text | Codex |
Where Codex helps, and where it hands over to you
Edits project text files consistently
Bundle IDs and version numbers live in project.pbxproj, permission texts in Info.plist, your settings in Config.swift. Codex changes every target in one diff instead of only the one you remembered.
Runs commands, with your approval
With the Codex CLI or IDE extension on your Mac it can run xcodebuild, pod install, plutil and sips. Commands that leave its sandbox (an Xcode build writes to DerivedData and may contact Apple) need your approval, or you run them and hand over the log.
Never your Apple account
Certificates, App IDs, capabilities and profiles live in your Apple Developer account, and the keychain needs your Mac password. Do not paste either into an agent. Codex writes the click path; you click.
Cloud tasks have no Xcode
A Codex cloud task can edit the project files in a repository and open a pull request, but it cannot build, sign or archive an iOS app. Builds happen on a Mac or in the Cloud Builder.
WebViewGold has allowed us the shortest and most efficient time-to-market ever possible from among all the other app platforms we have ever tried during the past 5 years. I don’t know why I hadn’t discovered you sooner, but I am really, really glad I did. Currently nearing 6000 app downloads on both iOS App Store & Google Play Store without any problem!
Hand Codex a full log
Run these in Terminal in the folder that contains WebViewGold.xcworkspace, or let Codex run them. The archive command does what Product → Archive does and saves everything to build.log.
bash
# 1. Schemes and targets (use the scheme name it prints below)
xcodebuild -list -workspace WebViewGold.xcworkspace
# 2. Archive from the command line and keep the complete log
xcodebuild -workspace WebViewGold.xcworkspace -scheme WebViewGold \
-configuration Release -destination "generic/platform=iOS" \
-archivePath build/WebViewGold.xcarchive archive 2>&1 | tee build.log
# 3. The errors only, with line numbers
grep -n "error:" build.log | head -40
# 4. Bundle IDs and versions of every target (one prefix, one version)
grep -n "PRODUCT_BUNDLE_IDENTIFIER\|MARKETING_VERSION\|CURRENT_PROJECT_VERSION" *.xcodeproj/project.pbxproj
# 5. Signing identities in your keychain
security find-identity -v -p codesigning
# 6. Does the icon have an alpha channel? (path from your AppIcon set)
sips -g pixelWidth -g pixelHeight -g hasAlpha path/to/AppIcon-1024.pngThe Xcode triage prompt
Fill in the brackets. The rules block is the important part: it lists what an agent should never touch in this project.
Paste into the Codex CLI or IDE extension, opened in the Xcode project folder
I am building the iOS app from the WebViewGold Xcode project in this folder, and the archive fails. Read build.log (the complete xcodebuild output) and help me fix it. Project facts: - Always build WebViewGold.xcworkspace (CocoaPods), never the .xcodeproj alone. - Targets: WebViewGold plus extension targets such as OneSignalNotificationServiceExtension (and others if present). Every extension bundle ID is the main bundle ID plus a suffix, e.g. com.yourbrand.app.OneSignalNotificationServiceExtension. - All targets use the same version, the same build number and the same development team. - My bundle ID: [com.yourbrand.app]. My Team ID: [ABCDE12345]. Version [1.0], build [1]. Rules: - Do not rename the Xcode project, do not run pod update, do not upgrade or remove SDKs (AdMob, OneSignal, others), do not delete the NSUserTrackingUsageDescription key, do not change the deployment target. - Before you edit project.pbxproj, show me the exact lines you will change. Change only bundle identifiers, version numbers and team settings. - I will not share passwords. For anything that needs my Apple account, the Apple Developer portal or the keychain, give me click-by-click steps instead. Answer with: 1. The first real error in the log, quoted (ignore warnings and follow-up errors). 2. Its cause in this project, in one or two sentences. 3. The fix: the changes you made, or the steps for me. 4. The command that verifies it.
Fix in this order
Each step removes a whole class of errors; skipping ahead makes later messages misleading.
Clean start
A fresh unzip of the current WebViewGold version with the folder names intact, the current Xcode, the workspace opened. Copy your Config.swift values over instead of nursing an old, half-fixed project.
Bundle IDs
Your ID on the app target, the same prefix plus a suffix on every extension. Decide it for good: choose the bundle ID once.
Team and signing
The same team on all targets, "Automatically manage signing" on, logged in with the Apple ID that belongs to your developer program membership.
App ID capabilities
In the Apple Developer portal, enable Push Notifications and App Groups for your App ID (the publishing docs ask for both), then restart Xcode so it fetches new profiles.
Versions
Version and build number identical across targets, and the build number higher than any build you uploaded before.
Archive
Destination "Any iOS Device (arm64)", then Product → Archive. If Archive is greyed out, a simulator is selected.
Upload and read the email
Distribute from the Organizer. Processing errors from App Store Connect arrive by email with an ITMS number; paste that email into Codex just like a build log.
Test the real build
Install from TestFlight, not only from Xcode: release builds use distribution signing and production push. See TestFlight for vibe-coded apps.
What Codex must not do in this project
- Run
pod updateor upgrade SDKs. That swaps the tested versions of OneSignal, AdMob and others for untested ones;pod installis enough. - Remove the AdMob SDK because you do not show ads. The docs warn that this produces many dependency errors; answer the Ad ID question in App Store Connect as the publishing docs describe instead.
- Rename the Xcode project, move folders or raise the deployment target to silence a warning.
- Delete the tracking usage description from Info.plist.
- Edit
project.pbxprojwithout a commit or backup first. Ask for the exact lines before the edit. - Receive your Apple ID password, an app-specific password or your Mac password. No build step needs the agent to know them.
Frequently asked questions
Can Codex in the cloud build my iOS app?
No. Cloud tasks can edit the Xcode project files in a repository, but compiling and signing an iOS app needs Xcode on macOS. Use the Codex CLI or IDE extension on a Mac, a rented Mac, or the Cloud Builder.
Should I give Codex my Apple ID so it can fix signing?
No, and it does not need it. Your Team ID (the 10-character identifier shown in the Apple Developer portal) is enough for the project settings; everything that needs the account itself is a few clicks you make in Xcode or the portal.
Apple emailed me about a missing push notification entitlement. Is that a rejection?
No, it is a warning that push is not configured. If you do not use push, continue with the submission. If you do, add the Push Notifications capability in Xcode and on the App ID in the Apple Developer portal.
Why is Product → Archive greyed out?
A simulator is selected as the run destination. Choose Any iOS Device (arm64) in the toolbar and try again.
Do I have to fix all the yellow warnings?
No. Warnings from third-party pods are normal in WebViewGold projects. Fix the errors, and the warnings App Store Connect mentions in its processing email.
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.