CRITICAL: Infinite "Version out of date" loop after pushing UI via MCP - Project Completely Locked

[vinicius-rebelatto]

Can we access your project?

• I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.

Current Behavior

After pushing a single page structure via the FlutterFlow CLI using the new MCP protocol (with Claude Code), the web editor became locked in an infinite "Version Out of Date" loop. The project is completely inaccessible via the UI.

Crucial Context & Failed Troubleshooting:

1. I have already contacted support@flutterflow.io. I received the automated troubleshooting checklist, but none of the suggested actions resolved the problem.
2. I fully cleared all site data (cache, localStorage, IndexedDB, service workers) for flutterflow.io.
3. I accessed the platform via a clean Guest Profile and a completely different network (Mobile 4G) to bypass local routing. The loop persists.
4. I successfully forced a remote version bump via the CLI (pushing and deleting a dummy page). The backend commit hash advanced, but the web UI remains deadlocked.
5. Duplicating the project is NOT a viable workaround. This is a production project with extensive Snapshot history and Deploy history that cannot be discarded.
6. I also attempted to open the project using the native FlutterFlow Desktop App. It fails to load the canvas, ejects the session, and forcefully redirects to the web browser URL, which then immediately hits the same infinite loop.

The snapshot restoration menu is inaccessible because the error modal blocks the entire canvas UI. This confirms the issue is a server-side deadlock/corrupted version stamp, not a client-side cache issue.

The project ID is: quero-lar-0wewwb.

Expected Behavior

The web editor should correctly fetch the latest version stamp pushed by the MCP/CLI. If a version mismatch occurs, the UI MUST provide a functional mechanism to force-sync or, at the absolute minimum, allow access to the Snapshots panel to perform a manual rollback. A CLI push should never result in a permanent, unrecoverable lockout of the visual editor.

Steps to Reproduce

1. Initialize flutterflow ai init on an existing project.
2. Connect an agent (Claude Code) via MCP.
3. Instruct the agent to create a new page and push the changes.
4. Open the project in the web editor.
5. The "Version out of date" modal appears and persists through all refresh attempts.

Reproducible from Blank

• The steps to reproduce above start from a blank project.

Bug Report Code (Required)

IT4kh8/l34ZOj7xD7aXxbcFogiksQ2YmTLJMt9VxSUghNbasE7AuZvfRPhNLYteken1feGKJqzkD+ejIhuz2V+4ENRCCfZx5+b5XQQLjRmKtV5CMBaqSSmpAM8JjN36M08Ow2h1/LfVfWWQNw1OhNfCdG3qCf9qOYwx5e6fDbOY=

Visual documentation

Environment

- FlutterFlow version: v6.4
- Platform: Android, IOS and Web
- Browser name and version: Chrome 148.0.7778.96 
- Operating system and version affected: Windows 11

Additional Information

This issue effectively holds my production project hostage. The CLI indicates the project structure is intact (flutterflow ai status), but visual development is impossible. Because duplicating the project means losing all deploy history, I urgently need a server-side reset of the version stamp for project 'quero-lar-0wewwb'.

[Juansarmi]

Hello! 👋

For this type of issue, please reach out to our Support team through the in-app chat or by emailing support@flutterflow.io.

Best regards.

[vinicius-rebelatto]

Cause issue found.

The problem was caused by a routing error in the FlutterFlow dashboard that incorrectly redirected the project to an outdated domain (flutterflow-prod-v6-4.web.app), which is incompatible with updates made via CLI or MCP. This legacy environment triggered the version mismatch loop, while the primary domain (app.flutterflow.io) correctly loads the latest editor version and functions as expected.