Why isn’t it no longer possible to save backups (copies) of an app that is in development? The history function is highly unreliable. I need to be able to save a copy before testing out something that could potentially screw the whole code up rendering the app unrecoverable. The auto save function was a very bad idea, too.
1 Like
branches could help i guess?
1 Like
Hi @MeatWater
Welcome to the Google AI Forum!!!
Are you seeing any error messages, disabled options, or unexpected behavior when trying to save a copy of the app? If so, please share the exact message or steps you are taking when the issue occurs. This information will help me understand the problem better and assist you more effectively.
Thanks!
Hi
there is no error message, it’s just a function missing. How can I save incremental versions of my code before implementing new functions that might 'cause havoc? The revert method is unreliable.
1 Like
Hello,
Yes, you can save a copy of the entire app from the apps list before asking the model to implement a new feature. You can then continue experimenting in the duplicated app. All saved copies are stored in your Google Drive for easy access, and if anything goes wrong, you can revert to the original working version.
Thanks!
Thank you for getting back Shivam. However, in AI Studio on the “Your Apps” list I can only pin or delete an app. Please instruct me on what steps to take in order to make backup copies of apps.
The history system is atrocious, and removing the option to let the user decide if an app should autosave or not was a bad call imho.
Before, it was as simple as just prompting along, and then save your progress when you knew the code was in a good state. If it ever entered a bad state, you could simply refresh the entire page and get back to a working version.
Now, not only does it save at every single step, you now have to dig through a long list of history to find the last entry where the code worked (which gets even worse if you restored snapshots along the way). If your browser or OS by chance updated while you were sleeping, you now have no way of going back to functioning code, because the last changes were autosaved on top of the existing version, with history being a ‘mystery box’ of ‘Automatic snapshot’ entries.
It was much much easier to control when there was no autosave. You could save when you knew the code was in a good state, and then create a new save that incremented the version, ensuring that you could always go back to the previous one that you knew was good.
Now, if you save a copy, continue prompting, something goes wrong and you revert through history, you revert back to the old version and start overwriting it, if you are not aware and didn’t create yet another copy with a new version number.
I guess my point here really is: bring back the option to toggle autosave - it saves some of us a lot of headache.
Open: Google Disk - Google AI Studio folder
Duplicate or “Fork” feature is so much needed here.
I spent a whole week reworking my app after adding too many features too fast. It’s a must.