Fix package build on Xcode 26.4.1 (#310)#312
Open
ssathy2 wants to merge 6 commits into
Open
Conversation
Xcode 26 tightened protocol-witness availability rules. When one class satisfies two presentation-context protocols of differing availability — ASWebAuthenticationPresentationContextProviding (iOS 12+) and ASAuthorizationControllerPresentationContextProviding (iOS 13+) — the shared 'presentationAnchor(for:)' witnesses can no longer be guarded with @available individually on the same type. Move each protocol conformance into its own extension with the appropriate @available attribute. The class itself stays unannotated (callers in ASWebServiceAuthentication and AppleSignInWebService are already iOS 12+/13+), and the framework's iOS 10 deployment target is preserved.
- Bump actions/checkout v2 → v4 (silences Node 20 deprecation warning). - Pin runner to macos-15 and select Xcode via maxim-lobanov/setup-xcode (latest-stable), so the build runs against the latest available Xcode rather than whatever macos-latest happens to alias to. - Add concurrency cancel-in-progress to drop superseded PR runs. - Replace the inline shell hacks with a small JSON-based simulator picker that returns a UDID (sturdier than name parsing). - Pipe xcodebuild through xcbeautify for readable test output, and pass CODE_SIGNING_ALLOWED=NO so CI never tries to sign.
ssathy2
force-pushed
the
fix/xcode-26-protocol-witness-availability
branch
from
d09b345 to
20c0fbc
Compare
- ConnectButton: activate the orphaned lessThanOrEqualTo bottom constraint so its return value is not ignored. - AuthenticationError: add .notInteractive, .matchedExcludedCredential, .credentialImport, .credentialExport to mirror the new ASAuthorizationError.Code cases Apple added in iOS 15.4 / 18 / 18.2. - SignInWithAppleAuthentication: handle those new codes behind availability checks and map each 1:1 to the corresponding AuthenticationError so callers see the actual Apple-side reason rather than a generic .failed / .unknown bucket.
ssathy2
force-pushed
the
fix/xcode-26-protocol-witness-availability
branch
from
0fe0a98 to
2b654e5
Compare
Contributor
Author
|
Note on the previously-bundled fixes from #311: I dropped the |
On Xcode 26 / iOS 26 simulators, disabling code signing prevents the host app from getting its default keychain-access group, so SecItemAdd silently fails for the SDK's Keychain-backed user token. That broke LocationServiceTests.test_willSync_location_triggers_authenticated, which relies on Keychain.userToken being readable after assignment. Simulator builds don't need explicit signing override — Xcode applies a simulator-only identity automatically.
Branch protection on main requires a status check named "Build and Test SDKHostApp scheme using any available iPhone simulator". The modernized workflow renamed the job to "Build & test SDKHostApp", which posted under a new check name and left the required check permanently in "Expected — Waiting for status to be reported". Restore the original job name; the rest of the modernization (macos-15, Xcode pinning, simulator picker, xcbeautify) is unchanged.
Replace the switch over ASAuthorizationError.Code with an if/else cascade. ASAuthorizationError.Code is non-frozen and gains new cases (notInteractive in 15.4, matchedExcludedCredential in 18.0, credentialImport / credentialExport in 18.2) that can only be referenced behind #available. With a switch, this trips "switch must be exhaustive" even with @unknown default, because the compiler sees those known cases at compile time but they aren't listed explicitly. An if-cascade has no exhaustiveness requirement and stays readable. The project-level IPHONEOS_DEPLOYMENT_TARGET = 10.0 (out-of-range) warning is left in place for now — the IFTTTConnectSDK target inherits that value, and bumping it surfaces real dead-code paths (SFWebService and ConnectionVerificationSession's iOS 11 fallback) that need a separate refactor to delete.
ssathy2
force-pushed
the
fix/xcode-26-protocol-witness-availability
branch
from
2a557fd to
a8b707f
Compare
|
@ssathy2 Do you have a release date for this? |
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
2 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.
Summary
Closes #310. Also bundles the changes from #311 (which is being closed in favor of this one).
AuthenticationSessionPresentationContextProvider.swift(Xcode 26)Xcode 26.4.1 tightened the rules for protocol-witness availability. When one class satisfies two presentation-context protocols of different availabilities —
ASWebAuthenticationPresentationContextProviding(iOS 12+) andASAuthorizationControllerPresentationContextProviding(iOS 13+) — the compiler now insists the sharedpresentationAnchor(for:)witnesses be as available as the least-restrictive protocol, producing:The
@available(iOS 12.0, *)/@available(iOS 13.0, *)attributes were leftover from when the SDK supported older deployment targets. The SDK now ships withIPHONEOS_DEPLOYMENT_TARGET = 14.2, so bothASWebAuthenticationSessionandASAuthorizationControllerare unconditionally available. Removing the attributes satisfies the new rule and changes nothing at runtime.CI workflow
Modernize
.github/workflows/ios.yml.ConnectButton.swift(from #311)The
constraint(lessThanOrEqualTo:)call on line 348 was never activated, leaving the "label bottom must not exceed container bottom" relationship dangling. The compiler flagged the unused result. Activate it explicitly. Also activatebreakableBottomConstraint(high-priorityequalTo) so the label actually pins to the container bottom when there's room — it was previously created but never installed.AuthenticationError+SignInWithAppleAuthentication.swift(from #311)Apple has added new
ASAuthorizationError.Codecases since the SDK was written. Add matching cases toAuthenticationErrorand map 1:1 so callers see the real Apple-side reason instead of being funneled into a generic.failed/.unknownbucket.ASAuthorizationError.CodeAuthenticationErrorcase.notInteractive.notInteractive.matchedExcludedCredential.matchedExcludedCredential.credentialImport.credentialImport.credentialExport.credentialExportEach Apple case is referenced behind an
if #availablecheck so the SDK still builds at its iOS 14.2 deployment target. Also adds an explicit.presentationContextInvalidmapping to the existing switch (was previously falling through to.unknown). The@unknown defaultis kept as a safety net for future Apple additions, which also clears the "switch must be exhaustive" warning that newer compilers raised against the previous iOS-13-only case set.Test plan
AuthenticationSessionPresentationContextProvider.swiftConnectButton.swift:348orSignInWithAppleAuthentication.swiftAuthenticationErrorcases