-
Notifications
You must be signed in to change notification settings - Fork 11
Description
π Hello
First off, many thanks for introducing opentelemetry-swift-core π β it makes the Swift API much easier to adopt for SDK vendors π.
That said, the current platform requirements in opentelemetry-swift-core are higher than Xcodeβs actual minimum deployment targets, which limits adoption for SDK vendors like Datadog who aim to support a broader range of platforms. We would be happy to contribute a change to align these requirements.
Context
Since April 24, 2025, all apps uploaded to App Store Connect must be built with Xcode 16+ (source). To maximize compatibility, it makes sense to align with the deployment targets available in Xcode 16, as listed in Appleβs Xcode Releases matrix.
Although the matrix now lists iOS/tvOS 15, it was subject to ambiguity earlier this year when it originally listed iOS/tvOS 12. This update was later confirmed on Appleβs forum, clarifying that iOS 12 remains a valid β though discouraged β option.
In our view, SDKs should remain flexible and allow app developers to choose their own deployment baselines. Therefore, iOS/tvOS 12 should continue to be supported in by OTel Swift Api until Apple explicitly lifts this option (when requiring Xcode 26 for ASC uploads).
Proposal
| Platform | OTel Swift Core | Xcode 16 | Proposed Alignment |
|---|---|---|---|
| iOS | 13 | 15 (recommended), 12 (valid) | 12 |
| tvOS | 13 | 15 (recommended), 12 (valid) | 12 |
| macOS | 12 | 10.13 | 10.13 |
| watchOS | 6 | 7 | 6 |
| visionOS | 1 | 1 | 1 |
The code changes required for this seem to be minimal, and we would be happy to contribute.
Would you be open to us opening a PR to propose this change?