Google AI Studio repeatedly reverts to API key from old project after app rebuild

Hello Google AI Studio Team,

I’m seeking technical assistance with an unresolved API-key configuration problem in Google AI Studio.

In August 2026, I rebuilt an application after its original version became corrupted.

The rebuilt application was configured to use a different API key associated with the intended Google Cloud project. However, Google AI Studio repeatedly reverted to the previous API key associated with the original, broken application.

Despite attempts to correct the selection, the intended API key would not remain selected.

I opened a Google One Support case approximately eight weeks ago. On October 27, 2026, a support representative confirmed that the case remains open and under investigation, but no technical explanation or resolution has been provided.

I have deliberately avoided modifying the rebuilt application since submitting the support ticket to preserve its configuration.

My questions are:

  1. What could cause Google AI Studio to repeatedly restore an API key from an older project?

  2. Is this a known issue involving project selection, saved configuration, or API-key persistence?

  3. How can the correct key and project association be preserved without rebuilding or altering the existing application?

  4. Is there a secure channel through which Google AI Studio engineers can review this issue without publicly exposing proprietary application code or API credentials?

I would appreciate assistance from someone familiar with Google AI Studio’s project and API-key management.

Thank you,

FlyingStarUSA