That strongly suggests the problem is not on the client side. It suggests FlutterFlow does not properly initialize or attach SDK commit tracking for projects created through its own UI, which means the first SDK push cannot succeed.
If that is the case, then the current product story is misleading:
- existing projects appear to be accessible from the SDK,
- the documentation does not clearly state that UI-created projects may be unable to perform a first SDK push,
- the error message gives no actionable explanation,
- and there is no clearly documented migration or initialization path.
So the issue is bigger than one 404. It calls into question whether FlutterFlow AI / SDK can actually be adopted on real pre-existing projects, as opposed to only working reliably on projects created through the SDK flow itself.
The questions that need clear answers are:
- Is "flutterflow ai run" officially supported on projects originally created in the FlutterFlow UI?
- If yes, is this 404 on first push a known backend bug?
- If no, why is that limitation not stated clearly in the docs and product guidance?
- Is there any supported way to initialize SDK push history for an existing UI-created project?
If anyone here has successfully used FlutterFlow AI / SDK on a UI-created project, I’d be interested to know whether that worked without intervention, or whether some undocumented setup was required.
GitHub issue with full repro: #7257 https://github.com/FlutterFlow/flutterflow-issues/issues/7257
