Hi, @Hiliyeh, that file doesn’t appear anywhere in the deployed files. This is the list of files in that deploy:
Also, the site HTML itself makes no reference to that file.
This doesn’t sound like a Large Media issue as much as this sounds like a build issue. It is a private git repo so I’m not able to test building myself.
Why doesn’t the site build contain the same file the local build does?
To troubleshoot and find the answer, I would clone the repo to a new empty directory, then run the dependency install, then run the build command.
Once that is done, compare that build to the site at Netlify. If the local build has the same issue, then you’ll need to resolve that locally as the issue isn’t at Netlify. Once the local issued is resolve then try the Netlify build again.
However, if the fresh clone works and the Netlify build still is not working, then it is time to look for differences in the two builds. For example, are the node versions used the same? I see v12.18.0 used in the most recent build here.
Last but not least, does you build try to process the MP4 during the build (like resizing or embedding the video as base64 encoded text in the HTML)? If so, this won’t work with Large Media as described in the limitations section of the documentation:
Files tracked with Large Media are uploaded directly to the Netlify Large Media storage service on push, completely bypassing the site build. This saves build time, but also means that the files are not available to tools that process asset files during the build, such as Hugo’s image processing or the
gatsby-image plugin. Depending on your needs, you may be able to replace this functionality with Netlify’s image transformation service.
Please let us know if there are other questions about this.