ENOENT: no such file or directory, open '/opt/build/repo/assets/favicon.png'

[luke]

Hi, @Louis_Syfer. You keep making incorrect statements. I realize you are not aware the statements are incorrect. However, you do have some facts completely wrong.

Please take a moment and consider what follows with an open mind. We really are telling you the reason for the error and the correct solution for it.

I tested your command and… it doesn’t work.

It did work. The entire purpose of the modified command was to dump the contents of the directory assets to the build log if the build failed. I explained that in detail when I suggested the change:

@luke

npx expo export:web || { tree /opt/build/repo/assets/ ; false ; }

This will log the contents of that directory to the build log so you can see if the file exists or not.

The logic above says this:

• run npx expo export:web
• only if the command above exits with an error, then run tree /opt/build/repo/assets/
• again, only if the npx expo export:web command exited with an error, also return an error (as false is a program that does just this)

The build did fail.

The directory tree did get dumped to the build logs.

The build did not get published (which is good as we don’t want to publish builds with errors).

That was exactly the plan. The command worked perfectly. It got us the information we needed to debug this.

This is also incorrect:

@Louis_Syfer

All extensions are lowercase, regardless of folder.

The filenames look lower-case to you only because your computer’s filesystem is case insensitive. (MacOS and some types of Windows filesystems are case insensitive.) All of the popular Linux filesystems are case sensitive.

The sites build logs do prove that there are mixed-case files in the assets directory:

12:42:13 PM: $ npx expo export:web || { tree /opt/build/repo/assets/ ; false ; }
12:42:14 PM: Exporting with Webpack...
12:43:17 PM: Failed to compile
12:43:17 PM: CommandError: ENOENT: no such file or directory, open '/opt/build/repo/assets/favicon.png'
12:43:17 PM: /opt/build/repo/assets/
12:43:17 PM: ├── adaptive-icon.PNG
12:43:17 PM: ├── boostarz_splash.png
12:43:17 PM: ├── expo_logos
12:43:17 PM: │   ├── adaptive-icon.png
12:43:17 PM: │   ├── favicon.png
12:43:17 PM: │   ├── icon.png
12:43:17 PM: │   └── splash.png
12:43:17 PM: ├── favicon.PNG
12:43:17 PM: ├── fonts
12:43:17 PM: │   ├── Metropolis-Regular.otf
12:43:17 PM: │   └── Quicksand-Regular.ttf
12:43:17 PM: ├── icon.PNG
12:43:17 PM: ├── images
12:43:17 PM: │   ├── adaptive-icon.PNG
12:43:17 PM: │   ├── favicon.PNG
12:43:17 PM: │   └── icon.PNG
12:43:17 PM: └── splash.PNG
12:43:17 PM: 3 directories, 14 files

This shows three directories with favicon files. Those locations are (in the order listed above):

/opt/build/repo/assets/expo_logos/favicon.png
/opt/build/repo/assets/favicon.PNG
/opt/build/repo/assets/images/favicon.PNG

The only one using all lower case is /opt/build/repo/assets/expo_logos/favicon.png. That isn’t the error message, though. The error message is for for this file:

/opt/build/repo/assets/favicon.png

You don’t have that file. You have it with an upper-case file extension:

/opt/build/repo/assets/favicon.PNG

It is right there is the logs in plain text. The filename is absolutely and without any doubt a mixed case filename.

This is exactly the issue that @hrishikesh pointed out twelve days ago:

@hrishikesh

Maybe relates to:

Are you struggling to understand why your project runs locally but errors out with missing files or logs that point toward issues with case when you try and build on Netlify? You are not alone. Often, case (as in: UPPERCASE or lowercase letters in filenames or paths) can cause problems. Here is a guide to understanding how case sensitivity issues present themselves, why they arise, and how you can fix them! 1. Errors you might see Case sensitivity issues can be frustrating to debug because som…

The build image filesystem is case-sensitive. The git repo is also case-sensitive. So, when the Linux build image clones the repo, the files are mixed case.

To summarize, we told you the correct answer twelve days ago. Please re-read that support guide above and, if there are still questions after reading it, let us know.