Repository navigation
Browser stuck on white screen when accessing dev server before compilation finishes #191957
Description
Run run -d web-server --web-port 5000 and then immediately go to http://localhost:5000 in your browser. The browser will attempt to load the flutter app (I see the blue loading indicator), but then the loading indicator disappears, nothing happens and I am stuck with a white screen. I can see in the chrome inspector that it correctly loaded the index.html of the flutter app, but it doesn't show any kind of error or anything. Just a blank page. I have to refresh the page to actually see my app.
Underlying problem is probably that at the time I hit http://localhost:5000 in my browser compilation hasn't finished yet in the dev server. However, that shouldn't leave me stuck with a white page. Either while the server is not ready yet it should return some kind of 5xx error HTTP status code or - even better - it should continue to show the blue loading indicator until compilation is done and then show me the app. The latter would probably be preferred.
Activity
mbcorona commentedon Aug 28, 2026
Hi @goderbauer, thanks for the report.
Reproduced on macOS: loading the page during the "Waiting for connection from debug service" phase shows the loader briefly, then a blank white screen with no automatic recovery once compilation finishes (a manual refresh is required).
Routing to the web team for evaluation.
[flutter_tools] Pause web server requests until initial compilation f…
[flutter_tools] Pause web server requests until initial compilation f…
[flutter_tools] Pause web server requests until initial compilation f…
[flutter_tools] Pause web server requests until initial compilation f…
github-actions commentedon Sep 12, 2026
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.