Status Update
Comments
ch...@appspot.gserviceaccount.com <ch...@appspot.gserviceaccount.com> #3
Hello there,
When following the steps you mentioned, the URL returned in my test environment is the /dev one and not the one you mention. Hence, I am not able to reproduce this behavior.
Would you mind providing more information regarding this and eventually a list of steps in order to investigate this further?
Moreover, did you notice this particular behavior only with this script or it has happened with others as well?
ch...@appspot.gserviceaccount.com <ch...@appspot.gserviceaccount.com> #4
When executing ScriptApp.getService().getUrl()
as a function directly it indeed works as you explained. We also receive the /dev url.
The way we deploy and test our add-on is on Google Calendar. We want to expose the Script URL through createSettingsUrlFunction
for the calendar addon.
Attaching the manifest file and the function we use for the createSettingsUrlFunction
function.
Attaching also a screenshot showing the mismatch between the Deployment ID and the URL generated in Google Calendar.
Attaching a screenshot taken from the script editor - showing the deployed version id.
Bottom line: I would expect the Google Calendar settings link to return the version deployed and not anything else.
Expected URL returned by ScriptApp.getService().getUrl()
:
Actual URL returned by ScriptApp.getService().getUrl()
:
ch...@appspot.gserviceaccount.com <ch...@appspot.gserviceaccount.com> #5
To answer your last question - this happens consistently. I am able to reproduce this on a new project.
ch...@appspot.gserviceaccount.com <ch...@appspot.gserviceaccount.com> #6
Thank you for all the details provided. However, I am still not able to reproduce the behavior you are mentioning as the URLs are returned correctly and match even after multiple changes and deployments.
Do you have any other information that might be of help?
Description
Internal (Googlers-only) Reports:
- Chromium:
(Legacy) Chromeperf Report:
Top 1 regressions (out of 1, with 0 improvements) in this group:
- ChromiumPerf/android-pixel-fold-perf/v8.browsing_mobile/total:500ms_window:renderer_eqt:v8_max/browse_media/browse_media_flickr_infinite_scroll_2019
28.52%: 23.4765 -> 30.172 ms
Top 1 affected measurements in android-pixel-fold-perf:
- v8.browsing_mobile/total:500ms_window:renderer_eqt:v8_max/browse_media/browse_media_flickr_infinite_scroll_2019
28.52%: 23.4765 -> 30.172 ms
Regressions grouped by v8.browsing_mobile includes data from the following benchmarks with listed owners:
v8.browsing_mobile: cbruni@chromium.org, leszeks@chromium.org
Commits in this range:
Chromium Git Hash:
Chromium Commit Position:
V8 Commit Position:
WebRTC Git Hash: