Production URL_ Repulishing error

Dear Google AI Studio Support Team,

I need your assistance with republishing an existing Google AI Studio application.

I have an existing application called:

Remix_V_Roots_Supabase_Test

The application is already published and currently has the following working production URL:

remix-v-roots-supabase-test-49816121579.us-west1.run.app

The existing production URL is still working correctly and opens the V_Roots application. However, I have made several updates to the application in Google AI Studio, and I need to publish those latest changes to the existing published application.

When I select Republish, AI Studio takes me to:

Publish your app → Step 2: Final touches

It shows the existing application and its current run.app URL, but it also requires an .ai.studio App URL.

AI Studio automatically suggests:

remix-v-roots-supabase-test-2180.ai.studio

However, it displays:

“This URL is not available.”

I have also tried the republishing process previously, and the same issue occurs with the generated .ai.studio URL.

What I need

Could you please confirm:

  1. Why AI Studio is requiring a new .ai.studio URL when this application is already published with an existing Cloud Run URL?
  2. Is there a way to republish the latest changes to the existing published application while preserving the current production URL:
    remix-v-roots-supabase-test-49816121599.us-west1.run.app
  3. Is the .ai.studio URL requirement a known issue with existing/legacy AI Studio publications?
  4. If there is a recommended migration or republishing procedure, please provide the exact steps.
  5. Most importantly, I want to ensure that the existing Supabase database, authentication, family-member data, photos, and existing production deployment are not affected or replaced.

The application is currently working, but it is serving the previously published version. The latest changes are visible in the AI Studio development environment but are not appearing on the production URL.

I would appreciate your guidance on the safest way to deploy the latest changes to the existing application without creating a duplicate application or changing the existing production URL.

Thank you for your assistance.

Kind regards,
Anoop Thampi