Yes, this issue is mostly occurring in Vercel deployments. The following thread has some suggested fixes: