Endless reload loop with pinned version

[Siltyx]

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

My Flutterflow App is Pinned to Version 6.4.
I now get the following Message. (see first visual proof)
The suggested reload does nothing.

Changing the base URL from https://flutterflow-prod-v6-4.web.app/ to https://app.flutterflow.io/ lets me access my project for some time. I cannot remove the pinned version in the settings (it says it did remove the pin but i did not) though at some point i get kicked out Saying this Version is Pinned to 6.4. (see second picture in visual)

Expected Behavior

Either let me Access the Project at 6.4 or let me remove the Pin.

Steps to Reproduce

Just open the project.

I copied the Bug Report code from some sign in page widget.

Reproducible from Blank

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

Bug Report Code (Required)

IT48jPLlvJRPxMNf7ariKcB7/ToRKUs7U40n19VDcEk8J5DaPOxzP/TBaldWUs+0T29PMWKj8Tk0+ffemvz1FcYqAxSubJR9+Ll+cRXiTnOuaKarELqwWW5/DedjIUzG0ZmFhSZAXfJidV4N61OMfOiicz/DNJixIlcaQv38IZKK2SrDX1iXc2URm05KZDPz

Visual documentation

Environment

- FlutterFlow version: incossistent apprently, 6.4 and latest i guess
- Platform: web
- Browser name and version: Chrome  146.0.7680.72
- Operating system and version affected: Windows 11

Additional Information

No response

[Juansarmi]

Hello. I'm sorry to hear you're experiencing this issue. It does not appear to be a consistently reproducible bug, but I was able to confirm this behavior in your project. I will check with our engineering team to make sure this is not a project-specific issue, and I will let you know as soon as I have any updates.

[Siltyx]

Thank you! It also started pretty randomly. We are working as a Two Person Team on this project. But the other developer also says he used the correct 6.4 Version.

[Wojtek-G]

Same here, we’re having issues with a couple of our projects.

Because of this and the issue where we can’t access branches that are pinned/unpinned in the desktop app, we ended up unpinning the projects. We simply can’t move forward with this level of issues in FlutterFlow.

This is really, really bad. A feature that is supposed to help us shield our production projects from problematic FlutterFlow updates becomes unusable when working as a team.

I even had a project pinned to 6.4. We had to update it, but when we selected “Next Stable Version”, it actually downgraded the project to 6.3!

[Siltyx]

I can't even change the Pinned version of my project. It will display unpinned before reverting to the previously pinned version within minutes.

The desktop app problems we have as well!