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.

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

Amplify Pull fails after updating @aws-amplify/ui-react to latest in package.json #832

Closed
4 tasks done
ErikCH opened this issue Feb 17, 2023 · 3 comments
Closed
4 tasks done
Labels
bug An issue which has been identified as a bug cli An issue that needs to be tracked by CLI team studio-ui An issue that needs to be tracked by Studio Console team

Comments

@ErikCH
Copy link

ErikCH commented Feb 17, 2023

Before opening, please confirm:

App Id

dv3zryo7esei9

Region

us-west-1

Environment name

Studio-test

Figma File Version (if applicable)

No response

Amplify CLI Version

10.7.3

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

16.15.0

What operating system are you using?

Mac

Browser type?

Chrome

Describe the bug

Run amplify pull fails with
✖ Failed to sync UI components

Expected behavior

Should pull Amplify components

Reproduction steps

Assuming you already setup studio and you are pulling components into your app

  1. Change your package.json to use latest

    "dependencies": {
    "@aws-amplify/ui-react": "latest",

  2. Run amplify pull

It will then fail

Project Identifier

No response

Additional information

No response

@ErikCH ErikCH added the pending-triage An issue that is pending triage label Feb 17, 2023
@ErikCH ErikCH changed the title Pull fails after updating @aws-amplify/ui-react in package.json Amplify Pull fails after updating @aws-amplify/ui-react in package.json Feb 17, 2023
@ErikCH ErikCH changed the title Amplify Pull fails after updating @aws-amplify/ui-react in package.json Amplify Pull fails after updating @aws-amplify/ui-react to latest in package.json Feb 17, 2023
@ykethan
Copy link
Member

ykethan commented Feb 20, 2023

Marking as bug, as I was reproduce the issue. Did observe the auto generated forms did get generated in the UI components folder.

@ykethan ykethan added bug An issue which has been identified as a bug cli An issue that needs to be tracked by CLI team studio-ui An issue that needs to be tracked by Studio Console team and removed pending-triage An issue that is pending triage labels Feb 20, 2023
@cwoolum
Copy link
Contributor

cwoolum commented May 23, 2024

Is putting latest in package.json actually a real use case? I would consider that a very bad practice.

@ykethan ykethan closed this as not planned Won't fix, can't repro, duplicate, stale Jun 4, 2024
Copy link

github-actions bot commented Jun 4, 2024

⚠️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
Labels
bug An issue which has been identified as a bug cli An issue that needs to be tracked by CLI team studio-ui An issue that needs to be tracked by Studio Console team
Projects
None yet
Development

No branches or pull requests

3 participants