Nextjs latest 13.3.0 deploy breaks IMAGE (next/image)

[marketsystems]

Before opening, please confirm:

• I have checked to see if my question is addressed in the FAQ.
• I have searched for duplicate or closed issues.
• I have read the guide for submitting bug reports.
• 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.

App Id

NEW_APP

AWS Region

eu-west-2

Amplify Hosting feature

Deployments, Frontend builds

Describe the bug

Deployed a simple gallery to Amplify as a test of my nextjs app which pulls images from cloudinary and passes them to next/image, site loads in browser fine and navigation to all pages works BUT ALL images appear broken using next/image <Image ... /> (server error 500 on all images).

Tried image urls from images hosted on S3 instead -> same issue all images broken.

Image Domains are allowed and correct in next.config.js

Using Next 13.3.0 npm package (the latest)
Using Nextjs App Dir

I have an app on amplify using next 13.2.0 and had no image problems at all so:
downgraded next package version to 13.2.0 SUDDENLY ALL IMAGES WORK FINE from any source!!

Can only assume next 13.3.0 and amplify do not work nicely yet

Expected behavior

The images should show instead of server error 500 and broken!

Reproduction steps

As Above description

Build Settings

No response

Log output

# Put your logs below this line

Additional information

No response

[killyvera]

i also had issues in the next 13 build provision phase, i cant go foward, but hosting my app in netifly works ok, it happened suddenly.

[nickfujita]

Had the same issue, and based on the error in CloudWatch, it seems like the following issue:
vercel/next.js#48173

So downgrading to 13.2.4 fixed this for me for now.

[shankiflang]

Same problem here !

[ghost]

Hi folks, this appears to be an issue related to Next.js 13.3.0 that may not be specific to Amplify Hosting according to this issue vercel/next.js#48173

However, we are investigating this further on our end to determine next steps. In the mean time, please downgrade Next to the previous working version.

[marketsystems]

Had the same issue, and based on the error in CloudWatch, it seems like the following issue: vercel/next.js#48173

So downgrading to 13.2.4 fixed this for me for now.

Yeah found 13.2.4 works fine! How do u find the error in cloudwatch? Not that clued up with aws yet myself but I did check cloudwatch to see if I could find out what it was - couldnt find an error log easily though..

[marketsystems]

Hi folks, this appears to be an issue related to Next.js 13.3.0 that may not be specific to Amplify Hosting according to this issue vercel/next.js#48173

However, we are investigating this further on our end to determine next steps. In the mean time, please downgrade Next to the previous working version.

I dont think its entirely AWS might be something other module related, looks like Docker deployment related but can tell you my project works on 13.3.0 locally with images showing and also no problems deployed to Vercel. Would be nice if it worked on Amplify too :D ;)

[ghost]

Hi @marketsystems thanks for those details. You can find those logs in the Amplify console by following these steps:

1. Navigate to Monitoring
2. Select the Hosting compute logs tab
3. Select the log group and a new tab will open with log events listed in the CloudWatch console

[ghost]

This issue no longer persists after the deployment of this fix from Next.js: vercel/next.js#48513

This was not an issue from Amplify Hosting and appears to have been resolved from Next.js side.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or 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.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.