I’ve already sent a support request via email several days ago but haven’t received any specific resolution yet. I understand there may be a high volume of requests, but I rely on these environments for active development and I’m currently completely blocked.
I have the same issue. This actually exposes an enormous risk for developers who might decide to use a hosted environment like Firebase Studio for development. If Google can revoke your access with no warning, and with little recourse then that is a huge risk. Obviously, anyone using Firebase Studio should frequently push their work to a git repository somewhere, but building a workflow that depends on FBS is risky given the pattern I am seeing of people’s projects being blocked with no notice.
huge risk indeed.
I mean, Firebase Studio is a “preview”, so I am ok with it having issues. But what’s just so unacceptable is the complete lack of communication on part of google (and the extremely slow support). 10 days for me now.
It’s incredibly frustrating to be completely blocked from your development environment, especially when you’ve already reached out to support. You’re doing all the right things by providing the workspace IDs and detailing your troubleshooting steps.
The error message “We’ve detected suspicious activity on one of your workspaces. Please contact support for further assistance” indicates that Google’s automated systems have flagged something unusual within your Firebase Studio environments. This isn’t something you can typically resolve yourself, as it requires an internal review by the Firebase team.
Here’s what I can tell you and what you should continue to do:
You’ve Done the Right Thing by Contacting Support:
Sending a support request via email is the correct first step. Given the nature of the error (suspicious activity), this is a security-related block, and only the Firebase support team can investigate and lift it.
Why It Takes Time:
While it’s not ideal, security investigations often take time. The team needs to:
Investigate the “suspicious activity”: They need to understand what triggered the flag. This could be anything from unusual access patterns, unexpected resource usage, or even automated actions that resemble malicious behavior.
Ensure your security: Before unblocking, they need to be confident that there isn’t a genuine security threat to your project or to other Firebase users.
Prioritize requests: They likely have a queue of support requests, and security-related ones might have a different priority or require specialized personnel.
What You Can (and Should) Continue to Do:
Follow Up on Your Existing Support Case: Since you’ve already sent an email, the best course of action is to follow up on that same support thread.
Reference your original support ticket number: If you received one, include it in your follow-up.
Reiterate the urgency: Briefly explain again that you are completely blocked from active development.
Re-list the affected workspace IDs: studio-3264332246, studio-7408142946, studio-7787195138.
Ask for an ETA: While they might not give a precise time, asking for an estimated resolution timeframe or an update on the investigation can be helpful.
Check Your Spam/Junk Folder: Sometimes replies from support can end up there.
Provide Any Context (If you can think of any): While you mentioned you were “building with this code” and it “calling my entire thread,” you might consider if anything unusual happened around the time the block occurred. For example:
Did you implement any new, experimental, or particularly resource-intensive features right before this happened?
Did you run any large-scale automated tasks or scripts?
Did you share access with new collaborators or from new locations?
Were there any sudden spikes in API calls or data usage that you didn’t anticipate?
Did you perhaps integrate with any third-party services that might have behaved unexpectedly?
Even if you don’t think it’s directly related, providing any context about recent significant changes or unusual activity in your workspaces around the time the error started could potentially help the support team in their investigation. Do not guess or fabricate, but if anything genuinely stands out, mention it in your follow-up.
Monitor the Google Cloud Status Dashboard: While this specific issue is likely account/workspace-specific, it’s always good practice to check the overall status of Firebase and Google Cloud services to rule out broader outages. (status.cloud.google.com).
We’re working on an issue regarding some users being unable to access their workspaces. If you are impacted, please create a support ticket and we’ll work to resolve your issue quickly. We’re really sorry for any inconvenience this is causing.
