Im trying to open my project but all i’m getting is a loading circle. I can go into the coding mode and that works fine but the prototyper just loads forever. I don’t get the initial firebase studio loading like setting up workspace etc either. The prototyper was working fine until my most recent rollout. If anyone has ran into a similar error and was able to resolve it let me know. Thanks!
6 Likes
I’m experiencing the same issue. I pushed the code to a GitHub repo and tried reconnecting it to a new Firebase Studio Workspace. However, the Prototyper was not available for the new workspace with the imported code. Does anyone have any other ideas on how to resolve this?
2 Likes
My issue seemed to auto resolve itself this morning. Not sure why.
I have this problem too. please is there any way to fix it?
This issue resolved itself in my case as well. When it loaded the next day, the chat history was gone, but everything worked fine.
1 Like
Same issue here. It happens both on the app and browser.
I gave it a chance and let it load during my dinner break but it did not load for 1.5 hours. No idea about how to solve it, though.
1 Like
What did you do to resume? Mine came back only after I did a hard reboot. But came back and had no history in prototype view. Worse is, it thinks I am working on a new project even though the codebase is there and all is working in code view. The prototyper seems to have been lobotomized and I have not been able to bring it back to the project I am on. It always thinks I am starting something new from scratch - kind of funny since right now any response assumes my prompt was about a new project.
1 Like
I didn’t do anything specific other than wait. I think what happened is the VM got stuck somehow and needed to be reset, which happened automatically after the project is inactive for a period of time. I do see that there is a new ‘Reset’ option in the dropdown next to the workspace in the prototype. I don’t know if it’s new, but I just noticed it. When you select reset it shows the following message:
Resets the workspace by assigning it a new VM while preserving the state of the files on home disk. Use this to recover cases where the VM is unresponsive.
It may be worth trying that.
2 Likes
Would this not erase all context of the prototyper though? Mine’s been stuck on loading for 2 hrs + now. Very frustrating, I’m tempted to try this but worried about loss of context.
Has anyone tried this?
1 Like
I’m experiencing the same issue, I have made a reset to the workspace but still not solved.
1 Like
That happened when mine returned on its own the next day. The prototype context was cleared, but the code base was fine, and I just picked up where I left off. I have not tried the Reset function yet, but I’m assuming that’s what it will do.
1 Like
Well, I went with the reset - and yes, I lost the context - but it really wasn’t a big deal. The new prototyper was able to ‘see’ my app and understand what we were doing, and we picked right up where we left off. I’d recommend resetting in this context, as it appears you’ll lose the original interactions with the AI anyway.
I hope this helps somebody save a few hours of waiting time!
Hi,
I am facing the same issue, but I dont see a reset button in the prototype view. Maybe it hasn’t rolled out yet in Sweden? This problem happens all the time. I would love if someone at Firebase could get this fixed.
It works now, the reset option was there now. I accutally kept the chat history.
What’s worked for me in these circumstances is in code mode, making changes to dev.nix. After making a change, a button appears to rebuild the environment. I have lost my context, but for me, it’s been better than an indeterminate wait.