topic Re: "The URL does not reference an AppBuilder Extension." when deploying custom web application in Web AppBuilder Custom Widgets Questions

"The URL does not reference an AppBuilder Extension." when deploying custom web application

BrianVan_Nostrand — Tue, 09 Jul 2019 19:29:21 GMT

Hi all (and hopefully Robert),

I'm trying to deploy the Elevation Profile widget to our GIS Portal environment. I've successfully stood an application up on an http-enabled server through IIS, "shared" the app in IIS, and added JSON to the list of MIME Types. I'm pretty sure I've done the initial steps correctly, but my only evidence of that is the fact that I can see the JSON response from the server:

I'm getting the error "The URL does not reference an AppBuilder Extension." when I try to add the hosted widget to Portal though:

Has anyone seen this error or does anyone know of any extra steps that are required that I may have missed?

We're on Portal 10.6.1

Thanks!

Re: "The URL does not reference an AppBuilder Extension." when deploying custom web application

RobertScheitlin__GISP — Tue, 09 Jul 2019 19:48:56 GMT

Brian,

I've successfully stood an application up on an http-enabled server through IIS

Is that url publically available or only internal to your network? If it is not publicly accessible then that is your issue.

Re: "The URL does not reference an AppBuilder Extension." when deploying custom web application

BrianVan_Nostrand — Tue, 09 Jul 2019 19:57:15 GMT

Ah, thanks Robert, that must be the issue. I'll put it on one of our public sites and try again.

Thanks,

Brian

Re: "The URL does not reference an AppBuilder Extension." when deploying custom web application

WilliamSpillane — Thu, 07 Sep 2023 13:40:26 GMT

We had the same issue with an internal installation and were getting the same error. We had the custom widget deployed in a folder below wwwroot/ The solution that we found was to access the widget folder using Windows Explorer, right-click on it and grant permissions to the <servername>\Users group and that also seemed to cure the problem. We're on v11.1