New IDE changing the urls of web apps???

[Marko Kolombo]

Hey all,

I was finally able to work with the new IDE, and I was pushing a new deployment of my web app when I realized... the new deployment has a different url?!?

And reverting to legacy editor won't help...anyone else affected by what it seems like a huge bug?

[Romain Vialard]

Are you sure?
Creating a new deployment in the new IDE should be exactly like creating a version in the old IDE and should not affect the URL of your web app.

[Marko Kolombo]

Here a screenshot...instead of "overwriting" the existing deployment as it used to do in the legacy editor, it creates a new deployment with a different url. And they are both active and working. 

I checked, reverting to legacy editor fixes the issue

[Romain Vialard]

Sorry, you are right.

If you deploy first from the new IDE, no problem.

But if you first deploy as a web app with the old IDE, then deploy from the new IDE, it will indeed create an entirely new deployment, with a different URL.

As you've seen, you now have 2 different "active" deployments. 

If you go to the old editor and click on "Publish" > "Deploy from manifest", you should see 2 deployments in addition to the "Latest Version (Head)" one.

• A deployment named "web app meta-version" => that's the one created from the old IDE
• another one named "default meta-version" => created via the new IDE

Currently, the "New deployment" menu in the new IDE lets you update the version linked to the "default meta-version", not the "web app meta-version".

I tried to rename the deployment "web app meta-version" to "default meta-version" but it doesn't help.

For now it seems you'll have to wait for an update in the new IDE before you can update your web app while keeping the same URL.

[Marko Kolombo]

Thanks for going in such detail!

What I don't understand is:

- is it a bug? then I should open an issue 

- is it an intended behavior? then it should be documented (so I should open an issue? :D )

What do you suggest?

Marko Kolombo

--
You received this message because you are subscribed to a topic in the Google Groups "Google Apps Script Community" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-apps-script-community/qhiqjGabQpI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-apps-script-c...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-apps-script-community/686c6419-dec5-4c58-a5e7-27faab68a0cdn%40googlegroups.com.

[Romain Vialard]

I think it's a bug. 

If only 1 deployment is available (eg: deployed as a web app), the new IDE should use it, not create a new one.

I'm not sure if Google is seeing that way though.

I wrote an article on Deployments in the new IDE and added a warning with a link to this thread.

https://romain-vialard.medium.com/deploy-easily-with-the-new-google-apps-script-ide-69343c71a889

[Marko Kolombo]

Good, thanks!

I'll open an issue later then

Marko Kolombo

You received this message because you are subscribed to the Google Groups "Google Apps Script Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-apps-script-c...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-apps-script-community/8b52f908-2353-4b10-ac1f-fdf86c64ac50n%40googlegroups.com.

[Instituto San Pedro]

Hi Friends

Is it possible this issue has no workaround yet?

We have multiple webapp created on legacy editor published in sites, social media, and email templates, we are editing them weekly. is the only possible solution to this changing all the published urls so we can keep editing if we want to use the new editor permanently from now on?

for each change we made we have to switch back to the legacy editor to keep the same published urls.

Thanks in Advance

Claudio Altamirano

I.San Pedro

[Adam Morris]

Unless there’s further comms from google that’s what you’ll have to keep doing. 

I have also been inconvenienced by this. 

I suggest filling out the dialog box each and every time so they have a record of how much the feature is needed. 

Adam

INSTITUTO SAN PEDRO
www.escuelasanpedro.com

--
You received this message because you are subscribed to the Google Groups "Google Apps Script Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-apps-script-c...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-apps-script-community/390406d7-32cc-4d63-82e5-77b196cd3e31n%40googlegroups.com.

--

http://classroomtechtools.com

[Instituto San Pedro]

Should I open an issue in issue tracker?

I filled in their form each time I had to opt out new editor due to this.

There are good new features in the new IDE so I will write my code there and opt out to the legacy each time I need to publish a new version which needs same url.

Thanks

Claudio

To view this discussion on the web visit https://groups.google.com/d/msgid/google-apps-script-community/CAHQVb%2BTCmHCAvcVUfk%2BCAs1Dc_vVbHXk%2BM%3DM%2BY3tViURKi31Ww%40mail.gmail.com.

INSTITUTO SAN PEDRO
www.escuelasanpedro.com

[derrick...@gmail.com]

Hi all,

I am also facing the same issue (script(s) created originally in old IDE, then updated in new, now with different URL). is there an Issue Tracker open for this?

For one of my scripts which now has multiple Active deployments, I am actually still able to use an older deployment link which appears to have become HEAD. That is, if I make any changes to the script (without creating a new version), the change gets reflected in the live app. 

[derrick...@gmail.com]

I created an issue here: https://issuetracker.google.com/issues/176920091

[Instituto San Pedro]

Great Derrick

Thanks

Claudio

To view this discussion on the web visit https://groups.google.com/d/msgid/google-apps-script-community/887b9409-4d93-4e19-b382-8cc8705afdedn%40googlegroups.com.

INSTITUTO SAN PEDRO
www.escuelasanpedro.com