Latest Contributions by GavinRehkemper

‎02-09-2022

Hi D_P, by default, Experience Builder does not load the ArcGIS API for JavaScript when the app loads. There are two options to use the JS API modules, documented here: https://developers.arcgis.com/experience-builder/guide/extend-base-widget/#modules-in-the-arcgis-api-for-javascript If you do not do either of those, but try to import a JS API module in your custom code, it will not work and you will likely experience errors like you mention above. I do not think that's related to your original issue, because you are getting the error when the jimu-arcgis dependency is properly included in the manifest.json file.

‎02-08-2022

Thank you both for this information. I am able to replicate this issue by following these steps: Download, unzip and install developer edition of Experience Builder v1.7. Add code to client\your-extensions\widgets\simple\manifest.json: "dependency": ["jimu-arcgis"], In the browser, create a new Experience. Add the "Simple" and "Map" widgets Save the experience Open the preview Open the browser developer tools (console) Expected: no errors Actual: Error: Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'popup') at y.updateMapView (:3001/widgets/arcgis/arcgis-map/dist/runtime/widget.js:1:26148) I'll check into this. Is this error blocking any functionality? Or is this just an error that shows up but is not causing any functional issues?

‎12-23-2021

Hi Shaun, thanks for the question. Here is the list that shows which version of the ArcGIS API for JavaScript is used with each version of Experience Builder developer edition: https://developers.arcgis.com/experience-builder/guide/about-versions/ Based on that pattern, I expect the next version of Experience Builder developer edition (version 1.7) to use ArcGIS API for JavaScript 4.22.

‎12-23-2021

We will have this sample widget fixed (so that it works in the Widget controller) for the developer edition of Experience Builder 1.7 release (next release). You can see the changes here: https://github.com/Esri/arcgis-experience-builder-sdk-resources/pull/110 . Thank you!

‎11-24-2021

Ronald, in general yes that should work. Also see some helpful tips in the FAQ (https://developers.arcgis.com/experience-builder/guide/frequently-asked-questions/) under "How should I set up my web-based repo to develop widgets, themes, and apps as a team?",

‎11-22-2021

Hi Laurynas, thanks for the question. Which NPM library are you using? Can you please give a step by step replication case that we can follow so we can see the same error you're getting? Thanks!

‎11-15-2021

Hi Ryan, thanks for the question. The first thing I'm noticing is that in your first CodePen, in the developer tools console it says "Using ArcGIS API for JavaScript 4.20" where in the second one the developer tools console it says "Using ArcGIS API for JavaScript 4.17". Which makes me think there's some issue with the second one where you're setting the API version.

‎11-10-2021

I do not see any geometry information (for example, latitude/longitude) in your screenshot - do you have that info for each asset? If not, that would be the first step. Then you can add them using Leaflet (for example, L.Marker). If you want to transform it into a GeoJSON FeatureCollection, you can use L.geoJSON - that would work too.

‎11-10-2021

A patch that fixes the unit tests issue is here: https://github.com/Esri/arcgis-experience-builder-sdk-resources/tree/master/patches/1.6/patch1/arcgis-experience-builder

‎11-10-2021

A patch that includes fixes to these jimu-icons errors is here: https://github.com/Esri/arcgis-experience-builder-sdk-resources/tree/master/patches/1.6/patch1/arcgis-experience-builder

‎11-10-2021

A patch that should fix the jimu-icons error you are seeing is posted here: https://github.com/Esri/arcgis-experience-builder-sdk-resources/tree/master/patches/1.6/patch1/arcgis-experience-builder

‎11-09-2021

@DaveFullerton thanks for the question. A patch to developer edition version 1.6 that will fix this is in progress here: https://github.com/Esri/arcgis-experience-builder-sdk-resources/pull/106 . We will make posts here in the Esri Community as soon as it is officially released.

‎10-28-2021

As of 3/20/2024, this documentation has been moved to the official Experience Builder Developers documentation: https://developers.arcgis.com/experience-builder/guide/deployment-topics/#automated-deployments Please refer there for the latest updates. This post will not be updated. --- If you’re using Experience Builder in a DevOps workflow, you may need the ability to generate the app ZIP export from a terminal without having the Experience Builder server running. There’s now a way to do this with developer edition of Experience Builder version 1.6 (released last week). In the terminal, browse to the extracted root directory of your Experience Builder developer edition install (the directory that contains the “client” and “server” folders). Then run the following command, replacing the ‘0’ with the ID of the app that you’d like to export, and the ‘app.zip’ with the name of the ZIP file you’d like it to generate. node -e "require('./server/src/middlewares/dev/apps/app-download.js').zipApp('0', 'app.zip');" The ZIP will be generated and placed in the current working directory. An example of using this command in a GitHub Actions dev-ops workflow can be found in this GitHub repository: https://github.com/gavinr/experience-builder-devops-example. Specifically, see the file build-app.yml to see app-download.js being used to generate the ZIP export. This GitHub action builds and deploys the Experience every time a commit is made to the repository – completely automatically! --- Update: In developer edition of Experience Builder v1.7 (released January 2022), you can now include the Client ID that you'd like to be included in the config.json of the output app. For example, node -e "require('./server/src/middlewares/dev/apps/app-download.js').zipApp('0', 'app.zip', 'my_client_id');"

‎10-28-2021

Thank you for your question @erniewise. I am also having that issue with the unit tests in the Simple widget. We're looking into this and will get back soon.

‎10-28-2021

I am seeing this behavior too. We'll check into it. Thank you for the report.

Online Status	Offline
Date Last Visited	‎04-28-2026 10:18 AM

My Ideas

Latest Contributions by GavinRehkemper

Re: [Bug ?] jimu-arcgis dependency => TypeError this.mapView is undefined

Re: [Bug ?] jimu-arcgis dependency => TypeError this.mapView is undefined

Re: Experience Builder Developer - load JS API 4.22

Re: I have an UI bug when i implement the Coordinate Conversion widget from ArcGIS API for JS into experience builder as a custom widget.

Re: Adding Experience Builder apps to source control

Re: Fails to load third party libraries

Re: Custom Layer with React and @esri/react-arcgis

Re: ESRI Leafley creating FeatureLayer with data in an array

Re: Experience Builder 1.6 Unit Tests

Re: Developer Edition 1.6 Errors When Copying Esri Widgets to your-extensions\widgets

Re: Fly controller widget cannot be build in Exb 1.6

Re: Fly controller widget cannot be build in Exb 1.6

Experience Builder DevOps: Generating the App Export ZIP from the Terminal

Re: Experience Builder 1.6 Unit Tests

Re: Developer Edition 1.6 Errors When Copying Esri Widgets to your-extensions\widgets

Re: Map extent tool

Re: Download Experience Builder via CMD

Re: Looking for a developer for project

Re: [Newcomer] Usage with Vite?

Re: Can I query a Scene Layer with Arcgis REST JS?

ArcAPI

Web AppBuilder Custom Widgets