Desktop app pinned to 6.4 cannot open project when last-edited branch is on newer version

[Wojtek-G]

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

When a project has multiple branches pinned to different FlutterFlow versions and the desktop app is pinned to 6.4, the desktop app always attempts to open the last-used branch. There is no option to select a different branch when opening a project from the desktop app.

This creates issues for team collaboration across multiple branches. Additionally, the project list does not update reliably or immediately after branch changes are made in the web app. Because of this, the desktop app may continue trying to open an incompatible, last-used branch, even after the user switches activity to a compatible branch (e.g., main).

As a result, users can end up in a situation where:
• the desktop app is compatible with one branch,
• but always attempts to open a different, incompatible branch,
• and provides no way to switch branches within the desktop app,

effectively preventing access to the correct branch in the desktop app and forcing the user to use the web app instead.

Expected Behavior

•	The desktop app should allow the user to choose which branch to open.
•	If at least one branch is compatible with the desktop app version (e.g. main on 6.4.134), the project should be openable in desktop.
•	Opening a project should not depend solely on the last-edited branch.

Steps to Reproduce

1.	Open the FlutterFlow desktop app (6.4.134).
2.	Go to the project list.
3.	Click the project that last used branch is other than 6.4.134, but has branch that has 6.4.134 but is not last edited one.
4.	Desktop app attempts to open the last-edited branch.
5.	Because this branch is pinned to different version, the desktop app:
•	does not open the project
•	redirects the user to the FlutterFlow web app instead.

Reproducible from Blank

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

Bug Report Code (Required)

IT4wlsjfz4p1xOpE17rUbMFvoCUvCDo3RoI3mMFuVis8GZT0B4kcYs+kfklUOc+od1Z2I2GjhnkX/MrIkt/hD+4qaBOeGdVIzc9MaQGWTk+nbrqwBa63b3FPNNFbJkCC1567gB5CIvt1cUI923GUfd6taCvYGb7QPGwRQuaoXdeK2SrDX1iXc2URm05KZDPz

Visual documentation

Environment

- FlutterFlow version: 6.4.134
- Platform: macOS
- Browser name and version:
- Operating system and version affected: 
	•	Current FlutterFlow version: 6.5.3
	•	Project setup:
	•	main branch pinned to 6.4.134
	•	test-new-ff-version branch pinned to 6.5.3
	•	Last edit was made on test-new-ff-version
	•	Desktop app installed: 6.4.134

Additional Information

No response

[musabsokkar]

i have same issue

[Juansarmi]

Hi!
I’m sorry you’re experiencing this issue. At the moment, this is a limitation of FlutterFlow, meaning it is expected behavior, so I’ll be closing this issue for now.

That said, I’ll share your feedback with the team to explore the possibility of adding this as a feature request. If that moves forward, I’ll reopen this thread and let you know.

Best regards