I’m starting to see some of the frustrations now around user feedback i’ve seen on the platform. I am getting constant server errors, not connecting, connecting then dropping, prototyper working then crashing, restarting itself half way through tasks, repeating a task that its just done, half completing tasks then stopping entirely and forgetting where it was up to, then retrying the task again, but a task its already completed… its just extremely unreliable right now. Where as a week ago it was faultless?
I’ve tried a lot to get it running again, nothing works - any suggestions?
If you still have access to the “Code” mode, you can connect your account to Github and use GitHub as your code repository, allowing you to restore the application from any point in time that the code was checked in.
it was conencted to git at one point - but I also just noticed its not even been updating , last update is 3 days ago. And I cant even access it for some reason or the commit ID for it. its like it doesnt exist.
A couple of other suggestions. These are just some things to try.
Can you try discontinuing the GitHub repo and connecting it to a new repo?
In the code view, you can ask gemini what the error is and it should be able to fix the problem. From the screenshot you shared, it looks like the typescript file is incomplete.
mock
is on a line by itself but it looks like something else is intended to complete the syntax.
Often if you fix the issue in the code, the server startup issue should resolve itself.
Another option you can try is to restart the VM. If you are the owner of the Firebase Studio project, you can click three dots on the home screen next to the project name and select “restart” from the selections in the menu.
ok so i tried GIT, wouldn’t even commit or allow changes. removed it an put back accessing our other git account. now running fine.
Also: the AI “fixing” seemed to make it worse, as it had the server running/listening on different ports, it was asking it to do 2, not one. all that changed. its running ok now… for now!
It also had no gitignore file, so worked out it was actually trying to track 100s of thousands of files bogging it down.
It turns out I was able to fix the prototyper silently not loading issue I was having.
I believe my context was so large (over 2M) by accidentally including a new build log file that it wasn’t even able to load. By reducing my context back down to a reasonable limit, it was able to load again.
