Repository navigation
Error when implementing a middleware with SWIFT_APPROACHABLE_CONCURRENCY #804
Description
Question
Since Xcode 26 beta 5 i cannot comply with the ClientMiddleware protocol of swift-openapi-runtime. The error that I got is Candidate has non-matching type '(HTTPRequest, HTTPBody?, URL, String, nonisolated(nonsending) @Sendable (HTTPRequest, HTTPBody?, URL) async throws -> (HTTPResponse, HTTPBody?)) async throws -> (HTTPResponse, HTTPBody?)' for a structure that seems (and was) to be well "made":
public struct ApiKeyMiddleware: ClientMiddleware {
//The API key to login
private let apiKey: String
public init(apiKey: String) { self.apiKey = apiKey }
public func intercept(
_ request: HTTPRequest,
body: HTTPBody?,
baseURL: URL,
operationID: String,
next: @Sendable (HTTPRequest, HTTPBody?, URL) async throws -> (
HTTPTypes.HTTPResponse, OpenAPIRuntime.HTTPBody?
)
) async throws -> (HTTPTypes.HTTPResponse, OpenAPIRuntime.HTTPBody?) {
var request = request
request.headerFields[.init("x-goog-api-key")!] = self.apiKey
return try await next(request, body, baseURL)
}
}Is this an Xcode/Swift bug or is there something that I'm missing?
Thanks
Activity
BrentMifsud commentedon Aug 7, 2025
running into the exact same problem. There doesn't seem to be a way to prevent Xcode from automatically adding
nonisolated(nonsending)to the implementation as far as I can tell.czechboy0 commentedon Aug 8, 2025
Ok, seems to be happening only with the SWIFT_APPROACHABLE_CONCURRENCY=YES build setting. While we investigate this, one workaround is to create a dedicated target for your middleware/generated code, and ensure the build setting is turned off in that target only.
Edit: An easier workaround is to add
@concurrentto thenextparameter, before@Sendable, making it:[-]`ClientMiddleware` compliant structure not compliant since Xcode 26 beta 5[/-][+]Error when implementing a middleware with SWIFT_APPROACHABLE_CONCURRENCY[/+]