Export archive step fails in Xcode Cloud when using Xcode 26.2 (17C48) RC.
- The same project exports successfully when switching back to Xcode 26.1 in Xcode Cloud workflow settings.
- The same project exports successfully when using Xcode 26.2 RC locally.
- Projects without Apple Watch app do not encounter this issue (not so sure about this).
From Xcode Cloud UI:
Exporting for App Store Distribution failed. Please download the logs artifact for more information.
Run command: 'xcodebuild -exportArchive ...
Command exited with non-zero exit-code: 70
From xcodebuild-export-archive.log:
error: exportArchive Automatic signing cannot update bundle identifier "io.***.***.watchkitapp".
error: exportArchive No profiles for 'io.***.***.watchkitapp' were found
error: exportArchive Automatic signing cannot update bundle identifier "io.***.***".
error: exportArchive No profiles for 'io.***.***' were found
** EXPORT FAILED **
IDEDistribution: App Store Connect request for store configuration failed for account Session Proxy Provider
(Account "Session Proxy Provider": Unable to authenticate with App Store Connect
(Error Domain=DVTITunesSoftwareServiceFoundation.DVTServicesSessionProviderCredentialITunesAuthenticationContextError Code=1 "(null)"))
DVTServices: Sending request A7605D4E-2892-4B6D-9197-90BD3AB53D67 to <http://172.16.57.4:8089/services/v1/capabilities>
Payload: {"urlEncodedQueryParams":"teamId=984L9QX9X5&filter%5BreferenceType%5D=bundle&filter%5BincludeRequestable%5D=true&limit=200"}
{
"errors": [{
"id": "fb67ecdb-103b-4446-a2db-618fd6bd99e7",
"status": "400",
"code": "PARAMETER_ERROR.INVALID",
"title": "A parameter has an invalid value",
"detail": "A parameter 'filter[includeRequestable]' has an invalid value : ''includeRequestable' is not a valid field name.'",
"source": {
"parameter": "filter[includeRequestable]"
}
}]
}
DVTServices: Could not fetch capabilities from network due to error: error = 'A parameter has an invalid value'
Workaround
- Switching Xcode Cloud workflow to use Xcode 26.1 works around the issue.
- Using Xcode 26.2 RC locally works around the issue.
