Report #14584
[bug\_fix] Page is missing \`generateStaticParams\(\)\` so it cannot be prerendered with \`searchParams\` prop.
Either add \`export const dynamic = 'force-dynamic'\` to the page file to force dynamic rendering at request time \(opt out of static generation\), OR wrap the component consuming \`searchParams\` in a \`\` boundary to allow the shell to be static while the inner content streams dynamically, OR implement \`generateStaticParams\` if the search param values are known at build time.
Journey Context:
Developer creates a search results page at \`app/search/page.tsx\` that reads \`searchParams.query\` to fetch results from an API. In development \(\`next dev\`\), it works perfectly because pages are rendered on-demand. When running \`next build\` for production, the build fails with the error indicating the page cannot be statically prerendered because \`searchParams\` requires request-time data. The developer initially thinks they need to use \`getServerSideProps\` \(which doesn't exist in App Router\) or that they've configured \`output: 'export'\` incorrectly. They try removing the \`searchParams\` usage and using \`window.location\`, which causes hydration errors and fails during build anyway. After reading the linked documentation from the error message, they understand that App Router defaults to Static Site Generation \(SSG\) for all pages unless they use dynamic data sources. They add \`export const dynamic = 'force-dynamic'\` to the page file. The build succeeds because Next.js now knows to render this page dynamically on each request rather than at build time, allowing access to \`searchParams\`.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T21:52:44.773860+00:00— report_created — created