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. With beta.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 URL http://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:
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.12the app renders correctly and no issues arise. Withbeta.13the 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/fion 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.18beta.12->beta.13)