I have an existing Google AI Studio app called Stamp Set Finder.
The app was previously published successfully and the current production URL is:
stamp-set-finder.ai.studio
The current published app is still working normally.
I have made additional changes in AI Studio Build/Preview, including an updated storage-location system. The latest changes work correctly in Preview.
However, when I try to publish/republish, AI Studio stays in the publishing workflow cycling through:
- Gathering app details
- Preparing Google Cloud Project
- Running launch checks
- Optimizing for speed and performance
- Deploying to the cloud
It never completes.
I checked the Google Cloud project and Cloud Run directly.
Google Cloud Project: Article to Image
Project ID: gen-lang-client-05247869..
Cloud Run service: stamp-set-finder
Region: us-west1
Cloud Run is healthy.
The latest successful revision is:
stamp-set-finder-00002-58x
It currently receives 100% of traffic.
Repeated publish attempts from AI Studio do not create a new Cloud Run revision.
So the current production app continues to serve the older version, while the newer code remains visible only in AI Studio Preview.
Firebase Firestore and Firebase Authentication are enabled in the same Google Cloud project.
I want to keep the existing app, Firebase data, user authentication, and existing URL:
stamp-set-finder.ai.studio
I do not want to create a new app or lose the existing Firestore data.
Could you please check whether this AI Studio project has lost its publishing/deployment association or whether the republish pipeline is failing before a new Cloud Run revision is created?
I can provide screenshots and the AI Studio App ID if needed.
AI Studio now shows “Stamp Set Finder is published!” with Status: Ready and the existing URL stamp-set-finder.ai.studio. However, visiting that URL still serves the older version of the app. The live app still displays the old Cabinet / Shelf / Box storage system, while the current AI Studio Preview contains the new Location A–Z + Number system. So the Publish UI reports success, but the latest Build version is not actually reaching production.
