Flutter web app sometimes only shows a blank/white page #3465
Things I have tried and didn't fix it:
How i fixed it
After downgrading vscode dart extension from 3.24.2 to 3.23.1 it worked again. I guess there must be a problem in the new dart extension version.
I always had an issue with hot reload since upgrading to null safety months ago. Whenever I try to hot reload(Android studio & vscode), the application disappears and the ios & android simulator goes blank/white screen. Might be connected to this issue might not. I didn't file an issue for that yet. I have searched a long time for a solution to this but couldn't find any
The text was updated successfully, but these errors were encountered:
I don't seem to be able to reproduce this. Can you reliably reproduce this behaviour between those versions? If so, could you capture a log for each by:
You can send the logs to me at email@example.com or attach/paste into gists.
There have been some other strange issues with Chrome (like #3206) but I don't recall any that would be different based on the Dart extension version. If something has changed that caused this, I'd definitely like to understand what.
@JonasKuschel thanks! I think I initially misunderstood the problem - are you saying the app appears then just turns white (like a rendering issue in Chrome), and not that Chrome disappears (which is what I initially thought it was)?
Is there anything in the Chrome developer tools console?
I can't see any obvious reason why this would behave differently in the newer version, although there were some slight differences in the commands used to launch Flutter:
Some of the
Does resizing the Chrome window while it's white make any difference? I have a recollection of @grouma having some issue with white rendering recently, but I can't find an issue that seems to be it now.
Is it possible for me to add the parameters back to the launch file or something to try if thats the problem?
Like this e.g.:
Yep, adding them to
Is the issue completely reliable when switching versions (eg. happens 100% of the time with the new extension version and 0% of the time with the old)? I've had a scan through a diff of those versions, but nothing stands out that might affect debugging functionality that I've found so far.
I'm wondering if this might be related to sending the VM Service extension values back at startup. This is something that was "fixed" by #3426 but caused some other issues (like #3454). I've changed how this works and wonder if that fixes things for you. Could you try the latest nightly build to see if it's still an issue?
If this solves the issue, then I guess it's already fixed and you can just use that version until the next release. If not, we'll need to find a way that I can reproduce it, or we'll have to build something between v3.23 and v3.24 for you to test to see if we can narrow down which change has affected it.
@producttuzmo the issue reported here was fixed - I suspect what you're seeing is a different issue that just happens to have the same symptoms.
Could you please file a new issue with a detailed description of your issue (including SDK/extension versions, what platform/target you're running on etc.), and confirm whether you can reproduce this in a brand new project, or only a specific project.