-
Notifications
You must be signed in to change notification settings - Fork 27.2k
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
A fully rendered next page is re-rendered to a 404 page after successfull initial render #868
Comments
I know that getting hold of a Safari 8 on Yosemite is a bit tricky but there are free tiers available for browserstack.com that will allow testing this easily. |
Also happening on Safari 9.0.3 and |
Hmm. It's a bug. Getting that browser is the hardest part. |
Guys, found the issue and here's the fix: #870 |
Excellent work @arunoda. Hopefully this will make it to the next beta. :) |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I've been trying to track this down for a day now and I've managed to come up with a small example code and I know the version bump that caused this issue.
This happens in older versions of Safari and Mobile Safari. The newest version of Safari I've found to have this issue is version 8.0.8 that is the only bundled browser for Yosemite. It's not even that old comparing how long Mac's last. I haven't seen this bug in other browsers (Chrome, FF etc.) while testing.
In
beta.12
the app renders correctly and no issues arise. Withbeta.13
the app is first rendered correctly and then very quickly re-rendered to a "404 This page could not be found.". I've tracked that the issue is related to next trying to load a URLhttp://localhost:3000/_next/pages/fi
on Safari that leads to a 404 error that causes the app to render the 404 page. Why this is happening is some kind of internal issue with next, custom server and older Safaris (my best guess).Here's what I can provide to help solve this issue:
beta.18
beta.12
->beta.13
)The text was updated successfully, but these errors were encountered: