Cannot assign value of type 'Int64' to type 'UInt64'

[gmantuanrosa]

Issue

I added the latest versions of URLSessionInstrumentation and OpenTelemetryProtocolExporterHTTP to my project via Swift Package Manager and once I try run the project I get the following build error Cannot assign value of type 'Int64' to type 'UInt64'.

The functions complaining with this issue are

/// func toProtoLogRecord(_)
if let observedTimestamp = logRecord.observedTimestamp {
    protoLogRecord.observedTimeUnixNano = observedTimestamp.timeIntervalSince1970.toNanoseconds
}
protoLogRecord.timeUnixNano = logRecord.timestamp.timeIntervalSince1970.toNanoseconds

/// func toProtoSpan(_)
protoSpan.startTimeUnixNano = spanData.startTime.timeIntervalSince1970.toNanoseconds
protoSpan.endTimeUnixNano = spanData.endTime.timeIntervalSince1970.toNanoseconds
    
/// func toProtoSpanEvent(_)
protoEvent.timeUnixNano = event.timestamp.timeIntervalSince1970.toNanoseconds

the .toNanoseconds extension is correctly converting to Int64

var toNanoseconds: Int64 {
    let nanoseconds = self * 1_000_000_000
    return Int64(withReportingOverflow: nanoseconds) ?? (self < 0 ? .min : .max)
}

but the generated logs.pb.swift and trace.pb.swift explicitly mentions UInt64

public var observedTimeUnixNano: UInt64 = 0

public var startTimeUnixNano: UInt64 {
    get {return _storage._startTimeUnixNano}
    set {_uniqueStorage()._startTimeUnixNano = newValue}
}
public var endTimeUnixNano: UInt64 {
    get {return _storage._endTimeUnixNano}
    set {_uniqueStorage()._endTimeUnixNano = newValue}
}
public var timeUnixNano: UInt64 = 0

Is there a way to fix this issue?

Environment:

iOS Version: 26
Swift version: 6
OpenTelemetry SDK Version: 2.3.0
OpenTelemetry Core SDK Version: 2.4.0

Also any version that I test I get the same error

[wesleynw]

Having the same issue. I reverted back to 2.3.0. It looks like they tagged 2.4.0 in the repo, so I autoupdated and this broke it. They haven't published any release notes, so maybe it's not finished?

[gmantuanrosa]

Having the same issue. I reverted back to 2.3.0. It looks like they tagged 2.4.0 in the repo, so I autoupdated and this broke it. They haven't published any release notes, so maybe it's not finished?

Weirdly enough I had to downgrade back to version 1.17.1 💀

[ArielDemarco]

Hey @gmantuanrosa thanks for the report! 2.4.0 was removed as it was generating backward incompatibilities. Downgrading to 2.3.1 should work properly.

We're going to be releasing 2.4.1 after merging this PR (there's more information related to the problem that we had there).

I'll let you know once that's released!