Repository navigation
fix: raise minimum deployment target to iOS 15 for Xcode 27 - #78
Merged
Merged
Conversation
Xcode 27 enforces a minimum iOS deployment target of 15.0 and refuses to build packages targeting anything lower. Bump Package.swift's iOS platform from v14 to v15 (macOS 12 / watchOS 9 already satisfy the equivalent minimums) and drop the now-redundant @available(iOS 15.0, *) attributes in the Upload API, which were already gating that code at iOS 15 regardless of the package's stated minimum. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
RTsta
marked this pull request as ready for review
September 17, 2026 12:35
lukasvalkovic
approved these changes
Sep 17, 2026
The pinned iOS 18.2 simulator no longer exists on GitHub's macos-15-arm64 runner image, breaking the "iOS 18.2, Xcode 16.2" job on this PR and on master. Move the job to macos-26-arm64 with Xcode 26.6 (default) and its paired iOS 26.5 simulator runtime, the newest combination actually available on a current runner image. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
ipek
previously approved these changes
Sep 22, 2026
ipek
approved these changes
Sep 22, 2026
TParizek
approved these changes
Sep 22, 2026
| runsOn: macos-15 | ||
| - name: 'macOS 15, Xcode 16.2' | ||
| - name: 'iOS Simulator' | ||
| destination: 'platform=iOS Simulator,name=iPhone 17 Pro,OS=latest' |
Contributor
Author
There was a problem hiding this comment.
yes, they are. The CI tests passed 😊
| 4. You can retry a specific task in case of failure with ``retry(taskId:)`` | ||
| 5. In case you are not using a singleton instance don't forget to call ``invalidateSession(shouldFinishTasks:)`` once the instance is not needed anymore in order to prevent memory leaks, since the `UploadAPIManager` is not automatically deallocated from memory because of a `URLSession` holding a reference to it. | ||
| */ | ||
| @available(iOS 15.0, *) |
lukasvalkovic
approved these changes
Sep 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Xcode 27 drops the ability to build packages targeting below iOS 15 — the Xcode 27 release notes enforce a minimum iOS deployment target of 15.0, and building against a lower target now fails outright.
What's changing
Package.swift: bump.iOSfrom.v14to.v15(.macOS(.v12)/.watchOS(.v9)already satisfy the equivalent minimums, so left unchanged)@available(iOS 15.0, *)attributes across the Upload API (UploadAPIManaging.swift,UploadAPIManager.swift,UploadTask.swift,UploadAPIManagerTests.swift), since that code was already iOS-15-only and the package minimum now matches