Open
Description
Describe the bug
With the release of iOS 26, the SPM pod breaks, I see the following error on attempting to compile.
Relevant log output
/Users/xxx/Library/Developer/Xcode/DerivedData/XYZ-gllhxxqtkpzmwigvqwfmyxanljeg/SourcePackages/checkouts/amplify-swift
/AmplifyPlugins/Auth/Sources/AWSCognitoAuthPlugin/ASF/ASFAppInfo.swift:19:24
Cannot find '__IPHONE_OS_VERSION_MIN_REQUIRED' in scopeXcode: 26.0.0-Beta OS: MacOS 26.0 iOS: 26.0
Steps To Reproduce
Steps to reproduce the behavior:
1. Install XCode 26.0 beta, target device running iOS 26.0 (beta)
2. Try following dependency in your proj:
`.package(url: "https://github.com/aws-amplify/amplify-ui-swift-liveness", from: "1.3.5")`
3. Compile to see errorExpected behavior
iOS 26 version should compile.
Swift Liveness Version
5.9
Xcode version
Version 26.0 beta (17A5241e)
Is this a regression?
No
Regression additional context
No response
OS Version
iOS 26.0
Device
iPhone 12 mini
Specific to simulators
No response
Additional context
No response
Metadata
Metadata
Assignees
Labels
Type
Projects
Milestone
Relationships
Development
No branches or pull requests
Participants
Activity
thisisabhash commentedon Jun 10, 2025
Hello, Thank you for posting this. Our team will take a look and post updates here.
benfrearson commentedon Jun 19, 2025
I have the same issue - exact same error and os/tool versions.
harsh62 commentedon Jun 20, 2025
This is expected because the underlying dependency
amplify-swifthas an issue. We will update once that is resolved.benfrearson commentedon Jun 20, 2025
@harsh62 Is there not an option for you to create a new iOS26 branch that points to the in progress fix for
amplify-swift's iOS 26 branch?aws-amplify/amplify-swift#4003
harsh62 commentedon Jun 20, 2025
Since this is Beta and you just want to test out Xcode 26. I would suggest to fork the repo and modify the Package.swift file to point to that custom branch from Amplify.
We will keep this issue open incase we need to fix anything specific to Xcode 26.
benfrearson commentedon Jun 23, 2025
That's a poor approach to maintaining this package imo.
This isn't really about "testing out" Xcode 26. The purpose of using Xcode 26 and the iOS26 SDK is to be able to prepare our app for the public release of iOS 26. As it stands, we can't build our app without Amplify, and so we can't do any work to update our UI.
No we won't be releasing any builds from this version of the toolchain in the short term, but that doesn't mean we don't need to be able to prepare for when we do.
Suggesting that all users of the package using Xcode 26 create a fork is ludicrous. I imagine many (most?) iOS devs will be trying to prepare their apps for the release of iOS 26 in September, and so to just write it off because it's a beta is very shortsighted.
A quick look at the error suggests that it is very likely this issue will need fixing in Amplify for the release version of Xcode 26—are you not planning on maintaining this package until then?
harsh62 commentedon Jun 23, 2025
@benfrearson
The packages are actively maintained and we have team members answering/fixing issues all the time. Xcode 26 will definitely be supported but we won't be able to support every beta that is rolled out by Apple.
We've already provided a WIP branch in Amplify Swift Repo discussed in this issue.
In the short term, if you want to try/test/prepare Xcode 26 with Amplify, you are free to do so by forking this repo and pointing to the Xcode 26 WIP branch.
It could even may be that Apple fixes this issue in the next Beta rollout.