Amplify Status and Push Not Reflecting New Analytics and Function Changes

[alpha-adam]

How did you install the Amplify CLI?

npm

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

18

Amplify CLI Version

12.1

What operating system are you using?

linux, cloud9

Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

NA

Describe the bug

When using AWS Amplify CLI, new additions to my project (specifically analytics and a function) are not being recognized. Despite successfully adding these components and ensuring they are present in the team-provider-info and backend-config files, running amplify status or amplify push does not reflect these changes.

Expected behavior

I expected amplify status to show the newly added analytics and function, and amplify push to update these additions in the cloud environment.

Reproduction steps

Add new analytics and a function to the Amplify project.
Push changes to the Git repository.
Observe that both dev and prod branches are synchronized.
Run amplify status and amplify push.
Notice that the new additions are not listed or updated.

Project Identifier

ba02cdbba92e71aa235c621a1b28c279

Log output

NA

Additional information

Amplify Environments: dev, prod
Git Branches: dev, prod
Setup includes multiple categories (auth, api, function, storage)
The issue persists despite ensuring the correct file locations for changes and following the standard sequence of Amplify commands.

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]

Hey @alpha-adam, thank you for reaching out. Wanted to get a bit more information on the reproduction steps
After the Add new analytics and a function to the Amplify project and before Push changes to the Git repository are you running a amplify push?
Are the branches connected to Amplify hosting CICD builds? As once the hosting build runs the backend build we should be able to run amplify pull to pull the changes.
are you observing any error messages on the push?

[alpha-adam]

I'll write a more detailed reproduction here.

1. Add function / analytics to amplify env dev
2. amplify push
3. git push origin dev
4. then in a seperate cloud9 terminal set up with prod env and branch already
5. git pull origin dev (no conflicts, in prod we can see in backend-config.json new function and analytics)
6. verify that git prod and dev are up to date
7. amplify push / status in prod does not show the new added categories
8. cry

I'm trying to use the dev / prod workflow shown here: https://docs.amplify.aws/react-native/tools/cli/teams/

Thanks in advance!

[ykethan]

Hey @alpha-adam, thank you for the information. We will need to run amplify env checkout <env-name>, this should generate the amplify-meta.json with the changes, then running amplify status should show the matrix with the new resources.

[alpha-adam]

I see. I have two cloud9 envs set up for each of the different amplify envs, and I pull the changes with git. So that must be why the meta file is not being properly generated, because the checkout step is not being done in my case. I will test out your suggestion soon and report back.

Cheers!

[ykethan]

Adding the response-response label for now, do let us know if this mitigates the issue.

[alpha-adam]

Just confirmed that this solution worked. It also solved another problem that I was having; where the prod environment was having configuration issues with secretes and function versions. I suggest adding a note to the documentation to point out that the env checkout is an important step. Otherwise, people who use two seperate workspaces for each env will run into this same problem.

Thanks for your help! Much appreciated!

[ykethan]

@alpha-adam Glad to hear you were able to mitigate the issue. Let me forward this feedback to the team.
Closing the issue, do reach out to us if you experience any issues.

[github-actions]

⚠️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.