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 push keeps showing updates needed even successful Deploy on Data Amplify Studio #13340

Closed
4 of 14 tasks
harrynguyenangle opened this issue Oct 17, 2023 · 6 comments
Closed
4 of 14 tasks
Labels
pending-response Issue is pending response from the issue author pending-triage Issue is pending triage transferred This issue was transferred from another Amplify project

Comments

@harrynguyenangle
Copy link

harrynguyenangle commented Oct 17, 2023

Description

As usual when running command Amplify push, it fetches the changes between local and Amplify on cloud to show which changes needed to be updated, then we open Data on Amplify Studio, start to Deploy

In my cash, after Deploy successfully, I ran Amplify push again, it still shows Datastore API needed be updated, then I push again -> deploy -> check again Amplify push locally, and it keeps shows "Datastore API needed be updated"
I did this process multiple time and still update needed

Note that I open new Studio page to make sure load new everytime when command run Amplify push locally done

Categories

  • Analytics
  • API (REST)
  • API (GraphQL)
  • Auth
  • Authenticator
  • DataStore
  • Notifications (Push)
  • Storage

Steps to Reproduce

No response

Screenshots

Screenshot 2023-10-17 at 15 44 24

No response

Platforms

  • iOS
  • Android
  • Web
  • macOS
  • Windows
  • Linux

Flutter Version

3.13.7

Amplify Flutter Version

1.4.1

Deployment Method

Amplify CLI

Schema

No response

@haverchuck
Copy link
Contributor

@harrynguyen2510 Thanks for reporting this. I'm transferring this issue to the amplify-cli repository.

@haverchuck haverchuck transferred this issue from aws-amplify/amplify-flutter Oct 17, 2023
@josefaidt josefaidt added pending-triage Issue is pending triage transferred This issue was transferred from another Amplify project labels Oct 17, 2023
@josefaidt
Copy link
Contributor

Hey @harrynguyen2510 👋 thanks for raising this! After deploying with Amplify Studio you can run amplify pull to sync the latest changes. If you run this command after deploying with Studio does it still show as UPDATE on every push?

@josefaidt josefaidt added the pending-response Issue is pending response from the issue author label Oct 17, 2023
@harrynguyenangle
Copy link
Author

harrynguyenangle commented Oct 19, 2023

Thanks for reply @josefaidt , after Deploying with Amplify Studio, I ran locally Amplify push, it will automatically pull to sync the latest changes from Studio, and still shows as UPDATE on every push. This is the issue

@github-actions github-actions bot removed the pending-response Issue is pending response from the issue author label Oct 19, 2023
@ykethan
Copy link
Member

ykethan commented Oct 19, 2023

Hey @harrynguyen2510, tried reproducing the behaviour using the following steps but did not observe the issue.

  1. created an amplify app with studio and added a GraphQL API resource.
  2. pulled the backend to local environment.
  3. the added a model in studio and deploy
  4. once deploy finished, ran amplify push locally which provided an status as follows
    image
    additionally, tried making local changes along with changes in Amplify Studio. running push showed a similar out.
    on running the push the local changes replaced the changes in Amplify Studio.

Could you run amplify pull with a version system like git enabled and provide us the changes observed.
Additionally, run amplify status after the pull command in run to check the API status.
Information on the changes made in studio and locally would also enable us in reproducing the behaviour.

@ykethan ykethan added the pending-response Issue is pending response from the issue author label Oct 19, 2023
@ykethan
Copy link
Member

ykethan commented Dec 13, 2023

Closing the issue due to inactivity. please feel free in reaching out to us, we would be happy in diving deeper.

@ykethan ykethan closed this as not planned Won't fix, can't repro, duplicate, stale Dec 13, 2023
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
Labels
pending-response Issue is pending response from the issue author pending-triage Issue is pending triage transferred This issue was transferred from another Amplify project
Projects
None yet
Development

No branches or pull requests

4 participants