Skip to content

[Mac desktop] “Error loading projects” after forced update to 6.0.10 + [Web] sudden “Set Form Field action” errors on untouched widgets #5966

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
1 of 2 tasks
FajneIO opened this issue Jun 10, 2025 · 4 comments
Assignees
Labels
status: needs triage A potential issue that has not been confirmed as a bug.

Comments

@FajneIO
Copy link

FajneIO commented Jun 10, 2025

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

🖥️ Mac desktop app
• Updated via in-app prompt. After restart the app shows a modal:
“FlutterFlow 6.0.5 is currently the newest version available (You are currently running 6.0.10).”
• Clicking “OK” drops me on the Projects screen with the banner:
“Error loading projects… We have been notified and will address the issue immediately.”
• Hitting “Retry” does nothing – project list never appears.

🌐 Web (Chrome)
• The same project opens, but the Issues panel now lists 4 identical errors that appeared on their own:
“Set Form Field action for is trying to set a field that doesn’t exist or is dynamic.”
Affected widgets (no recent edits on any of them):

  • Wyslij
  • Wyslij|Nagranie
  • Czat
  • (one more – see screenshot)
    • App still runs, but these errors block build & deploy.

Expected Behavior

🖥️ Mac desktop app
• The updater should install a version that the backend accepts, or at least still let me see my projects.

🌐 Web (Chrome)
• Existing Form Field actions that were valid yesterday should remain valid today; no phantom errors on untouched widgets.

Steps to Reproduce

🖥️ Mac desktop app

  1. macOS Sonoma 14.xx on Apple Silicon. Launch FlutterFlow desktop (was 6.0.5).
  2. Accept the “new version available” prompt. App auto-updates to 6.0.10.
  3. Relaunch → modal claims 6.0.5 is newest, I’m on 6.0.10. Click “OK”.
  4. Projects page appears → “Error loading projects… Retry”. Retry loops forever.

🌐 Web (Chrome)

  1. Open Chrome (v125) → https://app.flutterflow.io → same account.
  2. Select the project (ID: xxxxxxx).
  3. Wait for load. Issues panel instantly shows 4 ×
    “Set Form Field action for is trying to set a field that doesn’t exist or is dynamic.”
  4. No recent schema changes, no edits to those widgets since last successful build (≈ 24 h ago).

Reproducible from Blank

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

Bug Report Code (Required)

ITFXhfHl8c1NobVE7ZDLLMdviWAwGUQFUOdEl95Hd0gdCOPrBqQqP+DCQxZvXsOjaVNcMGKkoFMzwvzvieHXEvQDEE+dQKI+zc9ucgzee2imRKbUCs+ePXR7O5lnC0C05rSRgxRBAONoSVoewFyUCdytEyjDIuu/Zwh9f6PHaOI=

Visual documentation

Image Image

Image

Environment

- FlutterFlow version: 6.0.10
- Platform: Web and Mac
- Browser name and version: Chrome 137.0.7151.69
- Operating system and version affected: MacOS 15.5

Additional Information

No response

@FajneIO FajneIO added the status: needs triage A potential issue that has not been confirmed as a bug. label Jun 10, 2025
@adominicci
Copy link

Sam issue here.

Image

@adominicci
Copy link

Projects came back but it deleted the branch I was working on. Also removed my entry and logged in page. Disabled some actions in buttons. Overall a big mess!!!

Copy link
Collaborator

Hi there! Just checking in—are you still experiencing this issue?

@Alezanello Alezanello self-assigned this Jun 10, 2025
@FajneIO
Copy link
Author

FajneIO commented Jun 11, 2025

Thanks for checking in. The issue is no longer occurring on either the Mac desktop app or the web version—projects load fine and the previous form-field errors are gone. Appreciate the quick fix!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: needs triage A potential issue that has not been confirmed as a bug.
Projects
None yet
Development

No branches or pull requests

3 participants