Skip to content
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.

Sign up for GitHub

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

Jump to bottom

amplify pull sandbox fails with amplify-meta.json does not exist error #13215

Closed
2 tasks done
ykethan opened this issue Sep 12, 2023 · 4 comments
Closed
2 tasks done

amplify pull sandbox fails with amplify-meta.json does not exist error #13215

ykethan opened this issue Sep 12, 2023 · 4 comments
Labels
bug Something isn't working p2 platform-pull Issues related to `amplify pull` wontfix This will not be worked on

Comments

@ykethan
Copy link
Member

ykethan commented Sep 12, 2023

How did you install the Amplify CLI?

curl

If applicable, what version of Node.js are you using?

No response

Amplify CLI Version

12.4.0

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

Describe the bug

Creating a sandbox application and running a pull causes the following error

Error: File at path: '/Users/<path>/myapp/amplify/backend/amplify-meta.json' does not exist
Successfully generated models. Generated models can be found in /Users/<path>/rn/myapp/src

causing being unable to add resources to the project

Expected behavior

not error on pull

Reproduction steps

  1. cerate a app on https://sandbox.amplifyapp.com/
  2. copy and run the pull command example: amplify pull --sandboxId a51fb968-6335-4d95-9ad3-b024878001e7
  3. observe error

Project Identifier

No response

Log output

# Put your logs below this line

Additional information

No response

Before submitting, please confirm:

  • I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
  • I have removed any sensitive information from my code snippets and submission.
@ykethan ykethan added the pending-triage Issue is pending triage label Sep 12, 2023
@josefaidt josefaidt added bug Something isn't working platform-pull Issues related to `amplify pull` and removed pending-triage Issue is pending triage labels Sep 12, 2023
@josefaidt
Copy link
Contributor

confirmed this is a bug

@josefaidt josefaidt added the p1 label Sep 12, 2023
@josefaidt
Copy link
Contributor

note for fix: this flow does a partial "pull" in the sense that gitignored files such as amplify-meta are not created (likely because we do not yet have an App ID). If amplify codegen models is the operation that is dependent on amplify-meta.json we can remove this execution.

It is also important to note that Amplify Studio no longer automatically enables DataStore, removing the need for modelgen

@ykethan ykethan added p2 and removed p1 labels Feb 13, 2024
@ykethan
Copy link
Member Author

ykethan commented Feb 13, 2024

closing as wont fix

@ykethan ykethan closed this as not planned Won't fix, can't repro, duplicate, stale Feb 13, 2024
@ykethan ykethan added the wontfix This will not be worked on label Feb 13, 2024
@github-actions GitHub Actions
Copy link

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working p2 platform-pull Issues related to `amplify pull` wontfix This will not be worked on
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@josefaidt @ykethan