CRITICAL: Project ZAQ100 disappeared during global "Project Access Restricted" bug

[Zaq103]

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

I am experiencing the global bug where the dashboard incorrectly shows 0 projects while reporting a 2-project limit. In an attempt to fix this and regain access to my work, I cleared my Trash. Now my primary project ZAQ100 is completely gone from the dashboard.

This project represents months of work for a community project. Since this happened during a confirmed platform bug, I urgently request a manual restoration of my project.

Account Email: agtereren@gmail.com
Project Name: ZAQ100
Time of incident: 7 PM

Expected Behavior

The project "ZAQ100" should be visible in the dashboard and accessible for editing. Since I only have one project on my free plan, there should be no "Project Access Restricted" warning or restriction.

Steps to Reproduce

1. Log in to FlutterFlow with one active project.

2. Encounter the "Project Access Restricted" error (showing the "2}" bug).

3. Navigate to 'Trash' to clear ghost/duplicate projects in an attempt to fix the access bug.

4. Permanently delete a project from Trash.

5. Return to Dashboard to find that the primary project "ZAQ100" is now missing or inaccessible.

Reproducible from Blank

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

Bug Report Code (Required)

I cannot access the project editor to generate a code because of the "Access Restricted" bug

Visual documentation

Environment

- FlutterFlow version: 
- Platform:
- Browser name and version:
- Operating system and version affected:

Additional Information

No response

[momininkitabcasi]

I have the same problem.
I'm on the Basic plan.
I also get an error with Firebase...it happened after the last FF update.

[MaxFF1800]

This Should be fixed :)

[Zaq103]

@MaxFF1800 Thank you for the fix! The access restriction is gone, but I have a major problem: my primary project ZAQ100 is completely missing from both the Dashboard and the Trash.

During the platform instability (the 2} bug), I tried to clear my Trash to regain access, and I fear the project was lost in the process. Since this happened during a confirmed system bug, could you please manually restore ZAQ100 for me? It is months of work.

Account: agtereren@gmail.com
Project Name: ZAQ100

[Zaq103]

@MaxFF1800 Thank you for the fix! The access restriction is gone, but I have a major problem: my primary project **ZAQ100** is completely missing from both the Dashboard and the Trash. During the platform instability (the 2} bug), I tried to clear my Trash to regain access, and I fear the project was lost in the process. Since this happened during a confirmed system bug, could you please manually restore **ZAQ100** for me? It is months of work. Account: ***@***.*** Project Name: ZAQ100 wt., 10 mar 2026 o 21:27 Max ***@***.***> napisał(a):

…

*MaxFF1800* left a comment (FlutterFlow/flutterflow-issues#6981) <#6981 (comment)> This Should be fixed :) — Reply to this email directly, view it on GitHub <#6981 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B46TUSH7X6VWFIHG7RMTHKL4QB3D7AVCNFSM6AAAAACWNOFQT2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DAMZUGI2DGNRTGU> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[momininkitabcasi]

Hello FlutterFlow Team,

After the latest FlutterFlow update, I started experiencing issues in all of my projects.

Currently, I cannot download the APK. At the same time, the system shows the following warning:

“Firebase indexes not properly deployed for your project. Tap on settings to view deployment options.”

I have already tried deploying the indexes from the settings, but the warning still remains and the problem persists.

This issue appeared immediately after the latest FlutterFlow update, and it is happening in both of my projects.

Could you please investigate and fix this problem?

Thank you.

[Alezanello]

I’m glad everything is working as expected now! I’ll go ahead and close this issue, but if you encounter anything else, please don’t hesitate to open a new one!

@momoninkitabcasi please open a separated github issue with your Bug Report Code in order to check it your project issues