Prototyper history gone, now what?

I tried it, but it still failed. What should I do next?

I think they’re facing server overload

Okay, because it was still generating when I got back to the prototyper but it just didn’t write anything. I hope it will be resolved soon.

Do you think I can create a new app with the prototyper and then somehow import all the stuff from my github project there?

yes, the same process I outlined here with some minor changes, it’s actually simpler since you won’t necessarily need to worry with back up and reverting the initial commit (although this is a good idea)

1 Like

Thank you soooo much! You are such a hero for the firebase community! It worked really well. Thank you sooo much!

2 Likes

Thank you so much! I passed the details on to my bro and he’s helped me get the project back online following these steps! Really appreciate the help from you and the contribution to the community!

1 Like

BTW. I think the prototyper works muuuuch better since I created a new project.

yepz! it does works better because the context is clean, it’ll read the codebase and work with great precision… as context gets overloaded it becomes increasingly difficult to keep context precision. Although Gemini 2.5 is pretty awesome with context, still, in a large codebase precision is key. (it’s not like we are coding 1 shot tetris games).

Thanks @DaC ! This worked. This was the first thing I wanted to do but I didn’t know what folders to clear out first and frankly I wasn’t sure if it would make things worse. Thanks! I owe you a pint of any beverage!

1 Like

Glad I could help! Just let me know where I should redeem the coupon :slight_smile:

1 Like

If you’re ever in DC, give me a holler.
Now if only I could get firebase to deploy functions even once… studio just can’t handle eslint issues.