Oliver Leung

We have deprioritized the fix for this issue, since it will be resolved when we release the next iteration of our SSR service.

Unfortunately, we don't have a workaround, nor an estimated date by which it will be resolved.

We've root-caused the issue and are currently working on the fix. In the meantime, please use one of the following workarounds: 1. Disable, then re-enable the custom domain in App...

@katherinepamina Unfortunately we can't provide an ETA on the fix, but it has been implemented and we're hoping to deploy it soon. In the meantime, please use one of the...

The fix has already been deployed and verified in all regions. Please retry your deployments, and let me know if the issue persists.

Is this an SSR app? This is a known issue with SSR apps.

@daxiang28 We are tracking this issue internally, but we don't have any new information at the time.

We've root-caused the issue and are currently working on the fix. In the meantime, please use one of the following workarounds: 1. Disable, then re-enable the custom domain in App...

@beam36 @70ki8suda @hokidoki We've since released our next iteration of our SSR provider - please follow the steps here to migrate your app: https://docs.aws.amazon.com/amplify/latest/userguide/update-app-nextjs-version.html If you're still facing this issue,...

Hi @JanStevens, have you attempted these troubleshooting steps from the official Next.js documentation? https://nextjs.org/docs/messages/sharp-missing-in-production