Urgent Bug Report: Critical Issue with Checkpoint Restore in Google AI Studio Console

Google AI Studio
, ,
1

Urgent Bug Report: Critical Failure of ALL Restore Options in Google AI Studio

Hello team,

I am experiencing a critical bug with the restore functionality in Google AI Studio, and I need your help.

I’ve been building an application for several weeks. The app was working perfectly until today, when a small change made by the AI model broke the entire application.

The core issue is that I cannot restore my application from any previous, working state. This problem affects both:

  1. Checkpoints within the conversation: The Restore Checkpoint option fails.
  2. Copied app versions in my account: Restoring from a previously saved application copy also fails.

Both attempts result in the same fatal error: Uncaught TypeError: firebaseApp.auth is not a function.

This is extremely confusing, as all these saved versions were created when the application was fully functional.

Here is a summary of the problem:

  • Application was working: The app was stable until the AI model made a small, recent change.
  • Code was broken by the model: The change caused a critical bug, rendering the app unusable.
  • All restore options fail: Both the in-chat Restore Checkpoint and restoring from a separate application copy in my account result in the same error.
  • Auto-Fix also fails: The “Auto-Fix” option repeatedly fails to resolve the issue.

This bug is a significant problem. It suggests that saved, working versions of an application can become corrupted or incompatible with the console’s environment. The fact that this occurs across both types of restore options points to a fundamental issue with how the platform handles state and code versions. I kindly request that the Google AI Studio team investigate this issue as it completely undermines the ability to reliably build and manage applications using the platform.

Thank you.

image
image1920×1080 197 KB

3 Likes
3

Hello… are you me? Identical issue here. I have the working code I can re-upload, but with the file management / explorer being so bad at file management, it’s a huge pain. Restoring (back to an error free version) somehow either does not restore to that version, or maintains the new error introduced an hour ago. App no longer functional. However since you also mention FireBase, I am now curious if that might be the issue (thanks for the clue). I have the same error. Perhaps I’ll dig down into it from that end. Maybe my new bug is FB related and not code related at all. It might explain why all older versions now give the same error when they did not 13 hours ago.

1 Like