(This may be unique to Anthony but I did try hard to remove state and reproduce cleanly. Noticed first yesterday, I think. Dumping what I know.)
SSR content renders correctly then gets replaced by "500: Internal Error" during client-side hydration. Affects all pages (tested /, /about). The nav/shell remains; only page content is replaced with the error.
Environment:
Chrome 146.0.7680.164 (stable, no modified flags)
Android 14, Pixel 5 (Build/UP1A.231105.001.B2)
V8 14.6.202.26
Confirmed not the cause:
- Cookies / localStorage / site data (reproduced after full clear + phone restart)
- Network issues (HTTP responses are all 200, verified via chrome://net-export/ capture)
- Chrome flags (none set, reproduced after flag reset)
Works fine in:
- Firefox on the same device
- Chrome on other machines
What I could not obtain:
The actual JS console error. Android Chrome has no local DevTools, the #enable-logging-js-console-messages flag produced no output in a bug report logcat dump, and I lacked a USB data cable for remote debugging. Wireless ADB is the next step.
Next steps for anyone reproducing:
If you have Chrome 146 on Android, check if you see the same hydration failure
Remote DevTools (chrome://inspect) would immediately reveal the JS error causing the SvelteKit error boundary to trigger
(This may be unique to Anthony but I did try hard to remove state and reproduce cleanly. Noticed first yesterday, I think. Dumping what I know.)
SSR content renders correctly then gets replaced by "500: Internal Error" during client-side hydration. Affects all pages (tested /, /about). The nav/shell remains; only page content is replaced with the error.
Environment:
Chrome 146.0.7680.164 (stable, no modified flags)
Android 14, Pixel 5 (Build/UP1A.231105.001.B2)
V8 14.6.202.26
Confirmed not the cause:
Works fine in:
What I could not obtain:
The actual JS console error. Android Chrome has no local DevTools, the #enable-logging-js-console-messages flag produced no output in a bug report logcat dump, and I lacked a USB data cable for remote debugging. Wireless ADB is the next step.
Next steps for anyone reproducing:
If you have Chrome 146 on Android, check if you see the same hydration failure
Remote DevTools (chrome://inspect) would immediately reveal the JS error causing the SvelteKit error boundary to trigger