-
Notifications
You must be signed in to change notification settings - Fork 26.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Next.js App Router doesn't work with google cache (http://webcache.googleusercontent.com/) #55231
Comments
also the same problem with nextjs.org http://webcache.googleusercontent.com/search?q=cache%3Ahttps%3A%2F%2Fnextjs.org&oq=cache%3Ahttps%3A%2F%2Fnextjs.org&gs_lcrp=EgZjaHJvbWUyBggAEEUYOTIGCAEQRRg60gEIMzkxOGowajSoAgCwAgA&sourceid=chrome&ie=UTF-8 this problem happend not every render |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
@pogran I am facing the same issue, the webcache always behave in unexpected ways (different after a refresh or sometime after a click event...) eventhough everything seems fine in the live version. Same goes for the Nextjs website, which also lead me to believe that this isn't some kind of misconfiguration: After replicating Google webcache site locally to run nextjs in dev mode, I got the following errors: Page Router: App Router: On other websites using Page Router, I saw a different error but the rendering is stable:
As opposed to 423 and 418 minified React error when using the App Router. |
@Gunt3r-Tp Page router is working more stable than App router. And as I see sites with App router don't have problem with seo. with page router they have problems. don't want to use depricated page router because seo. mb its connected with document.baseURI as you told . As I saw some sites in cache load great and after 2-3 sec they recieve this errors 423 and 418 and after that we have view without css |
This comment was marked as off-topic.
This comment was marked as off-topic.
@timneutkens but i also have bad view in screenshot view tab... examle my site https://xn--80afhl4affaesa.xn--80asehdb/ . in devtools i don't have errors. i think fonts errors it doesn't matter i don't understand how to solve this problems ... |
Try disabling JavaScript. Could be that you're using a css-in-js library and it's not set up correctly for example. |
@timneutkens The same result ... |
@timneutkens I also have vercel code https://harry-potter-frontend.vercel.app/ and here disable javascript have another behaviour and nothing dislay |
That's because JS is required for hydration for that case (suspense boundaries and such). |
This comment was marked as off-topic.
This comment was marked as off-topic.
@pogran could you please add a minimal reproduction of your own that simply reproduces the issue you are having? Please don't just point to a full/complex codebase. The less code/dependencies the better. This could help the investigation greatly, avoiding any external factors. Note: Please refrain from tagging the maintainers for a quicker reply, as it might have the opposite effect |
@balazsorban44 the issue seems to happen with any starter project that use create-next-app with app router enabled. As mentioned above, the ai chat sample, which uses the default nextjs configurations, is also affected by this. |
any ideas how to solve this? |
@balazsorban44 @timneutkens this problem annoying. I don't have any errors when I use also vercel, but with google console I see problems... |
Unfortunately on the same track, waiting badly for this to be fixed |
I am facing this issue. Wherein I am getting Client side Application error, when I am trying to open my website with cache:https://bikes.tractorjunction.com Any help will be appreciated. |
This issue needs to be fixed asap. Google will hate NextJS projects. How can we fix this issue? I've migrated my Next App from pages directory to app and this started to happen. When I click cache in google i can see my website for 1 sec and then getting these errors. |
@timneutkens this is awful issue. At least the next.js site doesn't throw the Application error: a client-side exception has occurred (see the browser console for more information). but our own site does. I haven't figure out yet how to opt out this "application cache error feature". The latest and stable next.js is using https://webcache.googleusercontent.com/search?q=cache:FtWV3LZVkTsJ:https://www.ridestore.se/skidjackor-dam&hl=en&gl=it @jrsakizci @nitinTJ thank you guys, it's strange the other devs ignore it |
Facing same issue |
any news about this issue? We facing the same problems.... |
@Gunt3r-Tp, can you explain how to run it locally? 🤔 |
Maybe there is no more need to this anymore since Google removed caching. https://twitter.com/searchliaison/status/1753156161509916873 |
Hi everyone! Since Google removed this, I will going ahead with closing this issue. Feel free to create a new bug report if something similar arises! |
This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
Link to the code that reproduces this issue or a replay of the bug
https://github.com/vercel-labs/ai-chatbot
To Reproduce
Go to cache page http://webcache.googleusercontent.com/search?q=cache%3Ahttps%3A%2F%2Fchat.vercel.ai&oq=cache%3Ahttps%3A%2F%2Fchat.vercel.ai&gs_lcrp=EgZjaHJvbWUqBggAEEUYOzIGCAAQRRg7MgYIARBFGDwyBggCEEUYOtIBCDQxMDFqMGo0qAIAsAIA&sourceid=chrome&ie=UTF-8 and see a lot of errors in devtools
Current vs. Expected behavior
this not ok behavior only in google cache http://webcache.googleusercontent.com/search?q=cache%3Ahttps%3A%2F%2Fchat.vercel.ai&oq=cache%3Ahttps%3A%2F%2Fchat.vercel.ai&gs_lcrp=EgZjaHJvbWUqBggAEEUYOzIGCAAQRRg7MgYIARBFGDwyBggCEEUYOtIBCDQxMDFqMGo0qAIAsAIA&sourceid=chrome&ie=UTF-8 and see a lot of errors in devtools
In real site everything is ok https://chat.vercel.ai/
Verify canary release
Provide environment information
Which area(s) are affected? (Select all that apply)
App Router
Additional context
Also I can show my real project with the same problems
NEXT-1810
The text was updated successfully, but these errors were encountered: