-
Notifications
You must be signed in to change notification settings - Fork 202
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 project not updating on pull stating path not found #3590
Comments
Hey👋 thanks for raising this! The issue appears to be similar to #3139. |
A fix was recently made, validating why it did not make it in the Amplify CLI release. |
I believe since its a react native project, you should be using the following configuration, right? This is when you initialize
You are facing this error, because the project thinks its a native iOS project and hence it tries to find the xcode project file in directory, which is not there and hence the command fails. Hope this information helps. |
If you already have a project setup, you could simply use |
This issue is now closed. Comments on closed issues are hard for our team to see. |
How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
20.11.1
Amplify CLI Version
12.10.3
What operating system are you using?
Mac
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 running Amplify pull the Xcode project cannot be updated. The error states that the path is not found. This is for an ios app using react native and amplify. The Xcode file is in the ios folder within the project root directory. I have tried manually updating the path but it did not resolve the issue.
Expected behavior
Successful pull incl. updating the Xcode project.
Reproduction steps
🚫 xcodeProject:
-- Caused by: notFound(path: "")
🛑 Command failed with exit code 1: /
Project Identifier
a79cf338859ac519db799d321ca10ffb
Log output
Additional information
No response
Before submitting, please confirm:
The text was updated successfully, but these errors were encountered: