Hey there.
I'm experiencing a critical issue with Xcode Cloud builds for my macOS application (bundle ID: com.mymind.mymind-mac) where builds fail in Xcode Cloud with 7-8 errors, yet all logs indicate successful completion. Additionally, when manually uploading builds, they become stuck in "Processing" status indefinitely on App Store Connect. Issue Details:
Problem:
Xcode Cloud reports 7-8 build errors but logs show no fatal errors Secondary Issue: Builds uploaded to App Store Connect remain in "Processing" status indefinitely
Platform:
macOS application with Safari Web Extension Xcode Version: 26.1.1 (26B100) - Xcode 26.1 Build Environment: Xcode Cloud
What Works:
- Package dependency resolution completes successfully
- Archive creation succeeds (** ARCHIVE SUCCEEDED **)
- Export succeeds (** EXPORT SUCCEEDED **)
- Provisioning profiles are created correctly
- Code signing completes without errors
- Manual upload to App Store Connect completes
What Fails:
- Xcode Cloud: Build process fails with 7-8 errors, but no corresponding errors in logs
- App Store Connect: Builds remain stuck in "Processing" status and never become available for TestFlight or submission
- Logs Examined: All logs indicate successful completion with no fatal errors:
- xcodebuild-archive.log - Shows ** ARCHIVE SUCCEEDED **
- xcodebuild-export-archive.log - Shows ** EXPORT SUCCEEDED **
- resolve_package_dependencies.log - All packages resolved successfully
- IDEDistribution_standard.log - All distribution steps complete
- IDEDistributionPipeline.log - Packaging succeeds, code signing succeeds
- IDEDistributionProvisioning.log - Provisioning profiles created successfully
- IDEDistribution_critical.log - Only shows deprecated command warning
Only Warning Found:
- App Store Connect request for store configuration failed for account Session Proxy Provider
- Unable to authenticate with App Store Connect
(Error Domain=DVTITunesSoftwareServiceFoundation.DVTServicesSessionProviderCredentialITunesAuthenticationContextError Code=1)
Failed to find an account with App Store Connect access for team XXXXXXX
This warning appears non-fatal as the export completes successfully afterward.
Xcode Cloud Behavior:
- Xcode Cloud dashboard shows 7-8 errors
- No error details are visible in the Xcode Cloud UI
- All log files downloaded from Xcode Cloud show successful completion
- Build artifacts are created successfully
App Store Connect Behavior:
- Builds upload successfully (confirmed via Xcode)
- Build appears in App Store Connect with correct version/build number
- Status shows "Processing" with spinning indicator
- Build never completes processing (tested for 24+ hours)
- No email notifications about processing failures
App Configuration:
-
macOS application (minimum version: macOS 12.0)
-
Includes Safari Web Extension (SafariWebExtension.appex)
-
Includes Lottie framework
-
Uses automatic signing with managed provisioning profiles
-
Also tried with manual signing
-
Both Development and Distribution certificates valid until November 2026
Questions:
- Why does Xcode Cloud report 7-8 errors when all logs show successful completion? Where can I find the actual error details?
- Why do builds remain stuck in "Processing" on App Store Connect? Is there a backend validation failing that isn't being reported?
- Are there additional diagnostic logs that would show the actual errors Xcode Cloud is detecting?
- Is this related to the App Store Connect authentication warning? The logs suggest Xcode Cloud can't authenticate with App Store Connect properly, despite having valid credentials.
- Could this be related to Xcode 26.1.1 (26.1) compatibility with Xcode Cloud or App Store Connect processing?
Steps Taken:
- Verified all certificates and provisioning profiles are valid
Tested local builds and manual uploads (upload succeeds)
- Reviewed all available log files
- Waited 24+ hours for App Store Connect processing
- Tested both development and distribution exports (both succeed)
This issue is completely blocking our automated CI/CD pipeline and preventing us from releasing updates to the App Store. We cannot use Xcode Cloud for its intended purpose, and even manual workarounds fail at the App Store Connect processing stage.
Any hints or ideas would be welcome.
