-
Notifications
You must be signed in to change notification settings - Fork 113
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
NextJS 13 App Dir Image Serving #3436
Comments
As per #3428, the issue is fixed with a Next upgrade |
|
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. |
Before opening, please confirm:
JavaScript Framework
Next.js
Amplify APIs
Not applicable
Amplify Categories
hosting
Environment information
Describe the bug
I have deployed a Next13 site with the
app
directory enabled to Amplify, and I have various assets in the top-levelpublic
directory to statically serve. I am using an index file to export the various assets to the site, and using the Nextjs Image component to load them on the site.Locally, both on dev and production-build, the images are loaded, however when deployed to Amplify, the .pngs return 500s when queried.
Strangely, the .svgs are loaded fine.
Expected behavior
The static images are loaded and available.
Reproduction steps
app
dir enabled.index.js
file.Code Snippet
Log output
aws-exports.js
No response
Manual configuration
No response
Additional configuration
No response
Mobile Device
No response
Mobile Operating System
No response
Mobile Browser
No response
Mobile Browser Version
No response
Additional information and screenshots
No response
The text was updated successfully, but these errors were encountered: