Is it the bug? "Manage Deployments" -> "New Version" erroneously archives active deployment and creates a new "Untitled" instance

2 days ago 8
ARTICLE AD BOX

Component: Apps Script > Deployment / Web App

Description: I am experiencing a critical issue with the "Manage deployments" feature in the new Apps Script editor. When attempting to update an existing Web App deployment to a new version (to preserve the existing URL), the system incorrectly archives the active deployment and creates a completely new one with a different URL.

Steps to Reproduce:

Open an existing Apps Script project with an active Web App deployment.

Click the "Deploy" button (top right) -> Select "Manage deployments".

In the left sidebar, ensure the Active deployment is selected (highlighted).

Click the "Edit" (pencil icon) on the top right of the configuration panel.

In the "Version" dropdown, select "New version".

Click the "Deploy" button.

Expected Behavior: The existing deployment (Same Deployment ID) should be updated to the new version code. The Web App URL should remain unchanged, and the deployment should remain under the "Active" tab with its original description.

Actual Behavior:

The original active deployment is immediately moved to the "Archived" section.

A new deployment named "Untitled" appears in the "Active" section.

This new deployment has a new Deployment ID and a new Web App URL, breaking all existing links and QR codes distributed to users.

Impact: This effectively forces a URL change for every code update, which defeats the purpose of "Versioning". It makes it impossible to maintain a production application where the URL must stay static (e.g., printed on QR codes).

Additional Information:

Browser: Edge

Account Type: Personal Gmail

Read Entire Article