Error in add-on with an http:// URL suggests modifying a non-existent manifest field (enableHttpEndpoints) [214015254]

Assigned

Bug

Status Update

No update yet.

Description

co...@google.com

created issue #1

Jan 11, 2022 12:37PM

Issue summary: When creating an add-on, the documentation states that the allowlist URLs cannot use a http:// prefix, only https:// prefixes are accepted (

https://developers.google.com/apps-script/add-ons/concepts/workspace-manifests#allowlist_urls).

However, if an add-on with an http:// header is attempted, the given error (Executions on HTTP endpoints are disabled. Set enableHttpEndpoints to true in manifest file) indicates that a field of the json manifest object should be changed to allow for http URLs. That field does not exist nor is it mentioned in the documentation (

https://developers.google.com/apps-script/manifest/addons).

Reproduction Steps: 1. Create an add-on following the quickstart:

https://developers.google.com/workspace/add-ons/alternate-runtimes-quickstart 2. Modify the "runFunction" inside "homepageTrigger" to a valid URL with an https:// prefix 3. Observe the error given: Executions on HTTP endpoints are disabled. Set enableHttpEndpoints to true in the manifest file.

Expected Behavior: An error stating that http:// prefixes are not supported.

Actual Behavior: The error: Executions on HTTP endpoints are disabled. Set enableHttpEndpoints to true in manifest file

Comments

co...@google.com <co...@google.com> #2Jan 11, 2022 12:38PM

This bug has been submitted internally.

sg...@gmail.com <sg...@gmail.com> #3Feb 18, 2022 10:16AM

Hello, can we expect a fix soon? thx

ak...@gmail.com <ak...@gmail.com> #4Jun 8, 2022 12:56PM

Comment has been deleted.

Message last modified on Jun 8, 2022 12:57PM

ti...@timmolendijk.nl <ti...@timmolendijk.nl> #5Oct 11, 2022 01:20PM

I am facing the same issue: set homepageTrigger.runFunction to a valid HTTPS URL, which fails with "Executions on HTTP endpoints are disabled. Set enableHttpEndpoints to true in manifest file".

I am equally confused by OP’s expected behavior: ”An error stating that http:// prefixes are not supported” — this is not the behavior that I would expect after specifying a valid HTTPS URL.

(By the way: I am horribly stuck. It’s insane how convoluted this whole Add-on development process is. Documentation looks amazing on the surface but ends up surprisingly unhelpful, as stuff just doesn’t seem to behave as advertised. For instance, this entire section is irreproducible for me. 🤷‍♂️)

jp...@google.com <jp...@google.com> Jul 13, 2023 02:32AM

Assigned to wo...@google.com.

Issue 214015254