-
Notifications
You must be signed in to change notification settings - Fork 116
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
Next.JS deployment not working after build completed #3631
Comments
Hi @questionableservices, thanks for reporting the issue. Unfortunately, we cannot reproduce this issue on our end. Could you please share the nextjs version for your app? and have you try to import all files under root directory in your application? It would be great if you could provide the minimal repro repository for us, you can send it to [REDACTED] Thanks! |
Hey @Jay2113 & @victorccccc ... I have recently hit the same exact issue on a project which was working fine. Did anything change w.r.t environment? The error in itself is not clear and there are no logs.
I am on |
We are facing the exact same issue on a project that was working just fine. Without any single code changes it just won't deploy anymore . Completed phase: build2023-08-03T11:56:02.211Z [INFO]: ## Build completed successfully Is anybody able to identify the root cause of this? It has to do something with an update done to Amplify, I see no other reason why it wont deploy |
I am still hitting the same issue ... and I am hoping to get some help from AWS folks here. I guess this is seen on NextJS projects only. I am not seeing this issue on Vercel or Netlify - and I am considering switching over. I would really like to keep this app on amplify. |
I agree with @sudhishkr . I have also created a ticket on stackoverflow - https://stackoverflow.com/questions/76832987/nextjs-build-failing-aws-amplify-required-dependency-file-not-found |
Hello, Like I've mentioned, it is running version 13.1.6 of NextJs, of a default project that initially worked and then about 7 days ago failed to build successfully. Should I provide access to the repository for you? Also, I did not understand what you meant by: and have you try to import all files under root directory in your application? |
Is there a way to get aws support to notice this ticket? I unfortunately don't have a premium support account to flag this. Wondering if it is possible to get some help here? |
Please provide an update on this issue as our team is blocked from doing any deployments on Amplify. |
@Jay2113 - I am completely blocked here. It would be good to get some improved logging in your logs as well. Do you have any estimates here? |
Hi everyone, thanks for your continued patience and just a quick note here that we are actively investigating into this and will keep you posted with any updates. |
Hi @questionableservices 👋 , could you please add me to your repository if possible? It would be very helpful if we can reproduce the issue. [UPDATE 1]: Thanks for your patience. We are working on a fix for this issue and will update here when the issue is resolved. [UPDATE 2]: Issue has been resolved. Please build your application again. |
Hey @Jay2113 & @victorccccc - thanks for the fix. I can confirm - I am unblocked .. and I am able to move forward here. |
I can confirm the issue has been fixed. Thank you for your help @victorccccc @Jay2113 |
|
This issue has been automatically locked. |
Before opening, please confirm:
App Id
d1nkrztuk7xgun
AWS Region
eu-central-1
Amplify Hosting feature
Frontend builds, SSR
Frontend framework
Next.js
Next.js version
13.1.6
Next.js router
Pages Router
Describe the bug
In the last few days, deployments simply do not work. The app I am trying to deploy is an initial version of one that was easily deploy two weeks ago. Now I just keep getting this error:
2023-07-31T18:52:16.797Z [INFO]: # Completed phase: build 2023-07-31T18:52:16.800Z [INFO]: ## Build completed successfully 2023-07-31T18:52:16.801Z [INFO]: # Starting caching... 2023-07-31T18:52:16.811Z [INFO]: # Creating cache artifact... 2023-07-31T18:52:25.048Z [INFO]: # Created cache artifact 2023-07-31T18:52:25.165Z [INFO]: # Uploading cache artifact... 2023-07-31T18:52:28.547Z [INFO]: # Uploaded cache artifact 2023-07-31T18:52:28.618Z [INFO]: # Caching completed 2023-07-31T18:52:28.620Z [INFO]: Setting NEXT_PRIVATE_STANDALONE=true to produce .next/standalone directory 2023-07-31T18:52:28.621Z [INFO]: # No custom headers found. 2023-07-31T18:52:29.494Z [ERROR]: !!! CustomerError: Required dependency file not found: /codebuild/output/src2725073759/src/webcv/amplify.sh
I've read in several places ( like this one ) that there has been a change.
Expected behavior
Build and deploy running smoothly like in the last few deploys done before the update on Amplify hosting
Reproduction steps
Build Settings
Log output
Additional information
No response
The text was updated successfully, but these errors were encountered: