Next.js Static Export: Dynamic Route Missing generateStaticParams
Output project: export is built until it passes through the dynamic route and reports missing generationStaticParams. Static export cannot generate new pages on demand, so it needs a set of addresses known during the build.
How to identify the source of the problem
Check the output setting in next.config and a list of routes with segments in square brackets. Determine whether the data of all parties exists at the time of construction, or are taken upon request.
Compare the message from the console with the result of the production compilation and the condition after the page has been refreshed.
Repair steps
Add genericStaticParams returning a set of parameters when the set is known and finished. If the addresses are to be created dynamically, remove static export and use hosting supporting server rendering.
How to Test Solution
After the build there is HTML for each intended service, and the new service requires the intended publication procedure.
Security and restrictions
Do not set dynamicParams=true as an alleged repair of static export restrictions.