Hi Leigha Reid, Pooja Bhaumik and FlutterFlow Support Team,
My Third Bug Report: FlutterFlow, Are You Even Testing These Updates?
This is now my third post reporting critical bugs caused by the November 13, 2024, FlutterFlow update. At this point, I have to seriously question the level of testing—or lack thereof—being conducted before these updates are released.
After the Execute Callback issue I previously reported, I have now encountered another serious problem: the Refresh Database Request action no longer works as intended. This feature, which previously updated records in real-time after an insert, update, or delete, has become completely unreliable.
Here’s what happens:
When I attempt to use the Refresh Database Request, the updated records do not appear in the list until I manually reload the page or component. This behavior is unacceptable, especially for features that rely on real-time updates to provide a seamless user experience.
These issues point to potential backend or state synchronization problems introduced in the update.
FlutterFlow QA Needs Improvement
I am left wondering: how does such a fundamental feature—used by countless developers—break without being caught in testing? This is not an isolated case, and the cascading issues from this update suggest a serious lapse in quality assurance.
Developers Pay the Price:
Every hour I spend debugging and finding workarounds for these bugs is time I should be dedicating to advancing my projects. These bugs disrupt workflows, cause delays, and erode trust in the platform.
I expect the FlutterFlow team to not only fix these issues promptly but also to take a hard look at their testing processes. Updates should enhance the platform, not break core functionalities.
For developers relying on FlutterFlow for mission-critical applications, this level of instability is unacceptable.
FlutterFlow team, please prioritize quality and reliability moving forward. We depend on you, but you need to meet that responsibility with better testing and accountability.
My projects are on hold waiting for these problems to be fixed!
https://github.com/FlutterFlow/flutterflow-issues/issues/4916