Hello, I'm encountering an error when attempting to run a build process after introducing a new page_type. The issue seems to be resolved when I generate a new access token, but I'm uncertain about the cause. I'm seeking expert assistance to understand and address this problem.
Do you have at least one document published in each document type? An empty type can throw this sort of error, which could also result in previews redirecting to the home page as you described in your other thread.
Hie, i am kind of new to prismic, i recently did a project with nextjs 14 and prismic, i have successfully deployed the app on vercel but i recently acquired a custom domain and was hoping to use GitHub pages instead but when trying to deploy the same project with github actions i am getting these errors. The same code builds with no errors on my local host as well as on vercel but fails with the highlighted errors on GitHub when i try to use github actions.
Error: Page with `dynamic = "error"` couldn't be rendered statically because it used `request.url`.```
Export encountered errors on following paths:
/api/exit-preview/route: /api/exit-preview
/api/preview/route: /api/preview
Error: Process completed with exit code 1.
/**Here is my nextjs.config.mjs */
/** @type {import('next').NextConfig} */
const nextConfig = {};
export default nextConfig;
As far as I understand, GitHub pages only allows static HTML or client-rendered websites. With GitHub, you can't have any server functions. The paths listed in the error message both run logic on the server, and so they wouldn't work on GitHub pages. If you delete those files, it might work, but you won't be able to use Prismic previews.