@jamesor We’re going on two weeks for a critical blocker of a core feature of Firebase Studio. Can you provide an update? What’s the team’s internal SLA for issues like this?
This makes Firebase Studio unusable for me. 2.5 Pro, with great confidence, claims that changes were implemented while they were not. When asked to verify and correct, I am getting a litany of apologies, then another attempt when it is more of a coin toss when it comes to the outcome. Sometimes it manages to write the file, sometimes it doesn’t.
I’m starting to think there is no real owner here.
1 Like
@moderators Are you aware of this bug and the suspicious activity outage affecting hundreds of users right now?
If you’re still experiencing this issue please submit a ticket at Get help with Firebase Studio and include both the workspace ID and the debug info to better help the support team triage your personal issue.
1 Like
@jamesor , rather than responding with what seems to be an automated message, could you provide a clear explanation as to why all users have been banned? Every one of my classmates has been affected by this situation.
1 Like
We personally discussed my inability to submit tickets in the past and that issue is also unresolved.
I agree with @yy_nal and don’t think it’s appropriate to instruct users to submit a ticket for a system wide outage affecting hundreds of users.
Basic functionality is broken. It should be detected and responded to autonomously like other Google products.
2 Likes
