aws-amplify
#######
Hi @monjurulbjit521 👋 , thanks for reaching out to us!
I was able to reproduce a similar behavior while trying to preview the website URL (for a sample Next.js app) in the Line Messenger mobile app. I am investigating into this further to narrow down the root cause of this behavior and will keep you posted with any updates.
@Jay2113 Thanks for your support. I wanted to bring an interesting observation to your attention regarding our Amplify access logs. Upon reviewing the logs, I noticed a consistent pattern where requests with the user agent "facebookexternalhit/1.1;line-poker/1.0" receive a 400 status code from Amplify. This particular information could be valuable in your investigation.
As the user agent suggests, these requests are likely associated with Facebook and LINE crawlers. It seems that this behavior might be the reason behind the URL preview functionality not working as expected when our application is hosted on Amplify. We have tried different AWS accounts but it seems that the same 400 status code same user agent.
