Dear Prismic team I set up a new Next.js App Router project using your setup command npx @slicemachine/init@latest and walking trough your step by step setup guide. In previous versions, I never had issues deploying the site to Vercel and setting up Prismic Webhooks to trigger redeploys. With thi…

Hello everyone! I wanted to join the conversation as I built the Prismic website using Next.js. I've encountered similar issues as all of you have reported after migrating to app router. I've tried various solutions over the past few months. However, since version 14.0.2 , we haven't experienced a…

So I guess that adding the accessToken and re-doing the webhook solved my problem. I hope that this can help you guys

I've gone down a similar rabbit hole here, and found a decent solution with Vercel. The new prismic/next/isr fetch() cache setup was working great; updates in Prismic were invalidaiting the Vercel correctly via the /api/revalidate call. However, at build time I was getting "repo not found" errors …

[image] kyle: rm -rf .next/cache/fetch-cache && next build This was helpful. We had a similar situation. When there is multiple [:uid]/page.js files, e.g. /[:uid]/page.js and /some-path/[:uid]/page.js It seems like subsequent createClient() calls trigger a not-found repo error. There very we…

Another option is to use the Environment Variable VERCEL_FORCE_NO_BUILD_CACHE with a value of 1. You can find limited info on that here . This has solved the issue for me on multiple projects. Edit: After another day of dev the error RefExpiredError: The provided ref is no longer accessible, it has …

Perhaps it would be helpful, if you could extend the Next.js / Deploy documentation with the most proven deployment methods (in addition to the blog post ). Especially for those who are new to Prismic and the App Router, it might be difficult to find the best way to deploy the projects. I now use o…

Hey everyone, We've opened an issue on the Next.js GitHub repository. Please feel free to upvote this issue and follow along for updates: [image] Inconsistent caching with `revalidateTag()` and Vercel Data Cache ·... Hi Vercel team, I’m Angelo from Prismic. I maintain Prismic’s Next.js…

I'm now also facing caching issues on Vercel in Next.js applications (v14.0.3) using the pages router. Editing content in Prismic triggers a complete rebuild but the new contents are missing. This also happens with the following suggested option: [image] kyle: "scripts": { "build": "rm -r…

I have updated to version 14.0.4, and the cache issues have disappeared

That's wonderful news! Thank you for letting us know. :pray: Did you disable the build cache with VERCEL_FORCE_NO_BUILD_CACHE=1 earlier because of deploying outdated caches? If so, have you attempted to remove it as well? Samuel

Caching issue with Next.js App Router - Vercel Deployment

Developing with Prismic

alfredo.gtz92 (Alfredo Gutiérrez) September 16, 2023, 9:58pm 11

I reconfigured the webhook from vercel to prismic and it is now working as expected.

Topic		Replies	Views
The provided ref is no longer accessible, it has expired Developing with Prismic nextjs	2	210	September 13, 2024
Error fetching content "The provided ref is no longer accessible" Developing with Prismic nextjs	17	1337	June 4, 2024
Troubleshooting: Caching with Next.js & Vercel FAQs nextjs	0	533	August 28, 2024
Next.js Vercel revalidation error Developing with Prismic	7	539	September 18, 2024
Ref not found. Ensure you have the correct ref and try again Developing with Prismic nextjs	4	2108	December 18, 2023

Caching issue with Next.js App Router - Vercel Deployment

Related topics