Delayed changes slowing down debugging

A few platform updates ago I noticed that I couldn't just make a change and hit the instant reload in test mode, as it 99% of the time hasn't actually saved the last few changes so you have to refresh again. I've had to start changing some text or a visual queue to make sure all the changes have been saved correctly so I know when an error occurs it's based on the new changes and not the same error that showing up cause the changes weren't saved yet.

It's not an internet speed issue as I'm almost always on +100Mbps.

It seems like something small but when you have to double refresh or wait an indeterminate amount of time to refresh once 100+ times a day when debugging it's a huge waste of time.

I'm now running into it sometimes when pushing to GitHub, when I pull it down on my desktop to test on a device it also sometimes is missing the changes to the code (luckily VSCode usually picks it up if it leaves an error in the code, but not always the case).

There really needs to be a visual cue in the app that tells you when all changes have been committed to reduce the wasted time from the app being slow with saving changes and slowing down the development and debugging process.

Added it to the wishlist:

https://community.flutterflow.io/general-wishlist/post/a-change-status-or-change-commit-log-rGW6H8x3xql1g5y

9
9 replies