Main branch metadata corrupted โ€” empty name field, merge blocked, 99% empty merge snapshot

Troubleshooting

I'm stuck with what looks like server-side corruption on my main branch and hoping someone here has seen this.

The symptoms:

1. My main branch's record has an empty name field (is_main_branch: true, but name: ""). All my other branches have normal names.

2. Merges into main fail with either "Cannot merge: UNCOMMITTED_CHANGES on branch [ID]" or "No branch named 'main'".

3. The "Branching Options" menu doesn't open at all in the UI โ€” clicking the branching icon shows nothing. I'm the project owner, so it's not a permissions issue.

4. When I did manage to open a merge session, the base snapshot for main came back 99% empty โ€” 1125 of 1135 files with zero bytes, and entire sections missing (collections, theme, app-state, authentication). I did NOT run merge commit, given the obvious data-loss risk.

The odd part: main itself loads and renders perfectly in the editor. All pages display fine, commit history is intact. Inspecting the project record directly returns full content (25 pages, 9 collections). It seems to be specifically the branch's own identity record that's broken, not the project data.

I have about a week of work on a feature branch that I can't promote to main.

Has anyone seen a branch's name field get blanked like this? Is there any user-side fix, or does this always need FlutterFlow support to repair server-side?

Also โ€” would a Branch History revert on main be worth trying, or is that risky against a branch with broken metadata?

What have you tried so far?

- Committed on both branches to clear stuck uncommitted-changes flags (this did clear them, and let a merge session finally open)

- Tried merging with the target branch omitted, letting the server resolve main via parent linkage โ€” this bypassed the name lookup, but still hit the underlying issue

- Verified I'm the project owner (ruled out permissions for the missing Branching Options menu)

- Re-ran the merge snapshot check two days apart โ€” identical 99% empty result both times, so not transient

- Emailed [email protected], no response yet

- Searched existing GitHub issues (found #6715, similar symptoms, closed as can't reproduce)

- Backed up everything locally before touching anything

Did you check FlutterFlow's Documentation for this topic?
Yes
5
2 replies