Search Unity

  1. Good news ✨ We have more Unite Now videos available for you to watch on-demand! Come check them out and ask our experts any questions!
    Dismiss Notice
  2. Ever participated in one our Game Jams? Want pointers on your project? Our Evangelists will be available on Friday to give feedback. Come share your games with us!
    Dismiss Notice

Feedback Unity should recognize Git LFS link files and print a more descriptive error message on import

Discussion in 'Editor & General Support' started by DrummerB, Jul 16, 2019.

  1. DrummerB


    Dec 19, 2013
    When you check out a Unity project that is using Git LFS to manage large binary files, there is a chance that the LFS link files are not resolved correctly. For example, if you just download a project from GitHub, instead of cloning it, you only download the link files. This results in somewhat vague asset import errors in Unity that could be improved:

    Could not create asset from : File could not be read
    Error during import of AudioClip : Failed decoding audio clip
    ImportFBX Error: Couldn't read file
    The type or namespace name could not be found ...
    The name does not exist in the current context
    I suggest that when an asset import fails, Unity should check the file if it's a Git LFS file and print a more helpful error message like "Could not import asset at path <path>. It looks like a Git LFS managed file that has not been checked out correctly."