Amplify-cli: Amplify Publish not pushing changes to cloud - won't update.

[lowercase00]

Describe the bug
Yesterday, changes in my Vue project stopped being updated in the cloud.
I thought that it was because I had changed the version of my project at packages.json file.
So I deleted everything related to Amplify and my environment, cleared my related S3 buckets and init the project again. Today, everything was working fine - I'm 100% positive that I only made changes to the .vue files, but all of the sudden (after about 5 publish commands) it stopped pushing my updates to the cloud.

Expected behavior
When using the amplify publish command, the code should be updated in the cloud.

Desktop (please complete the following information):
macOS Mojave

Additional context
Using Vue-CLI

[UnleashedMind]

@lowercase00
publish has 4 operations, executed in the following sequence:

1. executes amplify push to update the backend resources in the cloud
2. builds your frontend application into the "Distribution Folder"
3. uploads the contents in the "Distribution Folder" into the deployment buckets.
4. if CloudFront is enabled and you explicitly added the '-c' flag in the amplify publish -c, a invalidation request is sent to the CloudFront.

I was not able to reproduce the bug. Could you be more specific which part of the above was broken? so we can investigate further.

[stayingcool]

I have the same problem today with Angular app.
amplify publish is completing without any issues, however, the latest version of the front end is not being served through S3.
If I try to serve it locally (npm start) just to see if the changes are showing up and I do see the latest changes I have made.
Things that I have done, the issue is still at large:

1. Remove the contents of S3 bucket manually (Never did this before, just getting annoyed)
2. Run the amplify publish command

Any clues to see why the latest front end build is not showing up on S3.

Note : I'm using new cli (multiple env version: 0.2.2-multienv.1)

[stayingcool]

Just an update from myside, after reading other issues I did the following to get the issue resolved:

1. amplify configure project
2. Deleted the contents of S3 bucket (Not required in my opinion, was just desperate to get the latest changes)
3. amplify publish

Note - By the way, I'm working on a multi-environment, chances are there that after bringing up an enviroment we might have to configure the project. Still new to multi-environment support functionality.

[lowercase00]

For me it works after deleting everything (S3 bucket and project).
My guess is that the publish is where the problem is, since just as @stayingcool when I run the project locally it works just fine (showing my updates). I chose to switch to aws s3 sync for now and adding a deploy script to my packages.json file:

"deploy": "node build/build.js && aws s3 sync ./dist s3://mybucket --acl public-read"

[kaustavghosh06]

@lowercase00 Were you checking for changes in your cloudfront instance or S3 instance?

[Gl0ntz]

Leaving this here for anyone else that comes across this problem
I was having the same problem with my react app. Tried everything that the other threads suggested but it still wont update.
I finally went to the S3 bucket and compared the build folder and found multiple files with file name "precache-manifest.123lkj123lk1j2lk312.js"
after "amplify push"
I compared it to my build folder and then deleted all files of that name/type other than the one that was the same as my local build folder.
Still on a regular browser it was showing me the old web app, I opened the react app on an incognito window and that worked.

[bradgreens]

I had this issue after moving the project to a different folder on my machine. I had to update the config file ./amplify/.config/local-env-info.json to tell Amplify where to deploy from. Prior to that it was deploying the old code in another directory and it looked like it was not pushing changes.

[mikeRChambers610]

@bradgreens Thank you!!!