Starting today, we are encountering a deployment error when deploying a custom 2020.1 theme based on the 2020.1 base theme. The error message is “[105133] TypeError: Cannot read property ‘files’ of undefined”, and it occurs after uploading the 12/12 chunk in the deployment. Has anyone else encountered this error? Here is snapshot of the deployment, error message and partial stack trace:

…
Uploading Chunk 10/12 [==================================================] 100%
Uploading Chunk 11/12 [==================================================] 100%
Uploading Chunk 12/12 [==================================================] 100%
[10:51:33] 'startDeploy' errored after 4.48 min
[10:51:33] TypeError: Cannot read property 'files' of undefined
  at /Users/kdf/Projects/SCA_2020.1/ThemeDevelopmentTools/gulp/extension-mechanism/deploy/deploy.js:153:58
  at Array.forEach (<anonymous>)
  at /Users/kdf/Projects/SCA_2020.1/ThemeDevelopmentTools/gulp/extension-mechanism/deploy/deploy.js:152:15
  at /Users/kdf/Projects/SCA_2020.1/ThemeDevelopmentTools/node_modules/async/dist/async.js:2939:19
…

We successfully deployed yesterday. It started happening today and it’s happening for two developers, and one of the developers is deploying a version of the theme that successfully deployed in the past. If you have ideas on the cause, please help. Thanks

Ugh this has happened to me in the past when playing around with 20.1 too. I'm also curious about it.

I’m digging into the node/gulp javascript now in hopes of finding the cause.

i tried adding an if somewhere to avoid nulls and made it worse, and rage-quitted 😅

I just fixed this problem on my theme deployment. If you are using a custom role to deploy, make sure your role has permissions in the RESTlet script deployments that were installed by the Tools bundle.

@wes_w, I think you nailed it. I haven’t confirmed it yet, but I discovered that NetSuite updated the Extension Management bundle to 2020.1.1 yesterday afternoon after we did the last successful deploy. Damn. Cross your fingers that this is it. Thanks.

@Keith Fetterman Sorry if that was not clear. Deployment means two different things in this situation

Thanks.

Now I'm having an issue where I can finally gulp theme:deploy, but the new version does not show up in the Extension Manager

The problem is solved. It was not the role / scripts deployments. I checked them all and they had the SCDeployer role that was from the Extension Management bundle. The problem was due to the local dev. environment was using the previous version of the ThemeDevelopmentTools-20.1.0.zip file. I wasn’t aware that NetSuite updated the extension management bundle yesterday. My zip file was from the 2020.1.a version, and now we have the 2020.1.1 version of the bundle installed. The version number on the zip file is still 20.1.0 in the 2020.1.1 bundle. When I downloaded and built the latest ThemeDevelopmentTools-20.1.0.zip file, the deployment now works.

I'm still using the 2020.1.0.a tools. What made you update?

We discovered the font files were being corrupted when the theme was deployed when the extension management bundle was 2020.1.0.a. Our developer tools zip file was from that version. We requested that NetSuite Support update the ext. mgmt. bundle to the latest 2020.1.1 to fix the font files. I am testing now to see if the deployment is still corrupting the font files.

Ah, I see. I have yet to actually get deployment to work all the way to even test anything. I finally got gulp to execute without erroring today (due to the permission issue).

Updating the developer tools zip file to the latest version fixed the problem, and the 2020.1.1 extension management bundle fixes the corrupted font file problem

@Keith Fetterman I'm wondering if I have the same font file problem as you were experiencing... I'm using a customized version of the Threads Theme and I am missing the characters for the search icon and the cart icon. Is that what you had?

Yes. When I deployed the theme, all of the icons were missing. I discovered the fontawesome font files were corrupted. Upgrading the Extension Manager to 2020.1.1 and replacing the theme developer tools with the latest zip file from the updated extension management bundle fixed the issue.

Thanks! I'm still getting that error that I thought was fixed with the permissions...