topic Re: Error when migrating to version1.3: Cannot read property 'widgetType' of undefined in ArcGIS Experience Builder Questions

Renaming Widget Error: Cannot read property 'widgetType' of undefined

DaveFullerton — Fri, 09 Apr 2021 22:46:09 GMT

Update: If you read through you will find that renaming widgets was the issue.

Up to now I have been working with Dev Edition v1.1 and wanted to try migrating to v1.3. When I ran into trouble, I tried migrating to v1.2 where I did not encounter this error:

My project has 2 custom widgets that I developed, but only one of them fails. A third widget that also fails is simply a copy of the argis-map widget that I renamed and made a few changes in mapbase.tsx to disable all navigation (replacing/enhancing the functionality of the disable zoom scrolling option). All 3 custom widgets worked correctly in v1.3 when I tested them in a new ExB project. Again, I have no problems migrating to v1.2.

I also see errors in the server command window:

Any thoughts regarding this would be appreciated.

Re: Error when migrating to version1.3: Cannot read property 'widgetType' of undefined

AlexisCuicui — Tue, 16 Feb 2021 16:28:41 GMT

Good afternoon,

Look in your browser console if the loading of the API isn't blocked du to CORS request.

https://HOSTNAME/arcgis_api_js/library/4.18/dojo/dojo.js

I had the same issue, until i enabled CORS requests on my server.

Re: Error when migrating to version1.3: Cannot read property 'widgetType' of undefined

DaveFullerton — Tue, 16 Feb 2021 16:51:10 GMT

I am running the developer edition on a pc (IIS turned on, of course). Here are the errors from the console:

What made you think that enabling CORS was the answer?

Re: Error when migrating to version1.3: Cannot read property 'widgetType' of undefined

DaveFullerton — Thu, 18 Feb 2021 05:02:18 GMT

This showed up now too:

Re: Error when migrating to version1.3: Cannot read property 'widgetType' of undefined

AlexisCuicui — Thu, 18 Feb 2021 09:31:30 GMT

I had a similar issue with the same prompt error message. But it seems to be different in your case.

I may ask a basic question but, are the file from the 404 error accessible from file explorer in client/dist/widgets ?

Re: Error when migrating to version1.3: Cannot read property 'widgetType' of undefined

DaveFullerton — Thu, 18 Feb 2021 16:30:21 GMT

This is not a basic question for me, Alexis. I don't see anything there or within the widget directory:

Re: Error when migrating to version1.3: Cannot read property 'widgetType' of undefined

AlexisCuicui — Fri, 19 Feb 2021 15:26:40 GMT

The only way , I could reproduce your error was to delete/empty the manifest file into the Widget.

Are you Widget in the client/your-extensions/widget repository ?

Is your client side started on NPM ?

Re: Error when migrating to version1.3: Cannot read property 'widgetType' of undefined

DaveFullerton — Fri, 19 Feb 2021 18:57:21 GMT

Thanks for trying that Alexis. The answer is a definitive yes to both questions. I have not tried enabling CORS yet. Developer Edition has been installed on a PC. We have a new IT director and he has recently taken away our administrator access to PCs. I cannot run IIS Manager anymore and am waiting to hear back from a system administrator (who is now overloaded due stricter policies).

Re: Error when migrating to version1.3: Cannot read property 'widgetType' of undefined

Junshan_Liu — Sat, 20 Feb 2021 00:11:22 GMT

@DaveFullerton I think you may not run "npm start" in the client folder. The custom widgets need to be compiled when they are upgraded to the new version.

Re: Error when migrating to version1.3: Cannot read property 'widgetType' of undefined

DaveFullerton — Mon, 22 Feb 2021 04:41:52 GMT

As I told Alexis above, web pack was running. I tried it many things and restarted web pack repeatedly to try those different things. Also, as stated in the original post, one of my custom widgets did work correctly. Custom widgets for a different application worked correctly too.

Re: Error when migrating to version1.3: Cannot read property 'widgetType' of undefined

Junshan_Liu — Mon, 22 Feb 2021 05:56:38 GMT

This looks strange if the widget is in the dist folder. Can you launch the URL in a new tab that shown as 404 in the console?

Re: Error when migrating to version1.3: Cannot read property 'widgetType' of undefined

AlexisCuicui — Mon, 22 Feb 2021 09:34:06 GMT

Could you try to create a new experience from scratch and try to add your own widget inside ?

It may give some leads on what is failing ?

Re: Error when migrating to version1.3: Cannot read property 'widgetType' of undefined

DaveFullerton — Mon, 22 Feb 2021 15:48:11 GMT

Thanks, Alexis, as stated in the original post I have tried that:

All 3 custom widgets worked correctly in v1.3 when I tested them in a new ExB project.

Re: Error when migrating to version1.3: Cannot read property 'widgetType' of undefined

DaveFullerton — Mon, 22 Feb 2021 15:59:02 GMT

Yes, the widgets are in the dist folder. This is what it looks like if I copy and paste the URL in a new tab:

This is what it looks like when I Preview the app:

Re: Error when migrating to version1.3: Cannot read property 'widgetType' of undefined

DaveFullerton — Mon, 22 Feb 2021 16:03:01 GMT

The NODE_TLS_UNAUTHRIZED error may be a hint that CORS needs to be enable. Hopefully I will hear back from IT about getting privileges set back to where there were so I can do that. A new error has cropped up:

Re: Error when migrating to version1.3: Cannot read property 'widgetType' of undefined

Junshan_Liu — Tue, 02 Mar 2021 01:59:36 GMT

The widget name is changed. Take op-whmn-search as a sample, it's called op-search in the config.json, but the widget name is changed to op-whmn-search, that's the reason why the widget can't be found.

Re: Error when migrating to version1.3: Cannot read property 'widgetType' of undefined

DaveFullerton — Tue, 02 Mar 2021 18:49:17 GMT

Thank you, Junshan. To differentiate the names between the widgets for this Experience from the ones for an Experience that followed, I renamed the widgets. This was a long while back. When I tested the projects in v1.1, everything worked fine. I made changes and redeployed the Experience multiple times - but made no changes to the custom widgets. It seems to me that the reason the widgets continued to work is that after I renamed the widgets there were functioning orphans in the client\dist\widgets directory.

So I guess the question now becomes: "Is there a way to rename widgets and fix Experiences that reference them?"

As you say, the config.json file in server\src\public\apps\5 did not have the correct widget names. I updated them, but it still didn't work. I then found the config.json file in server\src\public\apps\5\resources\config and updated it. This did the trick.

So from what I have seen so far, it seems that after renaming a widget, you should:

1. Delete the orphan in client\dist\widgets.

2. Change all references to the name of the widget in server\src\public\apps\[#]\config.json and server\src\public\apps\[#]\config.json.

Re: Error when migrating to version1.3: Cannot read property 'widgetType' of undefined

Junshan_Liu — Wed, 03 Mar 2021 05:28:19 GMT

To change a widget name, you need to:

1. Stop webpack in client

2. Change the folder name

3. Change the name in manifest.json

4. Change the reference in apps/#/config.json and apps/#/resource/config.json (one config is for published version, one config is for draft version)

5. Start webpack