Resolving NetSuite Extension Fetch Error: “File Not Found”

Introduction

While working with SuiteCommerce in NetSuite, you may encounter errors when fetching extensions using Gulp. One common issue is the “File Not Found” error, even though the file is present in the File Cabinet. This article discusses the possible causes and how to resolve them.

Error Details

During the execution of gulp extension:fetch, the following error appeared:

[12:13:20] Error in task gulp extension:fetch
Error Message
  Could not download all the extension files

"File not found:  SuiteScripts/Deploy_Extensions/JobinandJismi/Boulevard_theme_JJ_09_02_2021@4.0.1/Modules/BaseSassStyles@sco-2018.1.0/Sass/Fonts/bossa.scss"

However, upon checking the File Cabinet, the file was present at:

SuiteScripts > Deploy_Extensions > JobinandJismi > Boulevard_theme_JJ_09_02_2021@4.0.1 > Modules > BaseSassStyles@sco-2018.1.0 > Sass > fonts > bossa.scss

Cause of the Issue

The issue was caused by a mismatch in file or folder name capitalization between the manifest file and the actual File Cabinet structure. NetSuite’s file system can be case-sensitive, leading to fetch failures.

In this case, the manifest referenced Sass/Fonts/bossa.scss, while the actual path was Sass/fonts/bossa.scss (lowercase “fonts”).

Resolution

To fix the issue, follow these steps:

1. Modify the Manifest File

Since the file path was incorrect in the manifest.json file, updating it directly resolved the issue.

Open your manifest.json.
Locate the incorrect path.
Update it to match the exact case-sensitive structure in the File Cabinet.
Save and retry fetching the extension.

2. Clear Workspaces and Fetch Again

If the issue persists, try cleaning the workspace and fetching again:

gulp extension:clean
gulp extension:fetch

3. Ensure File Naming Consistency

If modifying the manifest is not an option, rename the file or folder in the File Cabinet to match the expected structure in the manifest.

4. Verify File Permissions

In the File Cabinet, edit the file.
Ensure it is accessible to the required Roles, Users, and SuiteCommerce Extensions.

Conclusion

This error occurs due to mismatches in file paths, often caused by case sensitivity or incorrect references in the manifest file. A quick fix is to update the manifest or rename the files to match. Keeping consistent naming conventions and verifying configurations can prevent similar issues in the future.

By applying these steps, the error was resolved, and the extension fetch worked successfully.