Can we access your project?
Current Behavior
My main branch's metadata/branch-identity record is corrupted server-side. The project content itself is healthy, but main-the-branch is broken:
- Its name field is empty.
- Its branch-project ID returns "Project not found" (404).
- Any merge into main resolves a 99%-empty base snapshot, so completing a merge would wipe the project.
Evidence: reading main directly (via the trunk) returns COMPLETE — all pages, components, collections present. Resolving main as a merge base returns 1103 of 1113 files empty (99.1%), while my feature branch and the common ancestor are both fully populated. merge auto reported 0 conflicts (a false negative caused by the hollow base).
I have NOT run merge commit, a Branch History revert, or any branch deletion — state preserved, full local backups. An experienced community member reviewed this and agreed: healthy content, corrupted branch metadata. FlutterFlow support directed me here from an email ticket. I can provide the exact project ID, both branch record IDs, and the merge session ID privately.
Expected Behavior
main should carry the full project content and be a valid merge target, so I can promote my feature branch into it.
Steps to Reproduce
- Read main's content directly via the trunk — returns COMPLETE (all pages, components, collections).
- Attempt to resolve main as a merge base (merge from the feature branch into main).
- Observe the base snapshot: 1103 of 1113 files empty (99.1%); feature branch and common ancestor fully populated.
- Inspect main's branch-project ID — returns "Project not found" (404); the main branch record's name field is empty.
Reproducible: reading main directly = healthy; resolving main as merge base = 99% empty.
Reproducible from Blank
Bug Report Code (Required)
IT40psrl8YZPxcdF+biJVu0yiiIvGml+R+UFlcJRaCosfZT2BLMcec/RVERWTemjdFFYMWD8q2oW3OiPuIbhUcc6PTSVfZxj+s8JFArid3KhSrLTFJWgP38lJ8VbI2qx07e7oR5+ItRYL0It702YNe+/QgDBJufaPm08Dq/LZO4=
Visual documentation
Environment
- FlutterFlow version: v7.0.68 (released August 12, 2026)
- Flutter version: 3.38.6
- Platform: Desktop (Windows)
- Browser name and version: N/A (Desktop app)
- Operating system and version affected: Windows 11 (25H2)
Additional Information
No response
Can we access your project?
Current Behavior
My main branch's metadata/branch-identity record is corrupted server-side. The project content itself is healthy, but main-the-branch is broken:
Evidence: reading main directly (via the trunk) returns COMPLETE — all pages, components, collections present. Resolving main as a merge base returns 1103 of 1113 files empty (99.1%), while my feature branch and the common ancestor are both fully populated. merge auto reported 0 conflicts (a false negative caused by the hollow base).
I have NOT run merge commit, a Branch History revert, or any branch deletion — state preserved, full local backups. An experienced community member reviewed this and agreed: healthy content, corrupted branch metadata. FlutterFlow support directed me here from an email ticket. I can provide the exact project ID, both branch record IDs, and the merge session ID privately.
Expected Behavior
main should carry the full project content and be a valid merge target, so I can promote my feature branch into it.
Steps to Reproduce
Reproducible: reading main directly = healthy; resolving main as merge base = 99% empty.
Reproducible from Blank
Bug Report Code (Required)
IT40psrl8YZPxcdF+biJVu0yiiIvGml+R+UFlcJRaCosfZT2BLMcec/RVERWTemjdFFYMWD8q2oW3OiPuIbhUcc6PTSVfZxj+s8JFArid3KhSrLTFJWgP38lJ8VbI2qx07e7oR5+ItRYL0It702YNe+/QgDBJufaPm08Dq/LZO4=
Visual documentation
Environment
Additional Information
No response