amplify-hosting
amplify-hosting copied to clipboard
aws-amplify
Failed to deploy with no error messages
Before opening, please confirm:
- [X] I have checked to see if my question is addressed in the FAQ.
- [X] I have searched for duplicate or closed issues.
- [X] I have read the guide for submitting bug reports.
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
App Id
d3v5fhuza2jj3v
Region
ca-central-1
Amplify Hosting feature
Logging, Manual deploys
Describe the bug
Since about a week ago, every builds in the application complete but the deployment fails, then a few seconds later they complete. Because of this, it seems that the deployment is incomplete: the application responds with a blank page, then a few minutes later (and after clearing the browser cache) the application deployed correctly, even though amplify mentions that the deployment failed.
I have no error message except this in the Deploy tab:
2022-09-08T13:59:51 [INFO]: Starting Deployment
2022-09-08T13:59:51 [INFO]: Updating Edge config
2022-09-08T13:59:51 [ERROR]: Failed to deploy
Got archive: 7602706 bytes
2022-09-08T13:59:53 [INFO]: Deployment complete
Expected behavior
Expected to deploy and verify successfully with the application being immediately available without any clearing of caches.
Reproduction steps
- Any deployment either manually with the console, or with automatically with new commits.
Build Settings
version: 1
frontend:
phases:
preBuild:
commands:
- yarn install --frozen-lockfile
build:
commands:
- yarn run build
artifacts:
baseDirectory: public
files:
- '**/*'
cache:
paths:
- node_modules/**/*
Additional information
No response
Same, it's terrible, I have to redeploy 4 or 5 times for it to finally work. Kill this service AWS, it's a catastrophe.
We also see failed builds. On the second failed one today (none have succeeded). Deploy seems to fail with error:
[ERROR]: Failed to deploy
Looking at the logs again a few minutes later, the log shows:
[INFO]: Deployment complete
At that point the logs don't show the failed message from before. Notifications are triggered as failed, so our platform does not fully finish the deployment.
Anyone from the Amplify team? Super disturbing to see reports like this go a week without any response.
Hello @alexdemers @houmark @bcastagna 👋🏽 apologies for the delay. We are investigating this issue internally and will provide an update with next steps shortly. @houmark and @bcastagna please provide your App IDs as well so we can provide better assistance. Thank you!
@hloriana thanks. What's the preferred email to use for sending app ID and more information?
Hi @houmark 👋🏽 you can send this information to [email protected]. The team is still root causing this issue but we will update as soon as we have next steps. We appreciate your patience!
@hloriana Our app ID is: d27sbj90esrqdg.
Build failed in both master and develop consistently, every time. It's quite embarrassing for AWS that it's now 21 days since this report, which has multiple others reporting the same issue, and they have just started looking into it. Are you not monitoring your platforms at all? I have a feeling the entire Amplify platform will soon be retired, it seems AWS has lost all interest in the product and reassigned all engineers to other tasks.
Hi @houmark thanks for providing your app ID. Your deployments moving forward should be shown as successful now. Your feedback is much appreciated and has been shared with the team. Please confirm with us that you're unblocked or if you are continuing to experience this behavior. Thank you!
Thank you @hloriana — I can confirm that we were able to build and deploy without issues on our development branch. Obviously curious to know what was the reason for this, but I expect it was a one-off and should not happen again?
@houmark Thank you for your continued patience and we sincerely apologize for the inconvenience caused due to a delayed response on the issue. We have unblocked your Amplify app d27sbj90esrqdg and you can now redeploy your previous build and they should complete successfully.
@alexdemers We have also unblocked your Amplify app d3v5fhuza2jj3v. Kindly redeploy your previous build.
@bcastagna Can you provide us your Amplify app ID?
That being said, we are actively working on root causing this issue and we will let you know once we have a timeline on the fix. In the meantime, if other developers run into this issue please provide us your Amplify app ID so that we can unblock you.
It builds on my side. What was the fix? It would be very helpful what caused the issue. Thanks for letting us know.
Hi there Amplify team! We are experiencing the same or similar issue - our deployment step is reported as successful, but then nothing happens; neither Cloudfront nor s3 buckets are updated. App ID dliunm6jxxnfd App ARN is arn:aws:amplify:eu-west-2:935417867901:apps/dliunm6jxxnfd The last definite successful build was Build 228 on the 23rd Nov. Possibly related; we moved onto the beta program on the 24th.
+1 with "INFO]: [4/4] Building fresh packages..." fails with no error messages. And not only with build command, but also install. For example, add postinstall script or husky, flow just stops there and doesn't show those failures as errors. IMO, to show the full stderr shouldn't be that hard.
Facing the same issue, App id: d3mmp4qranpgym
Its almost 3 days, the deployment keeps on failing without proper reason
Same issue with our app, deployment is reported as failed but actually works :
2023-12-05T11:23:12 [INFO]: Beginning deployment for application xxxxxxxxxxxxx, branch:dev, buildId 0000000000
2023-12-05T11:23:12 [INFO]: Got archive: 9164468 bytes
2023-12-05T11:23:15 [INFO]: Deployment complete
Having the same issue, build is successful but deployments are failing. Happens inconsistently across deployments that have identical codebases
