-
Notifications
You must be signed in to change notification settings - Fork 819
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
Labels
Comments
Hey, thanks for raising this! I'm going to transfer this over to our swift repository for better assistance. |
ykethan
added
the
transferred
This issue was transferred from another Amplify project
label
Sep 17, 2024
@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. |
ykethan
added
platform-init
Issues related to initializing a new Amplify project
and removed
pending-triage
Issue is pending triage
transferred
This issue was transferred from another Amplify project
labels
Sep 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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: