I encountered the same issue. Fixed by setting { reactStrictMode: false } in next.config This a temporary workaround until it get fixed.