-
Notifications
You must be signed in to change notification settings - Fork 820
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Xcode 16 Support #13929
Comments
Hey, thanks for raising this! I'm going to transfer this over to our swift repository for better assistance. |
@mindgrub-rkoch Thanks for submitting the issue. We'll try to reproduce the issue and investigate further. |
Transferring this issue back to the Amplify CLI team to added support for XCode 16.
|
@phantumcode thanks for the verification. Marking this as bug. |
Hi, I also meet this issue when I set up amplify environment in my demo project to test AWS Rekognition. The document I was reading is https://docs.aws.amazon.com/rekognition/latest/dg/face-liveness.html . When I typed ps: I'm an iOS developer, where can I help to solve the issue? As I can see, it is related to the element introduced by Xcode 16. So I guess if I know what exactly "Updating Xcode project" do, maybe I can update the script to make the "Updating Xcode project" work? |
Same issue after running amplify init as described in https://aws.amazon.com/getting-started/hands-on/build-ios-app-amplify/module-two/ |
Hey folks, for new projects we recommend using Amplify Gen 2 which uses AWS cdk with a TypeScript-based, code-first developer experience (DX) for defining your backends. |
I was developing AWS Face liveness, https://ui.docs.amplify.aws/swift/connected-components/liveness
Then how can I migrate to Gen 2 while I don't know what Amplify does and what liveness sdk needes, and Gen 1 just fails to run? We are developers, not fools, if we know the last step is just add two json files to the project, we can help to solve the issue. And then after we figure out what the sdk need and what gen1 does, we can migrate to Gen2. |
@RentonLin the liveliness component for swift is currently a part of the swift repository. Could you open a new issue on the amplify-swift repository with the above request. |
@RentonLin I am having exactly the same issues that you are, but with a different AWS iOS demo project. I have tried adding the files manually and adding Package Dependencies, but Xcode compilation still fails. I suspect other changes are required to the project files. |
Running into the same issue, any help here? Do note the temporary mitigation is to drop the generated models (e.g. User, User+Schema, AmplifyModels.swift) from amplify/generated/models into an "AmplifyModels" folder (create it). Make sure the files/folder are a part of your target. |
The support ticket I opened with AWS about this issue, has been closed. They were able to replicate the issue/s with Amplify CLI Gen 1, but the problem has been pushed to Xcode. What I have been able to do is successfully follow an Amplify Gen 2 demo project. |
How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v20.17.0
Amplify CLI Version
12.12.6
What operating system are you using?
macOS 14.6.1 (23G93)
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes made
Describe the bug
When attempting to run
codegen models
with a project created with Xcode 16, the generation succeeds, but updating the Xcode project is failing with the following error:Expected behavior
Codegen successfully generates the models and modifies the Xcode project appropriately.
Reproduction steps
amplify pull
if neededamplify codegen models
Note the codegen fails with the included error.
Project Identifier
704bf3f4b979261c925b5cb99d13f5b2
Log output
Additional information
No response
Before submitting, please confirm:
The text was updated successfully, but these errors were encountered: