Rolling back to working version question

I have created an app for work and everything was working fine, I deployed and testing live was all good. Found a few things that needed an adjustment so made the amendments and re pubilshed, some errors started to appear mainly arround permissions, anyway, on the advice of the chat I followed all the things to check and chage and we went back and forth for hours just getting nowhere. We are now at the stage where I will implode if AI says this will definatley fix the issue.

My question is, if I roll back to the working version befor the minor adjustments, asuming that works as I hope it will, can I then get that deployed version back onto my development project so I can work on it if needed?

Thanks
Josh

2 Likes

App has completly died now, never mind. Shame as it was working great. Put a support ticket in and hope for the best.

1 Like

It also occured to me. The prototyper deviated from published version and introduced various kinds of bugs. I have not found a way to bring back to the previous published version as well. But, if you did clear the chat by /clear and can’t restore the previous versions, I advice you to go to code editor and see the timeline/history on the left bottom. If you click on any file you want to revert back to, you can just click on it and copy paste that code.

1 Like

mine has done the same - built a substantial app and was working perfectly. now it FILLED with errors and im also having server connection problems, also unable to rebuild due to the errors.

1 Like

Screenshot 2025-06-22 182729

Im using github (source control) and this button..

Might look into that,

its a real shame as it was shaping up to be a game changer, 30 plus hours spent on it and now unuseable. Fingers crossed I get help from the support deask

im not getting the prototyper or chat or anything unfortuntly.

the app was back up today but buggy as hell, I will wait it out with the help desk and keep my fingers crossed

Im now just getting constant server error bugs - Ive looked back and its automatically deleted so much stuff - Incidentally, its all happened around the time I linked it to the project to go publish the app. Im now not even able to access prototyper or code area without it crashing - just getting “internal server error”

Im trying to roll it back via git to the point before It setup for publish but now its not even pulling in any git info to do that with.

im almost at the give up stage, this was an awesome tool but now its almost not worth the time sadly. No help from support so far.

Are you building a web app? Please give me some information about your project.

I am building a web app for my work, its a admin / HR tool. The app was working perfectly and was published and I needed to adjust a couple of functions and then it just stopped working with all sorts of errors. The issues i am looking to fix at the moment stem from cors issues it seems, i had a pdf upload function, thats not woking, the system no longer can look up and show storef files and the invite member function is not working. All was fine before. Happy to provide more info if you need it.

I’m also working on a web app and encountered a lot of errors the first time around. On the second attempt, I knew exactly what I wanted to build and told the AI ​​to make certain features like the upload function, notifications, authentication, etc. modular. Since then, I’ve been able to add new features without breaking everything. ^^ Modularity was the solution for me. Don’t despair; as is often the case with AI, the key is a well-worded prompt. Good luck!

1 Like

Thats an interesting concept, are you able to expand on how you did that within firebase studio

I believe that building a solid foundation is crucial when developing a web app.

On my platform, users can upload images, and others can rate, comment, and like them. I also wanted a functional admin panel to handle moderation and general management. That includes giving admins the ability to edit or delete comments and user uploads.

Looking back, the biggest mistake I made during my first attempt was blindly prompting the AI. The result? Spaghetti code. I kept piling on features without a proper structure: build this, add that… and suddenly, things started breaking. Especially when trying to update or change something, other parts would mysteriously stop working.

On my second try, I approached it differently: I started by clearly defining the layout. I knew exactly how the app should look and feel. Then I tackled authentication first and this time, I explicitly told the AI to create a “modular” authentication system. That was key.

Next, I laid the groundwork for the admin panel, setting up role-based access control for admins, moderators, and regular users. From there, everything else was built step by step. And yes, I kept reminding the AI: “Make it modular!”

Lesson learned: Structure first, features second.

Meanwhile, my project has grown significantly—it’s become quite extensive. And the best part? Everything works. Clean, stable, and maintainable.

1 Like

That looks nice and tidy, the kind of structure I would adopt. Can I ask, if you dont mind, how would you craft a prompt to acieve this? I am much better now than when I started using AI but this looks an intresting approach.

So I finally got this app back up and working. I am taking a break from it as it has caused me to have a breakdown :wink: I continued with my second project and started to get error-boundary-callbacks.js:83 Uncaught Error: React.Children.only expected to receive a single React element child., Guess what, that is now broken. I give up lol. I have deleted it and will give this one more chance.

A major BKM is to use a code repository.

Connect to GitHub if you can. I believe code repository connections (like to GitLab) are in the works.