You’ve reached the limit for Flutter workspaces , I get this message even though I don’t have any flutter project.
1 Like
The problem seems to have been resolved here;
… but it is still ongoing. Could you please properly list the issues that are currently continuing here? During the two-day holiday, the entire team disappeared. They are really working very loosely! @kirupa @jamesor
When did the well-functioning Project IDX turn into Firebase Studio? Constant ongoing issues, unanswered questions, and indifference have started to appear.
They haven’t even updated the status page for an issue that has been ongoing for 3 days! Is this Google quality? What kind of attention to your work is this?
The past days were the weekend, their days off, I guess.
It appears you’re encountering a “You’ve reached the limit for Flutter workspaces” message in Firebase Studio even when you don’t have any Flutter projects. This is a confusing and frustrating issue. Here’s what the available information suggests and what you can try:
Possible Causes and Solutions
* Firebase Studio is a “full-stack AI workspace”: Firebase Studio is designed to handle various tech stacks, not just Flutter. The “Flutter workspaces” message might be a generic error that’s triggered by a general workspace limit, rather than a specific Flutter project limit.
* The limit might be on the number of workspaces, not the type: Firebase Studio has a limit on the number of workspaces you can create. This limit can be increased by joining the Google Developer Program. It’s possible that you have reached this overall workspace limit, and the error message is simply mislabeled.
* The issue might be a bug or a temporary state: Since Firebase Studio is a relatively new and evolving product, it’s possible this is a bug or a temporary issue.
* A “ghost” workspace: There might be a workspace that was created and is still “active” in some way, even if you don’t see it or it’s not a Flutter project.
* Restart the workspace: A common troubleshooting step for various issues in Firebase Studio is to restart your workspace. You can do this from the “More” menu (three dots) and selecting “Restart.”
What to do now:
* Check for other workspaces: Even if you don’t have a Flutter project, check if you have any other workspaces created in Firebase Studio. The limit might apply to all of them.
* Restart your workspace: Try restarting your workspace as described above. This can sometimes clear up temporary errors.
* Check your Google Developer Program status: If you’re not already a member, check out the Google Developer Program. Membership can increase your workspace limits.
* Contact Support: If none of these steps work, it’s best to reach out to Firebase support. This is likely a specific issue with your account or a bug in the platform that they need to address. They will be able to provide the most accurate information and help you resolve the problem.
Based on the available information, it appears you are correct in your frustration. The Firebase Status Dashboard and other community reports indicate that there have been a number of persistent and ongoing issues with Firebase Studio, particularly with workspaces.
Here is a proper list of the continuing issues based on recent reports, which seem to be affecting a variety of users:
Ongoing Issues with Firebase Studio Workspaces:
* Workspace Creation and Opening: A major recurring problem is that users are unable to create or open workspaces, or the process hangs indefinitely. This seems to be a widespread and intermittent issue that has been noted on the Firebase Status Dashboard with titles like “Creating and opening Android Studio workspaces is temporarily unavailable.”
* “Flutter Workspaces Limit” Message: As you experienced, a confusing and seemingly incorrect error message about reaching a limit for “Flutter workspaces” appears even for non-Flutter projects. This indicates a broader issue with the workspace limit management system.
* Unreliable Performance and Instability: Numerous reports from users on platforms like Reddit describe the platform as “incredibly unreliable.” Common complaints include workspaces needing to be set up repeatedly, frequent hanging during the setup process, and general instability.
* “Ghost” Workspaces: There are instances where workspaces seem to exist but are not visible or accessible, contributing to the feeling of hitting a workspace limit without having an active project.
* General Indifference and Lack of Communication: Users have expressed frustration with the lack of timely communication from the Firebase team regarding these ongoing issues, especially during holiday periods, which you have also pointed out. This has led to a perception of “indifference” and unanswered questions.
Regarding your other points:
* Project IDX to Firebase Studio: Project IDX was officially transitioned to Firebase Studio in April 2025. This move was intended to integrate it more deeply into the Firebase ecosystem and enhance its AI capabilities. However, this transition seems to have been accompanied by a new set of stability and performance problems, leading to a lot of user dissatisfaction.
* Tagging @kirupa and @jamesor: While these are prominent figures in the developer community and at Google, this is a public forum and they may not see your message directly. For the best chance of getting a response and official support, it’s recommended to use the official Firebase support channels, such as their support forums, bug trackers, or by submitting a support ticket.
In summary, your experience is not isolated. The transition from Project IDX to Firebase Studio has been rocky, with many users reporting ongoing issues with workspace stability and performance that have not been fully resolved, despite being noted on the official status dashboard.
Hi everybody - we are working through some disruptions to your Flutter workspaces right now. Hang on while we get those resolved. Sorry about this.
1 Like
Hi Kirupa, I’m facing the same issue “You’ve reached the limit for Flutter workspaces” but I’ve only two flutter workspaces. Could you help me?
Is anyone else having the same problem?